[00:00] <popey> if you swipe back up to the top of the screen it will make the network indicator disappear
[00:02] <murrayuk> Is it possible to add my google contacts yet? It says that I should go into the accounts in system settings but there is only twitter and facebook there
[00:02] <popey> there is a command line tool to do it
[00:02] <murrayuk> is there a thread with useful command lines such as that?
[00:03] <popey> http://sergiusens.github.io/posts/google-contacts-on-ubuntu-touch.html
[00:11] <murrayuk> I keep getting this error "bash: ubuntu_chroot: command not found"
[00:11] <dejello> Anyone synced repos and try building again?  Mine's having an issue with the ubuntu-boot.img file not being present.  Started looking around but just wanted to see if anyone else had this issue
[00:12] <popey> murrayuk: ahh interesting, where are you seeing instructions to use ubuntu_chroot?
[00:12] <popey> we no longer need that
[00:13] <murrayuk> Ah okay, it was on the link you gave me :)
[00:13]  * popey pokes sergiusens to fix that
[00:14]  * sergiusens thinks about updating blog entry
[00:14] <popey> \o/
[00:14] <murrayuk> is there a default sudo password for the phone?
[00:15] <popey> phablet
[00:16] <murrayuk> I'm getting this error now "[INFO] addressbook: looking for databases...
[00:16] <murrayuk> [ERROR] GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[00:16] <murrayuk> [INFO] addressbook: backend failed
[00:16] <murrayuk> "
[00:29] <asac> cyphermox: you said that by now i can roam nicely between 3g and wifi?
[00:29] <asac> e.g. is it worth me giving that a try?
[00:31] <popey> yes
[00:31] <asac> ok cool
[00:31] <popey> todays image has 3g on by default
[00:31] <asac> let me double check i have the latest image
[00:31] <popey> s/today/yesterdays/
[00:31] <asac> how can i find that out without installing latest?
[00:32] <asac> well let me just flash and be safe
[00:32] <popey> heh
[00:32] <popey> if i could remember how to tell, I'd tell you, then put it in the FAQ
[00:32] <asac> still would love to be able to see the build id somewhere in the UI :)
[00:32] <asac> or shell
[00:32] <popey> its in a file somewhere, i just dont recall where
[00:32] <asac> popey: yeah. no problem my memory is at least as bad as yours :)
[00:33] <asac> we are just old
[00:33] <popey> so true
[00:33] <asac> interesting ... so phablet-flash didnt download anything, just went directly to flashing... guess that means i had the latest :)
[00:33] <popey>  /system/ubuntu_stamp
[00:34] <popey> yes
[00:34] <popey> which means you could CTRL+C
[00:34] <asac> it is already pushing
[00:34] <asac> i am scared that it will be trashed
[00:34] <popey> you can kill that
[00:34] <asac> ok done :)
[00:34] <popey> thats just like ftping a file up
[00:34] <asac> and now?
[00:34] <popey> reboot
[00:34] <asac> just pull power?
[00:34] <popey> adb reboot
[00:34] <asac> nice ... screen is off :0
[00:35] <asac> now it boots
[00:41] <asac> ok the wifi indicator is still bogus i guess ... i am connected against a 70/70 AP and its completely black. but i can ping
[00:41] <popey> nm-tool
[00:41] <popey> i find that the best way to see what connections i have
[00:42] <asac> cool... both are connected :)
[00:42] <asac> wonder if thats good for power consumption ... is that also the case on android if i am on wifi?
[00:44] <asac> bfiller: when is "remember password" for webbrowser targetted?
[00:45]  * asac goes for smoke
[00:47] <RobbyF> alright, unlocked my galaxy datt, time to ubuntu touch it up
[00:49] <RobbyF> anyone done this before and want to walk me through it, first time ever. not a dev
[00:49] <popey> asac: 3g eats battery way more than wifi
[00:56] <asac> popey: right... hence i thought that on android they go to pure phone and turn off 3g if you hit wifi
[00:56] <asac> while here it seems we have now both cooking :)
[00:56] <asac> ok going for real :)
[00:56] <asac> bbib
[01:12] <zdlite> Hi, Just dropped Ubuntu touch onto Nexus 4. I'm having issue making phone calls though when i press the dial button nothing happens.
[01:12] <zdlite> Did i do something wrong?
[01:14] <zdlite> anyone here?
[01:15] <RobbyF> people are here
[01:16] <zdlite> ok thanks Rob
[01:20] <RobbyF> must be busy
[01:20] <RobbyF> shouldn't have a problem with making a call
[01:20] <RobbyF> I was on 0708 build and it was ok
[01:25] <pmcgowan> zdlite, do you have a pin on your sim
[02:03] <lyric340> Hi, I'm just getting started and involved, is the data for maguro accurate (https://wiki.ubuntu.com/Touch/Devices/Nexus)?
[02:07] <pmcgowan> lyric340, that page is a bit out of date, maguro is a primary reference so support there will be as good as any device
[02:14] <lyric340> @pmcgowan, Thanks for the heads up. Is there any documentation on what is not working on Galaxy Nexus?
[02:15] <lyric340> I'm looking for an area to help...
[02:15] <pmcgowan> lyric340, not really an up to date list, better to ask here, the PIN support just landed for example
[02:16] <pmcgowan> lyric340, happy to have help, whats your interest
[02:16] <lyric340> I'm a little more partial to kernel/HAL layer when working with Android, but interested in looking at Ubuntu Touch as a whole.
[02:17] <pmcgowan> lyric340, did you get on the email list as well?
[02:18] <pmcgowan> ubuntu-phone@lists.launchpad.net
[02:18] <lyric340> @pmcgowan, not yet. I have only just now pulled the code, and begun setting up my environments and keys.
[02:19] <pmcgowan> lyric340, we are using much of he HAL so thats good
[02:19] <pmcgowan> most of the devs are offline this evening
[02:19] <lyric340> @pmcgowan, I'm in the market for a new phone to free up my galaxy nexus for work on this.
[02:19] <pmcgowan> great
[02:20] <lyric340> Okay, I'll sign up for the mailing list, and then plod through the code and read through the mailing lists. As soon as I can get a replacement phone, I'll wipe and flash my galaxy nexus and begin more in depth work.
[02:20] <pmcgowan> reflashing is pretty straight forward but it wipes android so its all or nothing
[02:20] <pmcgowan> good
[02:22] <pmcgowan> lyric340, anything that is working will work on the nexus so its a good device to use
[02:22] <lyric340> Exactly why I need the replacement first...
[02:23] <pmcgowan> ok
[02:23] <lyric340> @pmcgowan, All signed up, I have some reading to do. Thank you so much for your time this evening.
[02:24] <pmcgowan> ok will look for you next time
[04:53] <True_unReal> hello?
[06:18] <djcanadajeff> if I can get into ubuntu touch chroot but my screen is black
[06:18] <djcanadajeff> how do I fix this, can I post/view logs that will help find whats wrong
[07:06] <rickspencer3> hey all, does anyone know if awe's PIN support is in the current build if I do phablet-flash now?
[07:06] <rickspencer3> or do I need to wait for popey and ogra to validate the image?
[07:09] <rickspencer3> didrocks, ^ do you know? awe's mail said something about "today's image"
[07:10] <didrocks> rickspencer3: no, I'm more reviewing our work to publish as much as packages as possible, didn't flash before ogra or popey gives the green flag :)
[07:16] <rickspencer3> didrocks, ok
[07:16] <rickspencer3> didrocks, I thought they were going to validate the image and the move it to current
[07:17] <rickspencer3> so you couldn't get an "awful" image with phablet-flash
[07:17] <rickspencer3> did I understand that correctly?
[07:17] <didrocks> rickspencer3: I understood that too, so if you're wrong, we both are :-)
[07:18] <didrocks> (not sure it's a good relief though ;))
[07:18] <rickspencer3> :)
[07:19] <rickspencer3> didrocks, should be interesting to see how it goes when all the auto-pilot tests are being run on the daily images
[07:19] <didrocks> rickspencer3: well, TBH, I don't expect that much difference as explained in the email as we already run 80% of them in daily releases
[07:20] <didrocks> (but better once we will be able to run then on the hardware)
[07:20] <rickspencer3> didrocks, I think we will see issues
[07:20] <didrocks> they are, the apps stacks have tests failing for 2 days for instance
[07:21] <rickspencer3> I think running the tests on the daily image will cause back pressure to ensure that the daily upstream releases are good
[07:21] <didrocks> but you shouldn't see those as the components are then blocked for release
[07:21] <rickspencer3> I suspect it will make your job easier
[07:21] <didrocks> I hope so as well :) also, it's another data point to try to ducktype where the breakage happened
[07:21] <didrocks> if it passed dailies
[07:21] <rickspencer3> didrocks, also, I think adding the existing testes are just a start
[07:21] <didrocks> and then it's broken, we'll see that it's something else from distro
[07:21] <rickspencer3> we can use auto-pilot for testing all kinds of things
[07:21] <rickspencer3> didrocks, exactly
[07:21] <rickspencer3> integration testing is a good thing
[07:22] <didrocks> yep :)
[07:22] <rickspencer3> and if it goes smoothly because the individual stacks are well tested, that's also a good thing
[07:22] <rickspencer3> the key will be our speed in which we respond to test failures
[07:22] <didrocks> rickspencer3: we always take latest image with otto (and dist-upgrade in the morning), so we already catched several times regression from distros impacting us.
[07:22] <didrocks> yep, agree on the speed to respond to issues
[07:24] <rickspencer3> didrocks, yeah, like asac said, it will be good if we get to green quickly because of the work you already did
[07:24] <rickspencer3> I think running the tests that we already have is step 1
[07:24] <rickspencer3> step 2 will be adding new tests
[07:24] <rickspencer3> step 3 will be making it simple to run the tests in emulation, for developers and in the lab
[07:24] <rickspencer3> imo
[07:25] <didrocks> yep, totally agreed that step3 is a little bit too hard still for developers
[07:26] <didrocks> or just to be able to reproduce the env localy even
[07:29] <rickspencer3> didrocks, that's longer term ... I think our focus on daily quality right now is the best way to go, rather than waiting for magic tools to be developed ;)
[07:29] <rickspencer3> but we'll get to step 3, I am certain
[07:30] <didrocks> right, but I really think we need to have better manual testing right now
[07:30] <didrocks> like what we did for unity
[07:30] <didrocks> write a lot of manual tests, that we do for every release
[07:30] <didrocks> then, those manual tests would be transformed into autopilot tests
[07:30] <didrocks> that will ensure we always have a consistent phone image, knowing exactly the scenarios that works
[07:31] <didrocks> (and if we discover a new one failing, extending the manual test doc)
[07:35] <mko> hi
[07:40] <didrocks> popey: maybe that will make sense to you to ease your dogfooding task, thoughts? ^
[07:41] <dholbach> good morning
[07:44] <popey> rickspencer3: as I understand it phablet-flash currently doesn't pull from "current" but latest image on cdimage, it would need to be patched to do that. I don't see a bug filed for that https://bugs.launchpad.net/phablet-tools
[07:44] <rickspencer3> hey popey
[07:44] <rickspencer3> so if I phablet-flash now I can try the PIN support?
[07:44] <popey> when did PIN support land?
[07:44] <popey> the latest image on cdimage is yesterdays
[07:45] <rickspencer3> popey, in awe's mail to @ubuntu-phone he said something about "today's" image
[07:45] <popey> oh, not opened email yet
[07:45]  * popey does so
[07:47] <Saviq> asac, ping
[07:48] <popey> rickspencer3: I just apt-get update and apt-get install ofono-scripts on my phone which has yesterdays image
[07:49] <popey> which would be "today" by awe's timezone
[07:49] <rickspencer3> popey, so should I try phablet-flash?
[07:50] <popey> did you flash it "yesterday"?
[07:50] <popey> well you'll need to apt-get install ofono-scripts anyway, because that's not in the build (yet)
[07:50] <popey> you certainly could phablet-flash if you want a clean start
[07:51] <rickspencer3> popey, ok
[07:51] <rickspencer3> In a bit I'll install the ofono-scripts and give it a try
[08:04] <popey> didrocks: do you know of any manual tests we already have for any of the phone components?
[08:04] <popey> ah yes, on the QA tracker
[08:05] <didrocks> popey: yeah, it's quite limited, but it's a good starting base
[08:05]  * popey was looking in text files, silly me
[08:12] <didrocks> rickspencer3: btw, what about putting on the dashboard the daily release tests result as well?
[08:13] <didrocks> I think it will be valuable to see what failures blocked landing on some components
[08:13] <rickspencer3> didrocks, wfm, but I guess talk to gema about that?
[08:13] <didrocks> gema: ^
[08:13] <rickspencer3> didrocks, I think it would be good if you see a failure on the image, if you could see easily if the failure was on the daily release
[08:13] <gema> didrocks: what testing are you referring to? autolanding?
[08:13] <didrocks> rickspencer3: right, to see the diff :)
[08:13] <rickspencer3> so you would quickly know if it's a pure upstream or an integration issue
[08:14] <didrocks> gema: daily release, yeah
[08:14] <didrocks> rickspencer3: exactly!
[08:14] <gema> didrocks: we are working on that with the PS QA folks, the views are not quite where you can compare things straight away but we are working on it
[08:14] <didrocks> gema: ah, so you will publish soon the daily release tests status as well? great! :)
[08:15] <gema> didrocks: yep
[08:15] <didrocks> great :)
[08:15] <gema> didrocks: we'll land a first version soon and then we can work on making it better for your needs
[08:15] <gema> didrocks: I am chasing your devices today
[08:15] <didrocks> gema: excellent, that will be of a great help, thanks!
[08:15] <gema> didrocks: the very least I am going to make one or two of the ones we already have available for your testing
[08:16] <gema> and speed up the set up of the new ones
[08:16] <gema> didrocks: next time ping me earlier, plz :D
[08:16] <didrocks> gema: we opened a RT in may as requested, but I guess with pgraner transitionning and so on, the requests and pings were lost :)
[08:17] <gema> didrocks: it's been quite busy, yep, but I wasn't on copy on that RT so I completely missed that
[08:18] <gema> didrocks: I had been naively waiting for a while and thought you were busy with something else, rather than waiting for the devices
[08:18] <didrocks> gema: well, I think otto will need some adjustement once in prod, but with our local devices, it's working fine
[08:18] <didrocks> as we always refresh with latest images, but only provision once, it's fast as well :)
[08:18] <gema> didrocks: yep, but to be able to adjust in prod you need something to run on
[08:19] <didrocks> exactly ;)
[08:19] <gema> didrocks: will let you and jibel know later today
[08:19] <didrocks> thanks!
[08:19] <gema> np
[08:36] <djcanadajeff> I can get into ubuntu touch chroot but my screen is black
[08:36] <djcanadajeff> how do I fix this, can I post/view logs that will help find whats wrong
[08:37] <djcanadajeff> I'd even be willing to offer VNC remote desktop if someone could assist with this
[09:02] <seb128> do we have any way to lock screen rotation at the moment?
[09:03] <JamesTait> Good morning all, happy World Population Day! :-D
[09:03] <seb128> is that going to be a Mir feature? do we have an api somewhere in the stack to read/set the screen rotation locking?
[09:18] <ogra_> hmm, i wonder why the image doesnt finish today
[09:18] <xnox> seb128: we did have a tiny daemon doing screen rotation on nexus7-X, not sure if we have same for surfaceflinger....
[09:19] <popey> ogra_: still running or crapped out?
[09:19] <seb128> xnox, I doubt the solution used there works on the touch image
[09:20] <ogra_> no, the rotation is managed through androids sensor service via platform-api
[09:20] <seb128> tvoss_, ^ do you know about that?
[09:20] <ogra_> and hybris
[09:20] <xnox> seb128: yeah... i wouldn't expect it to.....
[09:20] <tvoss_> xnox, what's the use case you want to solve?
[09:20] <ogra_> no idea if we can lock it already ... probably via a property (try getprop if you see anything rotation related)
[09:20] <seb128> tvoss_, I was the one asking
[09:21] <seb128> tvoss_, I'm trying to figure what I need the system-settings "lock screen rotation" switch to
[09:21] <seb128> tvoss_, I'm trying to figure what I need to plug the system-settings "lock screen rotation" switch to
[09:21] <ogra_> popey, look like it is still running .... i'm probably just impatient
[09:21] <tvoss_> seb128, hmmm, should end up somewhere in the shell. saviq, can you help out here?
[09:23] <Saviq> tvoss_, seb128, well, we have no such thing yet
[09:23] <m-b-o> I can't unlock my phone anymore after apt-get upgrade this morning. Is there a way to unlock the screen from shell?
[09:24] <tvoss_> Saviq, so all apps listen to the rotation sensor?
[09:24] <seb128> Saviq, is that on a roadmap (Mir, shell, platform api, ...)?
[09:24] <Saviq> tvoss_, yes
[09:24] <tvoss_> Saviq, I think we should put it on the roadmap
[09:25] <Saviq> tvoss_, and I still don't know how we can communicate with the app for that (and other questions the shell might need to ask the app)
[09:25] <Saviq> tvoss_, I've asked many times, didn't get no answer
[09:25] <Saviq> we == shell
[09:26] <popey> m-b-o: i dont see that issue. do you not get the launcher when you pull in from left?
[09:26] <popey> i upgraded then rebooted and it's fine
[09:26] <tvoss_> Saviq, ack. I was wondering if it would make sense for the shell to "own" the device rotation system setting, with apps listening to it
[09:26] <tvoss_> s/system setting/system property
[09:27] <Saviq> tvoss_, still, what if the app doesn't support the orientation you've locked in?
[09:27] <tvoss_> Saviq, up to the app to not react to it
[09:28] <Saviq> tvoss_, let me find a doc
[09:28] <tvoss_> Saviq, ack
[09:28] <ogra_> ah, there is the image
[09:33] <m-b-o> popey: I can't turn on the screen anymore, when it's gone black after idling.
[09:33] <popey> m-b-o: can you adb shell in over usb and see if unity8 is running?
[09:33] <m-b-o> popey: and I can't turn of the screen when using on/off button. it fallsback to the lock screen, the screen dimms some times and turns off
[09:34] <m-b-o> unity8 is running
[09:34] <m-b-o> and when i click the on/off button, cpu load is on unity8
[09:35] <popey> if you adb shell in and look in /home/phablet/.ubuntu-session/logs - anything interesting?
[09:37] <m-b-o> popey: nope
[09:37] <popey> m-b-o: rebooted it?
[09:39] <m-b-o> several times. only came up after some persuasion and after the battery was removed
[09:40] <popey> erk
[09:40] <popey> you are using the latest flipped image?
[09:40] <popey> i.e. when you "adb shell" you get an ubuntu root prompt, not an android one?
[09:41] <m-b-o> haven't tried adb, was ssh'ing
[09:41] <popey> ah ok
[09:45] <m-b-o> popey: have a gnex. using on/off key, screen falls back to lock screen instead of getting switched off. can swipe away lockscreen. when on lockscreen and doing nothing, screens dimms slowly before getting switched off
[09:45] <popey> ogra_: does your gnex do the above after an apt-get upgrade?
[09:46] <m-b-o> image is from end of last week, flashed via twrp
[09:46] <popey> ah
[09:46] <popey> you probably want to flash newer, 20130710 - or wait for todays image a bit later
[09:46] <ogra_> the powerd upstart job moved today
[09:46] <popey> oh, todays image arrived
[09:47] <ogra_> yeah
[09:47] <popey> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130711/
[09:47]  * popey flashes
[09:47] <ogra_> i said so above, but didnt ping you, sorry
[09:47] <popey> np
[09:47] <popey> so you did
[09:54] <popey> ogra_: out of interest, what will we do at weekends, still flash and manually move to current? (I am happy to do that)
[09:54] <ogra_> hmm, good question
[09:54] <popey> given saturday image may well have friday crack / fun in it
[09:54] <popey> and for some saturday is a good day to flash
[09:54] <ogra_> well, i hope we wont have to do that for more than one weekend
[09:55] <popey> you're expecting automation?
[09:55] <ogra_> i know plars_ is working on fixing automated testing
[09:55] <popey> ok
[09:55] <ogra_> yes
[09:55] <popey> happy to do it until that happens
[09:55] <ogra_> there are a few parts missing on the build side too ... i'm just trying to fix them
[10:00] <rickspencer3> \o/ German SIM with PIN is working!
[10:01] <popey> yay
[10:01] <popey> ogra_: flashed 20130711 to mako, made phone call, browsed web, started some apps okay
[10:01] <ogra_> great
[10:02] <popey> however I am now seeing what m-b-o reported
[10:02] <ogra_> rickspencer3, yay
[10:02] <popey> can't wake/unlock the phone from slumber
[10:02] <ogra_> check syslog for powerd
[10:02] <ogra_> (and check if powerd runs at all)
[10:02] <popey> dmesg | grep powerd returns blank
[10:03] <popey> Jul 11 09:55:28 ubuntu-phablet kernel: [    1.225118] sp_tx_vbus_powerdown: 3.3V output disabled
[10:03] <popey> Jul 11 09:55:28 ubuntu-phablet kernel: [    1.283290] sp_tx_hardware_powerdown: anx7808 power down
[10:03] <popey> Jul 11 09:55:49 ubuntu-phablet kernel: [   26.221455] init: powerd main process (446) killed by SEGV signal
[10:03] <popey> Jul 11 09:55:49 ubuntu-phablet kernel: [   26.257836] init: powerd main process ended, respawning
[10:03] <popey> Jul 11 09:55:50 ubuntu-phablet powerd[1133]: Using backlight at /sys/devices/i2c-0/0-0038/backlight/lm3530
[10:03] <popey> oops
[10:03] <popey> same on nexus 7
[10:05] <ogra_> do you see it in the pprocesslist ?
[10:05] <ogra_> it seems to have respawned
[10:05] <popey> yes
[10:05] <popey> root      1133  0.0  0.2  71624  5404 ?        Ssl  09:55   0:00 /usr/bin/powerd
[10:05] <ogra_> hmm, thats weird
[10:06] <popey> https://bugs.launchpad.net/touch-preview-images/+bug/1200156
[10:06] <popey> to track it
[10:06] <ogra_> i used to ship a powerd.override job before ... but that was completely moved over into powerd now
[10:06] <popey> wonder who got bug 1200000
[10:07] <ogra_> it shold behave exactly the same still
[10:07] <davmor2> ogra_, popey: is there an issue with network manager?  Since the 3g auto connect thing has been in place the wifi list hasn't been populated. Or has been but sporadically
[10:07] <jodh> popey: anything useful in /var/log/upstart/powerd.log ?
[10:07] <popey> __pthread_gettid -2
[10:07] <popey> __pthread_gettid -2
[10:07] <popey> "no"
[10:09]  * ogra_ waits for his flash to finish
[10:09] <popey> davmor2: can't tell right now as my phone is a bit borked
[10:10] <popey> m-b-o: could you confirm bug 1200156
[10:10] <davmor2> popey: is that a hint not to upgrade this morning
[10:10] <popey> yes
[10:10] <m-b-o> popey: yes
[10:10] <popey> thanks
[10:11] <davmor2> popey: thanks for the hint I was going to flash my devices after reading emails :)
[10:11] <popey> always worth checking in here first ☻
[10:13] <mcute> Hi guys,anyone knows when the phone function is going to be usable in denmark ?
[10:14] <popey> mcute: should work in any region that has GSM
[10:14] <gema> popey: then that bug's important is quite high, I'd say critical
[10:14] <mcute> i can recieve calls, but cant make them :)
[10:15] <gema> mcute: what is the problem with making a call, are you trying to call a normal number or a services number?
[10:15] <davmor2> gema: Naaaaaaaaaaaaa it's only a flesh wound
[10:15] <popey> gema: fixed
[10:15] <gema> popey: it's fixed?! that was quick :D
[10:15] <popey> hah
[10:16] <popey> i wish
[10:16] <mcute> a normal cell number..it just goes to voicemail, no matter who i'm calling
[10:16] <gema> mcute: what happens when you call a home number?
[10:17] <mcute> didn't try that, don't know anyone that uses one : )
[10:17] <ogra_> heh
[10:17] <gema> mcute: haha, can you tell me what image you are using?
[10:18] <mcute> don't recall the version number, but its for the n4/mako
[10:18] <ogra_> when did you flash it ?
[10:18] <mcute> and it was a week ago i had it on
[10:18] <popey> mcute: phone me! :D
[10:19] <popey> Note: I am not in Denmark.
[10:20] <mcute> i did talk on the phone while using it...but coldn't make a call, straight to voicemail and then they would call back
[10:20] <ogra_> k, doesnt suspend here either on maguro
[10:21] <ogra_> restarting powerd doesnt help apparently
[10:21] <ogra_> i doubt it is related to the upstart job
[10:22] <gema> ogra_: needed to talk to you about the manual testing you guys are doing and was wondering if we could automate that and hook those tests to the publication of the images like we do with desktop
[10:22] <gema> ogra_: it'd help to know everything you guys are verifying as a minimum
[10:22] <ogra_> gema, i think plars_ was already working on it
[10:23] <gema> ogra_: yes he is, the problem is that I don't think our default tests as they are cover all you need
[10:23] <ogra_> gema, flashing, booting, starting an app and looking around if the shell is populated is what i do
[10:23] <gema> or I don't know if they do, rather
[10:23] <ogra_> i guess popey also tries a call
[10:23] <m-b-o> ogra_: what action should get triggered when pressing on/off key?
[10:24] <gema> uhmmm... maybe we should add the phone-app tests to the default job that'll run on every image
[10:24] <ogra_> m-b-o, powerd should recieve a message via dbus and switch the backlight on/off (and some other stuff)
[10:24] <popey> i called earlier, yes
[10:24] <popey> it worked but the phone app was very laggy
[10:25] <ogra_> gema, i think there is a test suite for the coreapps, when we had a broken image recently they properly all failed for asac
[10:25] <ogra_> i guess that would be a good one to run
[10:26] <ogra_> beyond that, my tests are very visual (check if the lenses in the shell are all populated for example) not sure how to automate that
[10:26] <gema> ogra_: there's several for the core apps
[10:26] <popey> we're mostly doing shakedown tests
[10:26] <popey> to make sure it's not catastrophically broken
[10:26] <gema> ack
[10:26] <popey> today i flashed, booted, launched 5 apps, dialled a number, made sure internet worked
[10:27] <gema> popey: whenever we switch to automating checking, we may miss some of the things you guys are checking until all the tests are working properly
[10:27] <popey> i dont plan on stopping doing my daily shakedown
[10:27] <gema> because I'd like to hook them up to stop images only when we are happy that they work as expected most of the time
[10:27] <popey> I've been doing them for weeks already
[10:27] <gema> popey: yeah, but if we hook up the automated tests to daily images they'll get published based on jenkins' feeling, not your testing
[10:28] <gema> popey: even though you can continue to do your testing afterwards
[10:28] <gema> you may find some problem has escaped us
[10:28] <popey> well maybe we should throw some deliberately broken images at jenkins and see whether it passes them or not
[10:28] <popey> e.g. todays and 20130709
[10:29] <popey> because if it passes really bad images then i dont think it can be trusted to gate the images
[10:29] <gema> popey: http://reports.qa.ubuntu.com/smokeng/saucy/
[10:29]  * popey has a mirror of past images you can throw at jenkins:- http://popey.mooo.com/mirror/
[10:29] <gema> it does
[10:29] <gema> well, today's results are not there yet
[10:29] <popey> wow look at all those passes for 20130709
[10:29] <popey> thus proving my point
[10:29] <gema> popey: yes
[10:30] <gema> and my worry
[10:30] <popey> that should have red lights on it
[10:30] <gema> that's why I want to improve those tests
[10:30] <popey> ergo we should not trust it yet
[10:30] <gema> popey: what was broken on the 9th image?
[10:30] <popey> I'd be happy to video myself doing a morning test so you can see exactly what I do, because I may not describe it well ☻
[10:30] <ogra_> gema, the shell
[10:30] <popey> shell didn't show any dynamic content
[10:30] <gema> popey: that'd be super useful
[10:31] <popey> alright, will video it tomottow
[10:31] <popey> -typos
[10:31] <gema> popey: ack
[10:32] <davmor2> gema: I do a heavier shakedown on an evening as I use the galaxy nexus and n7 as my daily devices where I can.
[10:32] <davmor2> I miss youtube play back though :)
[10:33] <gema> davmor2: that's good, I need to make sure you don't get broken and your evening entertainment obscured by bugs then :P
[10:33] <gema> davmor2: although you being you, you'll find other bugs :)
[10:33] <davmor2> gema: It's me they could say it was perfect and I'd find the only bug :)
[10:34] <gema> davmor2: yep, and I'd find the one after you no problem :P
[10:35] <davmor2> gema: hahaha
[10:35] <popey> this is true
[10:35] <ogra_> hmm
[10:38] <pete-woods> dpm: hi! Regarding the docs you uploaded for me yesterday - do they update automatically with distro releases of the -doc package?
[10:40] <popey> ʘ‿ಠ
[10:43] <xnox> ogra_: coloured output of android build looks "funny" in launchpad build logs.... =) but waiting for it to build and hopefully not fail like last time.
[10:44] <ogra_> xnox, yay
[10:44] <popey> ogra_: who should we poke with that bug?
[10:44] <ogra_> popey, working on it
[10:44] <popey> ok
[10:45] <popey> \o/
[10:45] <ogra_> gimme a few reboots more
[10:45]  * popey reboots ogra_ 
[10:45] <ogra_> lol
[10:45]  * popey hopes we have backups
[10:48] <xnox> ogra_: it takes 23minutes here. I'll give distro builders 1.5h
[10:48] <ogra_> well, you corss build, dont you ?
[10:49] <katie> popey, hi, i've updated my phablet-tools but still getting similar error http://paste.ubuntu.com/5864505/
[10:50] <xnox> ogra_: yeah.
[10:50] <xnox> katie: oohh mako. I could try flashing yours manually here.
[10:51] <katie> xnox., that would be great.. are you in the office?
[10:51] <xnox> katie, yeap =)
[10:51] <ogra_> env QT_QPA_PLATFORM=hybris
[10:51] <ogra_> env ANDROID_ROOT=/system
[10:51] <ogra_> popey, ^^ add these two to the upstart job
[10:51] <ogra_> then reboot
[10:52] <popey> ogra_: which upstart job?
[10:52] <ogra_> powerd.conf
[10:53] <popey> k
[10:54] <m-b-o> ogra_: popey: this fixes it
[10:55] <popey> nice one m-b-o
[10:55] <djjeff> does ubuntu touch require android/cyanogenmod to run?
[10:55] <djjeff> or can it run as a stand alone
[10:55] <ogra_> djjeff, it uses the drivers (and some services) from android
[10:56] <djjeff> sounds kinda lame
[10:56] <ogra_> ??
[10:56] <djjeff> it should have been built from the ground up
[10:56] <djjeff> because each time a new ubuntu touch comes out
[10:56] <djjeff> would you not have to upgrade cyanogenmod as well
[10:56] <popey> ogra_: yup, that did it
[10:57] <ogra_> djjeff, well, yeah, then we would have supported exactly the one phone for which we would have drivers
[10:57] <ogra_> djjeff, if yu can show me one that actually *has* linux (not android) drivers
[10:57] <ogra_> popey, great, uploading a fix
[10:57] <popey> neo freerunner ㋛
[10:58] <djjeff> could we find linux drivers for my hardware
[10:58] <popey> manufacturers generally dont make them, so no
[10:58] <djjeff> I have samsung galaxy tab 10.1 (p4wifi)
[10:58] <djjeff> I was able to get raring to work on p4wifi
[10:58] <djjeff> but not saucy
[10:58] <djjeff> because the cyanogenmod is out of date now?
[11:01] <xnox> ogra_: so katie's mako is unflipped, and it doesn't have enough space on /data to flash it.
[11:01] <ogra_> djjeff, you wont find any drivers except android ones for your tablet (nor for most usable other phones ... ) there is a reason we picked that path ...
[11:02] <ogra_> djjeff, ping the person that does the port for your device, porters need to regulary rebuild if we change code
[11:03] <djjeff> the porter for the p4wifi is missing
[11:03] <ogra_> popey, i uploaded a workaround but didnt touch powerd itself, can you assign the bug to mfisch and tell him about the two vars in there
[11:03] <djjeff> cant reach them
[11:03] <popey> sure
[11:04] <ogra_> well, alternatively you could try porting yourself
[11:04] <djjeff> is it easy to port?
[11:04] <ogra_> see the wikipage from the channel topic it has a step by step porting guide
[11:04] <djjeff> could I take a nightly image of cyanogenmod and port it over quickly?
[11:05] <ogra_> no
[11:05] <ogra_> you need to port the source
[11:05] <ogra_> we dont use 90% of cyanogenmod ... as i said, literally only the drivers and some services that make use of them
[11:05] <ogra_> (sensors, graphics drivers etc)
[11:07] <djjeff> so why would raring work on my p4wifi
[11:07] <djjeff> and saucy just show black screen
[11:07] <djjeff> does not make sense
[11:08] <ogra_> sure it does
[11:08] <ogra_> the bridging library that is used for communicating with android (libhybris) lives on both, ubuntu and android
[11:08] <djjeff> I dont have android installed
[11:08] <ogra_> if it gets updated on the ubuntu side, the android side needs to be updated accordingly
[11:08] <djjeff> only cyanogenmod
[11:09] <ogra_> erm
[11:09] <ogra_> you are aware that cyanogenmod *is* android ?
[11:09] <djjeff> where in cyanogenmod do I need to update is there a guide
[11:09] <ogra_> just differently built
[11:09] <ogra_> yes, see the channel topic, there is a porting guide
[11:09] <djjeff> cyanogenmod lives in /system
[11:10] <ogra_> the patched android/cyanogenmod tree needs to be rebuilt regulary
[11:10] <ogra_> every time libhybris changes in the ubuntu side
[11:11] <djjeff> is there a prebuilt cyanogenmod that I can download somewhere?
[11:11] <ogra_> yes, the one done by the porter
[11:11] <ogra_> but as you already noticed he didnt updatte since raring
[11:12] <ogra_> so reach oout to him and make him rebuild it
[11:12] <ogra_> i see his contact info linked on the wiki
[11:12] <ogra_> just contact him
[11:15] <ogra_> xnox, then katie needs to make some room :)
[11:16] <ogra_> (just a guess though :) )
[11:39] <asac> ogra_: we ran through all apps (core and default) to ge ta feel
[11:39] <asac> even wit h new image the outlook is gloomy :)... i hope folks have run them on their own and are working on it
[11:42] <xnox> ogra_: 41 minutes, done https://launchpad.net/~canonical-foundations/+archive/upstart-daily/+build/4785831
[11:42] <xnox> ogra_: I have no clue if those are flashable at all, though =)
[11:42]  * ogra_ takes a look at the build log
[11:43] <ogra_> the output looks promising at least :)
[11:44] <ogra_> i'll do some tests later, still busy getting the buildstamp into our rootfs atm ... seems thats what blocks automated testing
[11:45] <xnox> ogra_: the ppa for that package is https://launchpad.net/~ubuntu-toolchain/+archive/android/+packages
[11:45] <ogra_> yeah
[11:45] <xnox> ogra_: i'm off to launch and fix up installer. Will try to test them as well.
[11:46] <ogra_> are the binary blobs supposed to be in there ?
[11:46] <xnox> ogra_: they are.
[11:46] <xnox> ogra_: they are there, no idea if they are suppose to be or not.
[11:47] <xnox> tarball is still 500M =( and the images/zips include/embed kernel, not sure how good or bad that is.
[11:48] <ogra_> well, they kind of have to
[11:49] <ogra_> oh, you mean you dont pull the kernel packages dynamically atm ?
[11:52] <WebbyIT> Hi balloons :) Can you help me? I'm following the autopilot tutorial, but I have an error when I try to launch it http://paste.ubuntu.com/5864665/
[11:57] <m-b-o> WebbyIT: remove the / at the end, should only be the name CurrencyConverter
[12:04] <WebbyIT> m-b-o: thanks :)
[12:06] <m-b-o> WebbyIT: you can even call "autopilot list" to get a list of all available tests, so you can run a single test if you want
[12:08] <WebbyIT> m-b-o: cool! Thanks
[12:21] <djjeff> what is ifconfig "dummy0"
[12:21] <djjeff> and "sit0"
[12:23] <xnox> ogra_: dynamically pulls kernels, hybris, platform-api at build time.
[12:23] <xnox> ogra_: blobs are in the "upstream" orig tarball.
[12:23] <ogra_> perfect
[12:26] <ogra_> popey, new image build running ... we should have something to test in ~1h
[12:33] <xnox>  \o/
[12:33] <popey> ogra_: sweet!
[12:33] <popey> lunchtime!
[12:56] <sil2100> didrocks: I need advice regarding the autopilot-touch issue... I cannot make the python-ubuntu-platform-api dependency arch-specific, because autopilot-touch is a python package with arch: all, while I would feel dirty making an python package arch: armhf
[12:56] <sil2100> didrocks: since theoretically a touch device can be also i386, not only armhf :|
[12:56] <sil2100> didrocks: so maybe some Suggests/Recommends instead as it was before?
[12:57] <sil2100> It would be good if python-upa would at least provide some stubs for non-armhf archs
[12:58] <sil2100> didrocks: so maybe modifying python-upa to also provide some dummies for non-arm?
[12:59] <didrocks> sil2100: yeah, I think it's the right approach
[12:59] <didrocks> so upa for all archs, dummies (until we have stubs) for !armhf
[13:22] <ogra_> asac, hrm, phonedations has the daily standup at 17:00 ... not sure that time for the CI forum will fly so well
[13:29] <asac> ogra_: this will be once a month most likely
[13:29] <asac> i elieve you guys should skip the standup for this purpose
[13:29] <asac> there is not much flexibility
[13:29] <ogra_> yeah, thats fine
[13:29] <ogra_> i thought it was weekly
[13:29] <asac> with all those key people that are always overbooked
[13:29] <asac> well for now its a one time thing.
[13:30] <asac> then we can agree
[13:30] <ogra_> yeah
[13:30] <asac> i believe it will be monthly or so
[13:30] <ogra_> popey, new image should be up
[13:30] <asac> because its aligning
[13:30] <asac> and also want that people can come back with presentations etc.
[13:30] <ogra_> ughm, presentations ?
[13:31] <ogra_> you are turning into a manager !
[13:31] <asac> presentatkions == proposals
[13:31] <asac> however, the guy can present it without using hands and legs
[13:31] <asac> :)
[13:32] <asac> i dont know how it will work, but i assue we will identify problems first
[13:32] <asac> and then have tasks that folks come back with proposals/ideas so we can talk about them etc.
[13:32] <asac> presentations dont need to be slides :)
[13:32] <ogra_> heh, so i can dance my proposal too ?
[13:33] <ogra_> like a waldorf student ... :)
[13:39] <popey> ogra_: ok
[13:49] <sforshee> ogra_, popey: MR for the powerd bug - https://code.launchpad.net/~sforshee/powerd/fix-power-button/+merge/174203
[13:50] <ogra_> sforshee, still missing one
[13:50] <ogra_> env QT_QPA_PLATFORM=hybris
[13:50] <sforshee> ogra_: when I tested I didn't need it
[13:50] <sforshee> powerd doesn't use QT at all
[13:51] <ogra_> well, it doesnt work here if i only set one
[13:51] <sforshee> but if you say it's really necessary I'll add it
[13:51] <sforshee> all right
[13:51] <ogra_> i tried with about 700 reboots (felt)
[13:51] <sforshee> ogra_: which device?
[13:51] <ogra_> maguro
[13:51] <popey> phone app is so laggy
[13:51] <mfisch> popey: whats wrong with upstart
[13:51] <ogra_> mfisch, upstart is fine
[13:51]  * popey points mfisch at ogra_ 
[13:52] <ogra_> mfisch, but you dropped to many env vars
[13:52] <ogra_> sforshee, i dont think the var has much to do with Qt ... but with telling the platform api to talk to hybris
[13:53] <sforshee> ogra_: then it seems poorly named
[13:53] <ogra_> definitely :)
[13:53] <sforshee> anyway, I'll add it just to be on the safe side
[13:53] <ogra_> i guess rsalveti can tell us more about it ... or ricmm_
[13:53] <popey> ogra_: 20130711.1 seems good to me
[13:53] <ogra_> k
[13:53] <ogra_> still syncing
[13:54] <ogra_> but if powerd DTRT for you i think i can just mark it good ... i dont expect regressions on maguro
[13:55] <didrocks> sil2100: have you proposed the python-upa change?
[13:55] <ogra_> ah, my sync is done
[14:01] <sil2100> didrocks: uno momento
[14:03] <ogra_> popey, 20130711.1 maked good
[14:03] <ogra_> (maguro is fine too)
[14:03] <popey> nice one
[14:03] <mfisch> Saviq: whats the eta for the dash search to be enabled?
[14:04] <Saviq> mfisch, I'd say just over a week
[14:04] <Saviq> mfisch, so around midweek 30
[14:05] <mhall119> fginther: would it be possible to build the core apps for Precise?
[14:05] <sforshee> ogra_, mfisch: MR has been updated
[14:05] <fginther> mhall119, we can add that
[14:06] <mhall119> thanks fginther
[14:06] <sforshee> ogra_: the power button still worked for me on maguro without the QT var, but better safe than sorry I guess
[14:06] <fginther> mhall119, assuming thing build :-)
[14:06] <mhall119> I wonder if there's any purpose in keeping quantal builds of the core apps
[14:06] <ogra_> well, let me drop it again
[14:06] <mfisch> Saviq: great, thanks
[14:07] <fginther> mhall119, dropping quantal would probably be a good idea, save some lp resources
[14:07] <popey> uhm
[14:07] <popey> quantal is a supported release
[14:07] <sforshee> ogra_: the only caveat is that my image was a few days old, I'm downloading today's right now
[14:07] <mhall119> is it still?
[14:08] <ogra_> wow, my maguro is in a reboot loop
[14:08] <fginther> popey, we can keep it :-)
[14:09] <popey> mhall119: till 14.04 surely?
[14:09] <popey> 18 months
[14:09] <mhall119> I thought we started 9 months with quantal, or was it raring?
[14:09] <pipedream> raring
[14:09] <popey> https://wiki.ubuntu.com/Releases
[14:09] <mhall119> ok
[14:09] <popey> the wiki never lies
[14:09] <popey> *cough*
[14:09] <ogra_> apw, rtg, do you guys have a bug for this one http://paste.ubuntu.com/5865023/ ?
[14:10] <ogra_> sforshee, weird ... seems to work with the var dropped this time
[14:10] <pipedream> purdy pictures https://wiki.ubuntu.com/LTS of release dates
[14:11] <rtg> ogra_, nope
[14:11] <apw> ogra_, not seen that one before
[14:11] <apw> ppisati, ^^ have you seen that one ?
[14:12] <ogra_> sforshee, drop it, no idea why it works now without it ... it definitely didnt before, i tried several times
[14:12] <ppisati> apw: nope, first time
[14:12] <ogra_> apw, could be alsa on the ubuntu side ... i had it before but didnnt file a bug
[14:12] <apw> ogra_, so intermittent then
[14:13] <ogra_> (alsa being the trigger when loading the config ... but the asoc driver should still not kill the phone imho)
[14:13] <mhall119> rsalveti: https://code.launchpad.net/~mhall119/ubuntu-seeds/ubuntu-touch-sudoku-rename/+merge/173729 needs to land now, the new packages are in the PPA
[14:13] <ogra_> it causes a hard reboot
[14:13] <mhall119> rsalveti: also, ubuntu-calendar-app has been renamed to calendar-app
[14:13] <apw> rtg, so it seems panic of any kind is a hard re
[14:14] <apw> reboot, i guess that is a deliberate thing cause phones don't have a real hard reset
[14:14] <ogra_> yeah
[14:14] <rtg> apw, NULL derefs certainly seem so
[14:14] <ogra_> apw, the good thing is that you have the ram console so you can check the dmesg from the crashed boot
[14:15] <ogra_> (thats where i fished out the log)
[14:15] <ogra_> but yeah, android kernels are all set to automatically reboot on panic
[14:15] <ogra_> you can force that off via sysfs if you like your phone to hang :)
[14:16] <ogra_> plars_, tell me if you are around
[14:16] <plars> ogra_: hi
[14:17] <ogra_> plars, hey, so the change we made that IS had to apply wasnt complete
[14:17] <plars> ogra_: ok, any estimate on when we might be able to get the build stamp in that way?
[14:17] <ogra_> i'm just working on a fix for this ... that should be in livecd-rootfs today ... but will again have to wait for IS
[14:17] <plars> ogra_: understand
[14:18] <ogra_> so it depends on how fast IS processes the RT
[14:18] <ogra_> last time took three days or so
[14:18] <plars> ogra_: how about the way images move to pending? does the directory get created, and they are copied in as we get them, or do we copy them all, then flip the name of the directory all at once? Something else?
[14:19] <plars> ogra_: this is about the other problem I'm having, where I see the md5sum file change, but the images aren't quite available yet
[14:19] <ogra_> i think atm it is a symlink
[14:19] <plars> ok, so it *should* all be available as soon as one file changes I would think
[14:19] <ogra_> which gets moved to /current if the tests succeed
[14:19] <ogra_> but it doesnt have to be a symlink ...
[14:19] <plars> ogra_: well, not yet... at the moment it should be going to both current and pending
[14:20] <ogra_> no, we stopped that after a few desasters with unusable images
[14:20] <plars> ogra_: but we have to make sure it all works reliably, then we turn on another job that tells it to make the link in current if everything passes
[14:20] <ogra_> a new build only goes to pending atm
[14:20] <ogra_> i manually release it once we manually tested it
[14:20] <plars> ogra_: ok, that wasn't coming from me then, not sure who was doing that
[14:20] <ogra_> i think the hooks into your side are in place
[14:21] <ogra_> afaik cjwatson added them a while ago
[14:21] <ogra_> but we were overriding them or so, so it just went to both (pending and current)
[14:21] <ogra_> this was changed this week
[14:22] <plars> ogra_: but right now we still see lots of silly failures, for instance the first image that came out today, it saw the 20130711 image show up and downloaded the 20130710 image instead (this is the problem I was just talking about)
[14:22] <plars> on top of that, it failed because phablet-flash got 404 trying to download the image
[14:23] <ogra_> plars, i dont get why
[14:23] <cjwatson> ogra_: is the build-stamp you're trying to pass through livecd-rootfs *just* for outputting a file in the publication directory?
[14:23] <ogra_> 20130711 was never released to /current
[14:23] <plars> ogra_: I look in pending
[14:23] <ogra_> cjwatson, and for the in-image /var/log/installer/media-info
[14:24] <cjwatson> ah, ok, so it does need to go through livecd-rootfs
[14:24] <ogra_> cjwatson, this part works fine ...
[14:24] <cjwatson> you shouldn't need to wait for that to put it in the cdimage output directory though :)
[14:24] <plars> ogra_: because if I'm not testing from pending, then we'll never get to where we can call the script to copy to current once it works reliably
[14:24] <ogra_> but i'm struggling with the .id atm since my testbuiolds fail all the time due to different issues
[14:24] <cjwatson> ogra_: I could take care of the .id bit
[14:24] <ogra_> cjwatson, no, i dont
[14:24] <ogra_> cjwatson, ok, then let me upload the media-info stuff
[14:25] <cjwatson> plars: pending is flipped atomically on the cdimage master, but there's no way for us to sync it atomically to cdimage.u.c (which is a mirror)
[14:25] <ogra_> thats definitely working and tested now
[14:25] <ogra_> cjwatson, it isnt flipped automatically atm
[14:25] <cjwatson> ogra_: pending, not current.  please let me finish explaining this :)
[14:26] <cjwatson> I'm not talking about what you think I'm talking about ...
[14:26] <ogra_> ok
[14:26]  * ogra_ is quiet
[14:26] <cjwatson> plars: so there is certainly a race from your side when you notice an update in jenkins.  One suggestion I made to gema on Tuesday was that you could use a rather careful rsync call to find out what the pending symlink points to, and then rsync from that directory, to eliminate the race
[14:27] <cjwatson> plars: but I'm not sure if that's totally right.  It's a tricky one
[14:27] <plars> cjwatson: what's odd, is that we watch the same file for smoke testing on x86 images without seeing this problem
[14:28] <cjwatson> plars: it's a race, you'll only get unlucky sometimes
[14:28] <plars> cjwatson: is there some difference in the way touch images get into pending vs x86 images?
[14:28] <cjwatson> plars: no, just luck
[14:28] <plars> we get unlucky often on touch imgaes, and I don't recall ever seeing this in x86 smoke testing is all
[14:28] <cjwatson> plars: it just depends on whether you happen to rsync at the time when cdimage.u.c is populating
[14:28] <cjwatson> It could be size-dependent, or time-of-day-dependent, or ...
[14:29] <cjwatson> There's no fundamental difference that I can think of in play, and the reason I suspect you're seeing this would apply to both
[14:29] <cjwatson> It might well also be that this *is* happening to you sometimes on x86, but it's generally not causing failures so you don't notice
[14:30] <cjwatson> But phablet-flash is probably more pernickety
[14:30] <alecu> cjwatson: hi! I'm trying to figure out how to get the list of installed click packages.
[14:30] <cjwatson> alecu: you can't yet
[14:31] <cjwatson> alecu: I'm putting all that stuff together at the moment
[14:31] <stgraber> ogra_, rsalveti, cjwatson, slangasek: So looks like I resolved the last bug in my import-cdimage script, I have now added it to cron on nusakan (running once an hour), so touch images should automatically get converted and published to system-image.u.c
[14:31] <alecu> cjwatson: I need something like that in the "available-to-install click pakcages scope", to filter out the ones that are already installed.
[14:31] <alecu> cjwatson: ah, great.
[14:31] <cjwatson> alecu: I'll have it for you by next week or so - it'll be "click list", or probably a PackageKit-based D-Bus call
[14:32] <alecu> cjwatson: sounds good
[14:33] <cjwatson> plars: the other (simpler in software, more complex in deployment) possibility is for you to ask for access to rsync directly from nusakan rather than from cdimage.ubuntu.com
[14:34] <cjwatson> plars: that way you wouldn't have to cope with non-atomic updates of the pending symlink
[14:34] <plars> cjwatson: well, I'm using the phablet-tools to deploy these devices. so rsyncing wouldn't help me much unfortunately
[14:34] <plars> phablet-flash pulls over http
[14:34] <plars> and I don't think it currently allows you to specify another location
[14:35] <cjwatson> plars: You could just spin until the directory is fully populated, I suppose ...
[14:35] <cjwatson> Or we could see if IS can improve the way their mirroring of cdimage works, with a two-pass sync or something
[14:35] <slangasek> stgraber: nice!
[14:36] <plars> cjwatson: yeah, I'm trying to see if there's something more deterministic I can use to be sure it's ready, I haven't actually *seen* it in this state, I'm just going by what I see happening after the job runs
[14:36] <cjwatson> stgraber: Great, thanks
[14:36] <cjwatson> plars: I often see the directory semi-populated just after a push
[14:36] <cjwatson> Though the older images are more usually missing than old
[14:37] <cjwatson> Oh, but there are multiple cdimage.u.c servers - one IPv4, three IPv6
[14:37] <cjwatson> (at the moment, it varies)
[14:37] <cjwatson> So really, you can't guarantee that multiple requests will go to the same one
[14:37] <cjwatson> So I think the only reliable approach is:
[14:38] <cjwatson>  (a) rsync -l the pending symlink, readlink it to find out what the build ID is
[14:38] <cjwatson>  (b) pass that build ID to phablet-flash
[14:38] <ogra_> cjwatson, http://paste.ubuntu.com/5865116/ ... just for a final eyballing
[14:38] <ogra_> *eye
[14:38] <cjwatson>  (c) make sure phablet-flash retries a few times if the file is missing (perhaps)
[14:39] <cjwatson> ogra_: Looks OK, but delete the useless NOW=${NOW} visible in that patch context
[14:39] <ogra_> ooops
[14:41] <mhall119> sergiusens: ping
[14:41] <sergiusens> mhall119: pong
[14:41] <mhall119> hey, the click packaging for the core apps, is that something that should live in the bzr branch for the project?
[14:42] <sergiusens> mhall119: ideally yes, at least the manifests ... today the whole infra depends on the debian packaging though
[14:43] <sergiusens> so I strip that out on _build_ time
[14:43] <cjwatson> mhall119: It's like one file
[14:43] <cjwatson> I shouldn't expect it would be painful to include even if it's ignored ...
[14:43] <sergiusens> cjwatson: mhall119 I plan to MR it in
[14:45] <davmor2> popey: is it safe to reflash now?
[14:45] <mhall119> sergiusens: cool, I'm looking forward to seeing click stuff in action
[14:46] <popey> davmor2: yes
[14:46] <mhall119> cjwatson: will we be able to host click packages in a PPA?
[14:46] <ogra_> mhall119, popey, what happened to sudokutouchgame ?
[14:46] <mhall119> ogra_: it's now called sudoku-app
[14:46] <mhall119> ogra_: https://code.launchpad.net/~mhall119/ubuntu-seeds/ubuntu-touch-sudoku-rename/+merge/173729
[14:46] <ogra_> would be nice if someone could reflect that in the seeds in the future
[14:47] <mhall119> ogra_: see above MP
[14:47] <cjwatson> mhall119: Not currently planned
[14:47] <davmor2> popey: ta
[14:47] <cjwatson> mhall119: I should think it's possible and we might do it, but probably not for 13.10
[14:48] <ogra_> mhall119, oh, thanks
[14:48]  * ogra_ starts over regenerating seeds and meta 
[14:51] <cjwatson> seb128: Do you think https://bugs.freedesktop.org/show_bug.cgi?id=66689 is the sort of thing we could apply as a distro patch in advance of upstream taking it, or is that evil?
[14:52] <seb128> cjwatson, I'm happy to see it distro patched ... do you want me to backport or do you have an upload ready for it?
[14:52] <didrocks> sil2100: uno momento finished? ;)
[14:52] <cjwatson> seb128: I don't have an upload ready, sorry
[14:53] <seb128> cjwatson, no worry, let me do it, that will do a nice change of the qt stuff I'm banging my head against for an hour ;-)
[14:53] <sil2100> didrocks: yes, well, basically ;p I had a chat with kenvandine and seb128 and I made it differently ;)
[14:53] <sil2100> https://code.launchpad.net/~sil2100/autopilot/fix_autopilot-touch/+merge/174219
[14:53] <sil2100> Since the dummy-package idea was not so clean when trying to use the same source package, so seb128 recommended this
[14:53] <sil2100> He said it's fine that we're Arch: any!
[14:54] <didrocks> seb128: sneaky :p
[14:54] <seb128> didrocks, roh?
[14:55] <seb128> didrocks, that's the easiest way imho :p
[14:55] <xnox> I think there should be people around here who'd know =) so I'm looking at the indicators-client to "borrow" the networking plugin into the system settings, it looks like it's wrapped with a ChewieUI, how would that integrate into the system settings app?
[14:55] <didrocks> sil2100: seb128: I'm fine with that, I would prefer the dummy package approach, but anyway, it's not the first one :)
[14:55] <cjwatson> seb128: heh
[14:55] <xnox> is there a generic "load in a chewie" the design is slightly different, thus some tweaks are needed in the settings instead of the indicator.
[14:55] <xnox> furthermore, i'd need the same component again for out-of-the-box app =)
[14:56] <sil2100> didrocks: I wanted one too! But to make it non-hacky, I would have to create a separate source package or hack the debian/rules with if-conditionals for architecture detection ;p Which looked uglyyy
[14:57] <didrocks> sil2100: or having a .install.armhf -> .install in debian/rules
[14:57] <sil2100> didrocks: it would still try building the armhf bits on non-armhf
[14:57] <sil2100> We would have to ifdef the sources then ;p
[14:59] <cyphermox> stgraber: you're still working on the mountpoints stuff?
[14:59] <cyphermox> rsalveti: ^
[14:59] <didrocks> sil2100: or override dh_auto_build
[14:59] <cyphermox> I'd need an extra mount from Android in Ubuntu for the maguro:
[14:59] <didrocks> sil2100: but yeah, way more complicated, let's go that road :)
[14:59] <cyphermox>  .  /dev/mmcblk0p3	/factory	ext4	ro,noatime,nodiratime,errors=remount-ro 0 0
[15:00] <stgraber> cyphermox: in my images, all the android partitions are mounted in /android, so I'd expect /android/factory to exist there
[15:00] <sil2100> ;)
[15:00] <cyphermox> ok
[15:00] <sil2100> Let me ask someone from autopilot to approve that
[15:01] <cyphermox> stgraber: on the current images I don't have a /android though
[15:01] <stgraber> cyphermox: we can then symlink that to /factory but I'm really annoyed by the polution of / on the touch devices so would really like hybris to get some env variable we can set
[15:01] <cyphermox> stgraber: I'm fine with that
[15:01] <stgraber> cyphermox: correct because the current images aren't the loop-mounted ones I'm working on
[15:01] <cyphermox> I'll try to mount it there, and see if I can change the property that needs this
[15:03] <stgraber> rsalveti: not to put any more pressure on you but do you have any kind of ETA for being able to tell hybris to look into something other than / for the Android partitions? would be great if we could get rid of the / polution at the same time as we switch to the read-only images
[15:04] <stgraber> rsalveti: I guess something like ANDROID_ROOT in the environment would be reasonable with it defaulting to / when unset
[15:04] <stgraber> we'd then need to patch some non-hybris stuff like NM to respect it too but that should be simple enough
[15:05] <ogra_> stgraber, lets hope that none of the binary drivers have hardcoded /system in them
[15:05] <stgraber> ogra_: none of the binary drivers are running in the Ubuntu side
[15:05] <ogra_> well they get talked to by userspace apps on the ubuntu side
[15:05] <ogra_> see the powerd issues we had today
[15:06] <stgraber> sure, but those apps are open source and so can be changed to respect ANDROID_ROOT
[15:06] <ogra_> (input wont work if you dont export ANDROID_ROOT=/system)
[15:07] <didrocks> stgraber: thanks!
[15:07] <stgraber> ogra_: ah, ok, bad choice of environment variable name then if ANDROID_ROOT already rexists, maybe ANDROID_PARTITIONS would be better then
[15:07] <didrocks> sil2100: thanks!
[15:07] <ogra_> stgraber, the android input layer seems to expect it that way
[15:07] <didrocks> stgraber: thanks you too (for a future request, you owe me one ;))
[15:07] <stgraber> didrocks: ;)
[15:07] <ogra_> stgraber, and that is full of binary stuff i think
[15:09] <gema> didrocks: we have the hardware ordered and it will be in the lab tomorrow, in the meantime we are preparing a machine for you to have your devices hooked to
[15:10] <esigolo> flashing i9000B
[15:10] <ogra_> stgraber, oh and look in the closed channel, seems BT wont work either if you dont have /factory
[15:10] <sil2100> didrocks: np, approved by Omer ;)
[15:10] <stgraber> ogra_: I'm not talking about changing anything to the fs layout in the container, only changing our own bits to look into a different base path (/android instead of /). The only cases where that'd be a problem would be if 1) we get paths from the blobs and just assume they're right or 2) we run binary blobs in the Ubuntu side
[15:10] <didrocks> gema: excellent news! thanks :)
[15:10] <ogra_> stgraber, i'm not sure if it is so clever to not use the android mountpoint setup on the ubuntu side
[15:11] <ogra_> stgraber, well apparently it already causes probs ..
[15:11] <stgraber> ogra_: well, our current setup looks like a huge hack to me, we basically try to make everyone think that Android and Ubuntu share the same rootfs, and they don't
[15:12] <stgraber> it's just a matter of time before we get a path conflict between the two
[15:13] <stgraber> accessing the Android paths through /android makes this much cleaner and sure we'll find bugs and will need to fix them, but at least we won't have stuff randomly blowing up later and it'll be much much easier to figure out where the various bits are coming from
[15:14] <stgraber> slangasek: any opinion? ^
[15:15] <slangasek> stgraber: well, personally I don't see why we should rule out having them share the same fs over the long term
[15:15] <ogra_> i dont care about the whole FS
[15:15] <ogra_> but there are certain paths the blobs assume
[15:15] <slangasek> currently there are some vaguely-defined issues with Ubuntu and Android colliding on the filesystem... but I think those are solvable over the longer term
[15:15] <ogra_>  /system /vendor ... some use /factory
[15:16]  * slangasek nods
[15:16] <ogra_> the container can live where you like it
[15:16] <plars> ogra_, cjwatson: I'd like to do some tests to make sure that the job for mark-current works for touch images. I'm going to be out next week, so once some other pieces land, if others need to turn it on I'd like all the pieces to be there and working
[15:16] <ogra_> but we need to make these paths available
[15:16] <ogra_> plars, i'm using mark-current since monday
[15:16] <cjwatson> plars: I've already verified that the cdimage end works, so it's just the communication with your end
[15:16] <ogra_> it DTRT when i call it manually at least
[15:17] <stgraber> slangasek: the actual list of paths appears to be device-dependent so having those directoriees shipped in the hardware-independent image seems weird to me
[15:17] <plars> ogra_: what options do I need to call it with? Can I do it per device? or is it all or nothing?
[15:17] <ogra_> mark-current -p ubuntu-touch -s saucy -i daily-preinstalled -a armhf BUILD-ID
[15:17] <plars> cjwatson: I was able to call with --help just now, so I know it *can * work, which is nice :)
[15:17] <ogra_> (BUILD-ID obviously being the versioned dir)
[15:17] <plars> ogra_: so this is going to depend on us getting th proper build-id in any case
[15:17] <stgraber> slangasek: my other concern is that with the new partitioning/loop-images, /data != Android's /data (which is actually /data/android-data) so we may get into weird cases if something attempts to use /data thinking it's the same asAndroid's
[15:17] <ogra_> plars, which rsync -l will give you
[15:18] <slangasek> stgraber: well, I assume that things are not allowed to use /data
[15:18] <slangasek> because /data is for user data
[15:18] <plars> ogra_: and I guess it is all or nothing, so for instance if mako passes and grouper fails, we can't tell it to mark the mako image current
[15:18] <slangasek> as for the paths, there may be variation between devices, but isn't the superset of paths used well-defined from the android side? (ogra?)
[15:18] <cjwatson> plars: So it'll be fine then
[15:18] <stgraber> slangasek: and then we have the obvious problem (though AFAIK we haven't actually found any of those yet) where something on the Ubuntu side would like to access say /etc/fstab which exists in both
[15:18] <cjwatson> plars: It's all or nothing, yes
[15:18] <plars> hmm, I'll have to see how I can check for that
[15:18] <ogra_> plars, atm its all or nothing, yeah
[15:19] <plars> I'm sure I can work around it somehow
[15:19] <slangasek> stgraber: sorry, I don't understand what you mean
[15:19] <stgraber> slangasek: /data seems to be used for way more than userdata in Android... things like wireless firmware and wireless configuration are stored there on the nexus4
[15:19] <cjwatson> plars: The various platforms share files, so we can't promote one and not another
[15:19] <ogra_> plars, though due to the nature of the image it will be a very very rare case that you have only one broken subarch
[15:19] <ogra_> plars, rsync -l rsync://cdimage.ubuntu.com/cdimage/ubuntu-touch/daily-preinstalled/|grep pending
[15:19] <plars> ogra_, cjwatson: true
[15:19] <ogra_> that works for me
[15:19] <slangasek> stgraber: well, configuration yes
[15:20] <slangasek> stgraber: oh, why is /data != /data?  Is that for the rootfs loop-mount case?
[15:20] <ogra_> (might need a different url from the lab indeed ... and some post processing of the output)
[15:20] <ogra_> slangasek, yeah, it is well defined ... usually the dirs i listed above plus -data
[15:20] <ogra_> */data
[15:21] <slangasek> ogra_: is that actually defined in some android filesystem standard, or is it just "these are the only directories seen in the wild so far"?
[15:21] <ogra_> slangasek, well, for me its the latter, but i bet there is some kind of policy i just havent read yet :)
[15:22] <slangasek> then that's not "well-defined"
[15:22] <stgraber> slangasek: /data is the raw userdata partition, which then contains a bunch of directories (android-data, user-data, system-data, ...) that are then bind-mounted into the right places. Having /data == /data would mean that Android would directly create a dozen entries right at the root of the data partition which may or may not conflicts with some of our entries based on devices and how the binary blobs feel on a specific day
[15:23] <slangasek> stgraber: so why are we not doing the same thing with /data on the Ubuntu side that Android does with it?
[15:23] <ogra_> stgraber, you are aware that the majority of android drivers expects the subdirs in /data to store theit variable files ?
[15:23] <ogra_> and for drivers we use on both sides we will definitely need that
[15:24] <ogra_> (we have bits that get initialized in android but managed afterwards in ubuntu)
[15:24] <stgraber> ogra_: which is exactly why I suggested the ANDROID_MOUNTS (or whathever we call it) environment variable that can point to the location where we have the Android view of those partitions (in my case, /android where /android/data == Android's /data)
[15:25] <ogra_> i doubt that will fly
[15:25] <ogra_> happy to be proven wrong ... but it sounds a bit like we are artificially introducing problems for FHS cleanness
[15:26] <stgraber> slangasek: you mean, let any software create random entries everywhere with no apparent kind of structure? Sure we could do that and hope that we never get any kind of conflict or never have to actually go look at those by hand
[15:26] <ogra_> Mir wont start if you dont have the EGL/GLES libs in the right place
[15:26] <ogra_> (which is underneath /vendor)
[15:27] <slangasek> stgraber: I mean, why is Ubuntu's /data anything different from Android's /data?  I don't see why they wouldn't be the same *by definition*, given that /data as a mountpoint only exists for Android compatibility
[15:27] <ogra_> BT seems to expect /factory to be able to do stuff
[15:27] <stgraber> ogra_: and if Mir is made to respect ANDROID_MOUNTS, it'll look into $ANDROID_MOUNTS/vendor which will perfectly work
[15:27] <slangasek> so if we're mounting something at Ubuntu's /data that we're concerned about being polluted by android... then we have the wrong thing mounted at /data
[15:27] <ogra_> stgraber, and the blobs ?
[15:27] <ogra_> stgraber, they run on both sides
[15:27] <ogra_> initialized on android, used on ubuntu
[15:28] <slangasek> stgraber: right, the GL drivers themselves may need filesystem access according to Android's layout.
[15:28] <stgraber> hmm, right, I mentioned that as being a blocker earlier, if we do run binary blobs in Ubuntu (and not in the Android container) that hardcode those paths, then we indeed can't do it
[15:28] <slangasek> we certainly do
[15:29] <ogra_> stgraber, thats what i meant :)
[15:31] <stgraber> ok, I'll have to do a few changes then, basically stop using /data as the userdata mount point, instead use /userdata and make /data a symlink to /userdata/android-data, same of all the other random bits from Android
[15:31] <ogra_> we could probably route all EGL through hybris but i bet that would have quite some performance impact
[15:32]  * stgraber starts changing lxc-android-config and initramfs-tools-ubuntu-touch for that
[15:35] <stgraber> ogra_: /cache, /data, /factory, /firmware, /persist, /system, /vendor
[15:35] <stgraber> ogra_: anything I missed?
[15:35] <stgraber> note that if a path doesn't exist, those will be dangling symlinks
[15:36] <stgraber> (so /factory at least will be a dangling symlink on mako)
[15:36] <ogra_> stgraber, not from the top of my head
[15:36] <ogra_> yeah, some are device specific
[15:36] <ogra_> mako has some others thogh ... that we didnt need yet
[15:37] <stgraber> ogra_: not that are listed in its fstab, the mako fstab only contains cache, data, firmware, persist and system
[15:37] <ogra_> ah, fine then
[15:44] <dpm> hi sergiusens, I just noticed your announcement about "Initial click packages for all community core apps have been created and added to Jenkins, next step is to land on the image." Good work! Is there anything we should bear in mind/change in terms of how the core apps are built in our daily PPA? How and where are the click packages being generated?
[15:45] <sergiusens> dpm: click today has no PPA concept, right now they are all here: https://jenkins.qa.ubuntu.com/search/?q=click
[15:46] <sergiusens> dpm: I pick them up from trunk daily. Today our testing strategy depends on generation autopilot debian packages, we probably need a migration path away from that to strip out the debian stuff from there (should be simple)
[15:46] <sergiusens> I also modify (on the fly) the desktop files to remove the hardocded paths
[15:47] <stgraber> ogra_: uploaded both lxc-android-config and initramfs-tools-ubuntu-touch
[15:47] <sergiusens> but in the end that would need integration with upstart user sessions
[15:47] <ogra_> stgraber, thanks
[15:48] <zoktar> is there a way to check battery status from an ssh login ?
[15:48] <dpm> sergiusens, ok, cool. Let us know if we need to change anything in trunk to make it easier to generate the click packages
[15:48] <dpm> popey, mhall119 ^^
[15:48] <popey> ok
[15:51] <stgraber> ogra_: I'll want an image rebuild once everything has published, is it simply a matter of triggering a livefs build from nusakan?
[15:52] <ogra_> just grep ubuntu-touch from the crontab
[15:52] <ogra_> and make sure someone does the manually testing to set the current symlink right
[15:52] <ogra_> *manual testing
[15:53] <ogra_> the command for setting pending to current is in /home/ogra/README.mark-current
[15:53] <ogra_> just run that of all arches have been tested
[15:53] <ogra_> *if
[16:01] <stgraber> ogra_: well, as my changes only affect my images and my importer doesn't look at the pending/current flag, I can also just as well save myself the trouble of testing it on standard flipped and just not marking it as tested
[16:02] <rickspencer3> awe_, fwiw you SIM PIN unlock script worked perfectly for me
[16:02] <stgraber> btw, barry's new system-image-cli updating my phone by 4 versions just using deltas: http://paste.ubuntu.com/5865338/
[16:02] <ogra_> stgraber, if you rebuild, the new build will be stuck in pending
[16:03] <ogra_> stgraber, due to no automated testing happening, every build has to be manually tested
[16:03] <stgraber> ogra_: sure, and? everyone will keep downloading the old one with phablet-flash and my importer will import it anyway (as it ignores pending/current), what's the problem?
[16:03] <ogra_> no
[16:03] <ogra_> phablet-flash doesnt use /current yet
[16:04] <ogra_> thats why testing is critical until sergiusens fixed that
[16:04] <ogra_> so we can at least roll back before to many people have the broken image
[16:04] <elopio> jppiiroinen: ping.
[16:04] <stgraber> ah, ok. I'll ping here for someone to test on standard flipped then
[16:04] <ogra_> currently every new build has to be tested manually immediately
[16:05] <ogra_> and rolled back if broken
[16:05] <ogra_> (of fixed if its fast to fix)
[16:06] <stgraber> cjwatson: hey, is there a way to check whether an older build was considered as good by Jenkins (or the manual tool)?
[16:06] <ogra_> jenkins doesnt do any tests :) thats the issue
[16:06] <stgraber> cjwatson: the reason I ask is that my importer doesn't look at current/pending but instead imports any build ID it didn't see previously, so ideally I'd want to know the testing status for any of those
[16:07] <ogra_> stgraber, pull from /current
[16:07] <ogra_> stgraber, and to see if there is a new build, just compare the last and /currten SHA256SUM
[16:08] <ogra_> s/last/local/
[16:08] <stgraber> ogra_: not that simple, my tool supports importing a build history, so multiple existing builds. I'd like to know for each of those whether they were considered good.
[16:08] <ogra_> heh
[16:08] <mhall119> sergiusens: why do you need to modify the .desktop file path?
[16:09] <ogra_> you ask for advanced features of a tool that doesnt even work yet :)
[16:09] <mhall119> to click packages get installed somewhere else?
[16:09] <stgraber> ogra_: basically looking for a .marked-good stamp file or similar in the build directory, if we don't have that somewhere, I'll just add it as it's simple and useful (even for non-touch images, so we can know which of the previous builds were considered good)
[16:09] <ogra_> stgraber, thats a great idea, do it !
[16:09] <ogra_> and no, we dont have that
[16:10] <ogra_> the only way to distinguish is /pending vs /current atm
[16:10] <stgraber> ok, I'll add that then, then it'll be a simple two extra lines of python for my importer to skip any non-tested image
[16:11]  * ogra_ is ouot for 1h
[16:11] <sergiusens> mhall119: click packages get installed in /opt/com.ubuntu.click/{APPNAME}/{VERSION}
[16:11] <sergiusens> mhall119: remember the /usr will be readonly
[16:12] <mhall119> sergiusens: hmmm, is there a way to put an install path variable in the .desktop that the installer will replace with the real path?
[16:12] <sergiusens> the path may change though according to cjwatson
[16:12] <mhall119> all the more reason for a variable
[16:12] <sergiusens> mhall119: there's supposed to be a hook that does the right provisioning, the strategy for the is still unbeknownst to me
[16:16] <art_> can we put ubuntu mobile on gsIII
[16:17] <art_> bueller...bueller...
[16:22] <esigolo> i'm trying to boot up after flash and got only a black screen
[16:23] <davmor2> ogra_, sergiusens, popey: Muhahaha  todays image includes the nice button that switch off wifi and 3g,  oh except the 3g stays connected here :)
[16:23] <esigolo> logcat shows failed to read /data/.layout_version
[16:23] <esigolo> galaxy s i9000B
[16:28] <popey> davmor2: oh, it does?
[16:28] <popey> oooh
[16:30] <davmor2> popey: you're welcome :)
[16:30] <popey> :D
[16:30] <davmor2> popey: just as well you didn't claim it work perfectly right :D
[16:31]  * davmor2 now waits for gema 's bug
[16:31] <davmor2> popey: it does weird and wonderful things if you knock both off and only switch the wifi back on too :)
[16:33] <davmor2> popey: can I have a quick reminder on what the command is to take a screenshot please, ta.
[16:35] <pmcgowan> davmor2, popey I tried it yesterday and it turned my 3g off for sure
[16:35] <pmcgowan> still getting the latest
[16:40] <davmor2> pmcgowan: I'm on galaxy nexus here if that helps
[16:41] <mhall119> ogra_: rsalveti: https://code.launchpad.net/~mhall119/ubuntu-seeds/rename-calendar-app/+merge/174243
[16:41] <popey> davmor2: seeing this? http://popey.com/~alan/device-2013-07-11-174120.png
[16:41] <mhall119> ogra_: I'll wait for that to land before deleting the old packages this time :)
[16:42] <popey> Note two "Mobile data" stanzas
[16:42] <cjwatson> stgraber: I'm not sure.  You want plars or somebody I guess ...
[16:42] <cjwatson> stgraber: (cdimage doesn't record any of this except by moving symlinks around)
[16:43] <cjwatson> stgraber: Recording it somewhere other than cdimage/log/mark-current.log is probably reasonable, yes
[16:43] <cjwatson> mhall119: No variables; you should use only relative paths in the .desktop for a Click package.
[16:43] <popey> davmor2: http://popey.com/~alan/device-2013-07-11-174331.png  getting very confused now
[16:44] <mhall119> cjwatson: relative to what?
[16:44] <cjwatson> mhall119: (Yes, I know that's against the desktop spec.  The idea is for the real .desktop file with full paths to be generated.)
[16:44] <davmor2> popey: I don't get the Wifi names any more just the double mobile switch
[16:44] <cjwatson> mhall119: The app unpack directory.
[16:44] <cjwatson> mhall119: i.e. your top level
[16:44] <popey> davmor2: bug number?
[16:44] <plars> cjwatson, stgraber: couldn't we just have mark-current drop that file in the directory when it's called?
[16:44] <davmor2> popey: I want to take a screenshot to add to it so I haven't written it yet
[16:44] <cjwatson> plars: Well, sure, mark-current can always log in a more machine-readable way if it wants ...
[16:45]  * popey uses his handy "screenshot.sh" script to take screenshots ☻
[16:45] <cjwatson> Or stgraber could parse cdimage/log/mark-current.log
[16:45] <davmor2> popey: hence asking what the command is to take a screenshot
[16:45] <popey> aquarius: oi oi. i need a script like your sss thing which takes an image and stuffs it in U1 and then gives me a sharing url ☻
[16:45] <popey> oh sorry davmor2
[16:46] <davmor2> popey: but feel free to point me at screenshot.sh by all means
[16:46] <popey> http://paste.ubuntu.com/5865478/
[16:47] <davmor2> popey: ta,
[16:48] <aquarius> popey, just a script? that is: you're OK to run it from the command line, say?
[16:51] <popey> aquarius: ya
[16:51] <aquarius> popey, and you're OK with it being python?
[16:51] <popey> i want it on my desktop for when i want to quickly share pics
[16:51] <popey> i dont really care, but!
[16:52] <popey> http://paste.ubuntu.com/5865478/  that is what mine does
[16:52] <aquarius> oh, on your desktop?
[16:52] <popey> yes
[16:52] <popey> i run that and currently then "scp file.png ... " and then give someone the url
[16:52] <popey> which is all very manual. i want to press a button (or run a script) and it give me a copy/pasteable u1 public url
[16:52] <aquarius> popey, so you have full on U1 running, so "stuff it in U1" can be "copy it to ~/Ubuntu One/pictures", gotcha
[16:53] <popey> yes
[16:53] <popey> its a standard 13.04 machine
[16:53] <stgraber> plars: yeah, I'll probably just change mark-current to write a dotfile in the build directory, that way this shouldn't be visible to people browsing cdimage.ubuntu.com but will be easy to find on nusakan without having to do any log parsing
[16:53] <chilicuil> good morning, does anyone know if there is a native sip app for ubuntu touch/ubuntu phone?
[16:54] <popey> chilicuil: not yet
[16:54] <popey> aquarius: http://paste.ubuntu.com/5865513/ thats what i do now
[16:57] <pete-woods> dpm: ping
[16:57] <popey> aquarius: feel free to publish your script and take all the credit ㋛
[17:01] <dpm> hey pete-woods
[17:01] <pete-woods> dpm: do the published API docs automatically update with distro releases of -doc packages?
[17:02] <aquarius> popey, I'm customising a script I've already published ;)
[17:02] <dpm> pete-woods, for the development release or packages in PPAs, the docs are updated daily at midnight
[17:02] <pete-woods> or do I have to nag (poor) you each time I make a change?
[17:03] <dpm> pete-woods, no worries. You only have to nag me if the automatic updates don't happen for any reason :)
[17:03] <pete-woods> dpm: okay, cool, so my docs should automagically update tonight then! nice!
[17:04] <dpm> pete-woods, yeah, I could also increase the frequency to hourly instead of daily if that helps you
[17:05] <pete-woods> dpm: it's not a problem - I just wanted to check. It'd be super-fancy if the upload was triggered by the same process that does the distro / PPA releases, though!
[17:06] <dpm> pete-woods, in any case, I've just updated them manually for you, so you can check them out earlier, enjoy ;)
[17:06] <pete-woods> dpm: sweet. thanks! :D
[17:06] <mhall119> Calculator meeting starting in #ubuntu-touch-meeting
[17:07] <dpm> pete-woods, I agree, and I'm all up for automation, but I'm not sure we can hook up the d.u.c server to the release process
[17:08] <davmor2> popey: I forgot to ask is it the standard network-manager-applet or something else package wise?
[17:08] <pete-woods> dpm: I'm assuming there there's some good reason for that. I really don't know our infrastructure here at all. I'm used to being the mug who has to (literally) hide a server in the server room to run jenkins, etc, on..
[17:09] <aquarius> popey, http://paste.ubuntu.com/5865546/
[17:09] <dpm> pete-woods, no worries :)
[17:09] <davmor2> popey: sorry for the delay push a .deb to launchpad at the same time and didn't want to get confused :)
[17:10] <aquarius> popey, er, except, close the triple quoted string on the first lien :)
[17:11] <pmcgowan> popey, I told renato about the double mobile data thing yesterday
[17:11] <pmcgowan> but did not make a bug, was hoping he would fix and do a new mr
[17:12] <davmor2> pmcgowan: is it standard network manager that is in use or is it something specific to touch I'd like to file a couple of bugs on it
[17:13] <pmcgowan> I think that bug is just the indicator UI
[17:13] <davmor2> pmcgowan: nm-applet even?
[17:13] <pmcgowan> nope
[17:13] <pmcgowan> new stuff
[17:14] <davmor2> pmcgowan: great do you happen to know it's name or do I need to just file against a device?
[17:15] <pmcgowan> davmor2, let me get it for you
[17:16] <davmor2> pmcgowan: thanks
[17:22] <pmcgowan> davmor2, https://launchpad.net/indicators-client
[17:23] <davmor2> pmcgowan: ta
[17:24] <davmor2> pmcgowan: ha nice no way to report a bug :)
[17:24] <pmcgowan> davmor2, let me check if its the server project
[17:25] <pmcgowan> davmor2, the 3g toggle was part of indicator-server
[17:25] <pmcgowan> which is actually going away soon as I recall
[17:26] <davmor2> pmcgowan: https://launchpad.net/indicator-server is not accepting bug reports either :D
[17:27] <pmcgowan> davmor2, oh?
[17:29] <davmor2> pmcgowan: neither of those project have the report a bug button clickable
[17:29] <pmcgowan> davmor2, it is now ;)
[17:30] <pmcgowan> but it is going away soon
[17:30] <pmcgowan> there is a new consolidated implementation
[17:30] <davmor2> pmcgowan: ta
[17:32] <seagle> asl?
[17:33] <awe_> rickspencer3, awesome!  ;)-
[17:33] <rickspencer3> awe_, you guys are just ripping it up
[17:33] <seagle> name?
[17:33] <rickspencer3> I've never seen anything like it
[17:35] <esigolo> 3g autocon already patched?
[17:36] <seagle> name?
[17:57] <aquarius> popey, does that work?
[17:58] <davmor2> popey, pmcgowan: https://bugs.launchpad.net/indicator-server/+bug/1200324  and https://bugs.launchpad.net/indicator-server/+bug/1200322 enjoy move them as you feel fit :)
[18:00] <pmcgowan> davmor2, how did you check the connection status? by accessing the net or command line or both?
[18:02] <davmor2> pmcgowan: opened the web browser and it loaded the home page thought it might be cached so tried a different page, knew I'd been to that page todat so tried a completely random page
[18:02] <pmcgowan> davmor2, ok
[18:03] <davmor2> pmcgowan: ifconfig shows an ip address for rmnet0 too with the indicator disabled
[18:04] <pmcgowan> davmor2, ok maybe its a nexus vs nexus 4 thing
[18:04] <pmcgowan> although I thought it got tested for both
[18:05] <davmor2> pmcgowan: well I'm on the u1 team and have a device of my own so if you need anything testing as long as I can use it still feel free to ping me here it will mail me if I'm away
[18:06] <pmcgowan> davmor2, great thanks
[18:07] <davmor2> pmcgowan: if you need more info on anything as well, just ask I'm happy to grub around getting log files etc :)
[18:15] <davmor2> kenvandine: hey dude I get this on that galaxy nexus http://ubuntuone.com/6JQFVLxMEp3Nx1amdByWAA if I have the terminal open with the keyboard on display and let it sleep when I wake the device I get that.  I see you own the phablet maliit plugin so is this in your realm?
[18:16] <pmcgowan> davmor2, no thats tmoenicke
[18:17] <davmor2> pmcgowan: ah thanks
[18:21] <davmor2> pmcgowan, tmoenicke: maliit and maliit-phablet are another one where you can't file bugs :(
[18:21] <sergiusens> davmor2: against the image for now
[18:22] <mhall119> davmor2: I get it on my nexus 7 too
[18:30] <davmor2> mhall119: https://bugs.launchpad.net/touch-preview-images/+bug/1200332 :)
[18:32] <pmcgowan> davmor2, yeah I filed that one yesterday too ;)
[18:33] <davmor2> pmcgowan: I asked about it ages okay but got called into a meeting and that was the end of that :)
[18:46] <stgraber> rsalveti: can you push: http://paste.ubuntu.com/5865827/ ?
[18:47] <stgraber> rsalveti: and trigger a rebuild once that's landed (not sure how to do that myself). I'm planning an ubuntu-touch rebuild in the next hour or so and would like that change to be part of it.
[18:53] <bfiller> kenvandine: trying to login to google via uoa-create on latest image to test the eds stuff. getting this error: http://pastebin.ubuntu.com/5865845/
[18:55] <sergiusens> stgraber: I can push that patch
[18:56] <stgraber> sergiusens: was just about to ping you! that'd be great!
[18:59] <nik90> Does anyone here know who is working on the browser app?
[18:59] <bfiller> nik90: osomon but he's not on now
[19:00] <nik90> bfiller: ah thanks. Will catch him later
[19:00] <bfiller> nik90: I might be able to help if you have a question
[19:01] <nik90> bfiller: oh great! I would like to know if the address url bar is placed in a toolbar?
[19:01] <nik90> bfiller: or is it a separate Qrectangle or something?
[19:02] <bfiller> nik90: I think it's some sort of custom panel that functions like a toolbar
[19:02] <nik90> bfiller: ok. Because in the clock app, I have a bug where the osk hides the text field.
[19:03] <nik90> bfiller: but popey noticed that it doesnt do the same in the broswer
[19:03] <nik90> so I was wondering if it was a osk bug or clock app
[19:03] <FlowerPot> hi, i just installed ubuntu touch on my nexus 7 however when i now try to boot i just see Google and nothing happens .. any idea how to fix that?
[19:03] <bfiller> nik90: I think there is special code in all the apps to listen for when the osk is made visible and to scroll
[19:03] <bfiller> nik90: which is a pain but necessary atm
[19:04] <bfiller> nik90: let me find a simple example
[19:05] <nik90> bfiller: is there a bug report filed in the osk to fix that? Should Implement this special code which is essentially a temporary hack or wait for the osk developer to fix it on their end?
[19:05] <bfiller> nik90: don't thinks it's an osk bug but rather something that should be built into the sdk
[19:06] <bfiller> nik90: I'd implement it for now as don't know when this will be fixed
[19:06] <nik90> bfiller: ok. I will also parallely let kaleo know about this issue and if necessary report a bug report to track this issue.
[19:08] <nik90> bfiller: where can I find this extra code that I need to add?
[19:09] <bfiller> nik90: phone-app does it in the messages view, as does browser. I'm looking now too
[19:11] <bfiller> nik90: search for onVisibleChanged in phone-app
[19:11] <stgraber> sergiusens: do you know how to kick a new build of the Android bits? (for when you have landed my change)
[19:11] <sergiusens> stgraber: yup
[19:12]  * stgraber is really looking forward to having all that done as packages on LP, finally a build process I'll be familiar with ;)
[19:12] <bfiller> boiko: can you give nik90 a pointer in phone-app where we scroll the entry field in messaging when the osk is shown/hidden?
[19:13] <boiko> bfiller: yep, let me get the code here
[19:14] <bfiller> boiko: thanks
[19:14] <boiko> nik90: so I have this QML item that watches for the keyboard changes: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/Widgets/KeyboardRectangle.qml
[19:15] <nik90> boiko, bfiller: thnx
[19:15] <boiko> nik90: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/DetailViewCommunication/CommunicationView.qml#L235
[19:15] <nik90> boiko: Is Connections just any other qml element?
[19:16] <nik90> boiko: can you explain briefly the logic?
[19:16] <boiko> nik90: you basically anchor the KeyboardRectangle item to the bottom of your view, and then the contents you want to scroll you anchor to the top of the KeyboardRectangle
[19:16] <boiko> nik90: this KeyboardRectangle is a normal item that has the size of the virtual keyboard.
[19:17] <boiko> nik90: when the keyboard is visible it has the height of the keyboard, when the keyboard is hidden, it has a height of 0
[19:17] <boiko> nik90: Connection is part of the QML language, yes
[19:17] <bfiller> boiko: could this be moved generically into the sdk somehow so app developers get the functionality for free?
[19:17] <nik90> boiko: oh so I use the whole KeyboardRectangle.qml file
[19:17] <kenvandine> bfiller, don't use uoa-create anymore
[19:17] <kenvandine> :)
[19:18] <nik90> boiko: I get it now.
[19:18] <boiko> bfiller: maybe, but one should take the time to refactor it as a proper component
[19:18] <boiko> nik90: yep, for now copy it and then at some point it might be part of SDK
[19:18] <nik90> boiko: awesome! Thanks a lot
[19:19] <boiko> nik90: no problems, ping me if you still have problems with it, ok?
[19:19] <bfiller> boiko: seems like setting a hint on the field that you always want to be visible would be desireable
[19:19] <bfiller> kenvandine: how to do it then? no ui for it in system settings
[19:19] <nik90> boiko: sure :)
[19:19] <kenvandine> bfiller, accounts
[19:19] <kenvandine> bfiller, but you need to install the plugin
[19:19] <boiko> bfiller: but how the contents should be scrolled is totally dependent on the view's layout, hard to do something generic there
[19:20] <kenvandine> account-plugin-google
[19:20] <kenvandine> bfiller, ^^
[19:20] <bfiller> kenvandine: cool, I'll try
[19:20] <kenvandine> let me know how it goes
[19:20] <kenvandine> i need to test that myself :)
[19:22] <sergiusens> stgraber: did you use git format-patch for that?
[19:24] <bfiller> kenvandine: I get a UI for google in accounts but the ID field I can't enter anything. It shows 3 checkboxes for EDS as well
[19:24] <sergiusens> stgraber: I applied and building android now
[19:25] <stgraber> sergiusens: thanks!
[19:25] <kenvandine> bfiller,  :/
[19:25] <stgraber> sergiusens: that was a post of git show, probably should have used git format-patch to make it easier to apply
[19:26] <kenvandine> bfiller, the ID should get captured on login
[19:26] <kenvandine> it got mine
[19:26] <kenvandine> that isn't editable
[19:27] <sergiusens> stgraber: yaeh, git am said it could detect the patch :-)
[19:27] <bfiller> kenvandine: I'm not getting prompted to login are you?
[19:27] <stgraber> sergiusens: where can I see when android's done building?
[19:27] <kenvandine> bfiller, i did
[19:28] <kenvandine> bfiller, if you see the EDS entries, it's already logged in
[19:28] <kenvandine> oh
[19:28] <kenvandine> maybe your account got created partially with uoa-create?
[19:28] <kenvandine> bfiller, remove the account and try again
[19:29] <bfiller> kenvandine: ack
[19:33] <bfiller> kenvandine: worked, logged in
[19:37] <bfiller> kenvandine: is there another package I need for the google eds plugin? my google contacts are not showing up in eds after logging in
[19:40] <mhall119> bfiller: I think you still need to manually do the contact sync (unless that's changed recently)
[19:40] <bfiller> mhall119: manually how?
[19:40] <mhall119> using syncevolution
[19:40] <mhall119> following sergiusens's instructions
[19:43] <kenvandine> mhall119, no, that doesn't use the UOA account
[19:43] <kenvandine> bfiller, not sure how to make it use that as the address book
[19:43] <mhall119> kenvandine: but it's still the only way to import contacts isn't it?
[19:43] <kenvandine> we should be able to have online access to google contacts
[19:44] <kenvandine> with UOA
[19:44] <kenvandine> but it'll be  a different eds address book
[19:44] <kenvandine> not sure if maybe the contacts app needs to do something different to query that
[19:46] <kenvandine> bfiller, for example, in gnome-contacts i can change address books
[19:46] <kenvandine> my default one is "Google"
[19:46] <kenvandine> which i think i set ages ago in evolution
[19:46] <WebbyIT> mhall119: can you help me with this? http://91.189.93.70:8080/job/ubuntu-calendar-app-autolanding/5/ I don't understand where is the problem! Thanks in advance :)
[19:48] <mhall119> WebbyIT: give me a minute and I'll take a look
[19:49] <WebbyIT> mhall119: thanks
[19:49] <mhall119> np
[19:54] <AskUbuntu> Can Ubuntu be installed on a Samsung Galaxy Nexus Verizon 4g phone | http://askubuntu.com/q/319051
[19:59] <asac> ogra_: you said that we dont own the task to make phablet-flash support pulling from --pending --current etc.?
[19:59] <asac> who is the guy that would fix that?
[20:00] <popey> asac: sergiusens ?
[20:03] <asac> sergiusens: there?
[20:17] <bfiller> kaleo: http://pastebin.ubuntu.com/5866087/
[20:18] <kaleo> bfiller, thx
[20:19] <kaleo> bfiller, I see
[20:19] <kaleo> bfiller, if boiko can make something a bit generic, it would be welcome in the SDK
[20:19] <kaleo> bfiller, however what we could try is to resize the entire app automatically
[20:19] <kaleo> bfiller, and make it opt-out
[20:20] <kaleo> bfiller, so that if devs want to implement their own relayouting they can
[20:20] <kaleo> bfiller, but by default there would be no overlap
[20:20] <bfiller> kaleo: that would be good
[20:20] <boiko> kaleo: that would be a solution indeed
[20:21] <kaleo> bfiller, can you file a bug? boiko: can you put your code in there?
[20:21] <boiko> kaleo: maybe not really resize the app, but the page? (like having a property on the page saying if it should resize with the keyboard or not
[20:22] <kaleo> boiko, yes, hmmm, I meant the MainView
[20:22] <kaleo> boiko, hmmm
[20:22] <kaleo> boiko, the Page would be smart I think
[20:24] <bfiller> kaleo: yes I'll file
[20:24] <sergiusens> asac: popey am now
[20:24] <kaleo> bfiller, thanks!
[20:24] <mhall119> kaleo: ping
[20:24] <sergiusens> asac: yes, I am supposed to fix that toady
[20:24] <sergiusens> today*
[20:24] <kaleo> mhall119, pong
[20:24]  * kaleo has got some cheese
[20:24]  * kaleo from La Boulangerie
[20:24] <kaleo> YAY!
[20:25] <mhall119> kaleo: QDesktopServices.openUrl() works as expected on desktop, but not on devices, why might that be?
[20:25] <kaleo> mhall119, bug report is ther
[20:25] <kaleo> mhall119, https://bugs.launchpad.net/qtubuntu/+bug/1186556
[20:26] <mhall119> kaleo: right, but my question is why we need a different implementation on Ubuntu Touch than we already have on Ubuntu desktop
[20:26] <mhall119> since presumably they both use XDG standardxs
[20:27] <kaleo> mhall119, because we don't launch apps the same way
[20:27] <mhall119> we don't?
[20:27] <kaleo> mhall119, and also even if we wanted exactly the same way there would still be a tiny bit of code required in qtubuntu to actually do that
[20:27] <kaleo> mhall119, apps are launched with an extra parameter
[20:27] <kaleo> mhall119, --desktop_file_hint
[20:28] <kaleo> mhall119, and another one if they are in the sidestage
[20:28] <kaleo> mhall119, I reckon the fix for the bug would not be very hard anyway
[20:28] <kaleo> mhall119, I also think that we could save on startup time by not using the xdg perl scripts
[20:28] <kaleo> mhall119, (while still respecting the standard of course)
[20:29] <mhall119> ok, I see the bug is critical, do we have any ETA on when it might be worked on?
[20:29] <kaleo> mhall119, I marked it as critical today :)
[20:29] <kaleo> mhall119, I guess we can bump it to high if that prevents the ETA question :)
[20:29] <asac> sergiusens: what will be done?
[20:29] <mhall119> kaleo: nothing can prevent the ETA question, you know that :)
[20:29] <asac> sergiusens: so there is one more requirement that might be supereasy to include in that batch...
[20:30] <asac> sergiusens: we have those "preview images" ... like mir
[20:30] <kaleo> mhall119, as usual, we have a million things to do and it's really hard to plan with the million more new things coming all the time
[20:30] <asac> i want phablet-flash to also be able to take those... like
[20:30] <asac> phablet-flash -r current --overlay URL-TO-REMOTE-OR-LOCAL-PREVIEW-TARBALL
[20:30] <kaleo> mhall119, my guess is that it will have to wait until loicm is free in a few weeks or if you can convince ricmm_ maybe sooner?
[20:30] <asac> sergiusens: notsure if that makes senes
[20:30] <mhall119> while(len(workitems) > 0) { kaleo.fork(); }
[20:31]  * mhall119 hopes that works
[20:31] <kaleo> mhall119, doing that but it takes nine months
[20:31] <sergiusens> asac: as long as the url it sits on is formated correctly the --uri should pick it up
[20:32] <asac> sergiusens: you know what i mean?
[20:32] <mhall119> kaleo: seriously? congrats!
[20:32] <kaleo> mhall119, thanks :)
[20:32] <kaleo> mhall119, 2 months to go
[20:32] <asac> sergiusens: e.g. the preview images only publish the ubuntu parts... while the rest is still on cdimage
[20:32] <asac> sergiusens: does --uri support file:///...
[20:32] <asac> ?
[20:32] <asac> (two questions)
[20:33] <popey> asac: https://bugs.launchpad.net/phablet-tools/+bug/1198147 ☻
[20:33] <sergiusens> asac: yeah, I understand, let me see how easily I can add an override
[20:33] <mhall119> kaleo: do you know yet if it's a C++ or Python developer?
[20:33] <asac> sergiusens: also... if you say "uri is correctly formatted" do you jyust mean having the right URI format like file:///? or really about magic stuff encoded in the path?
[20:34] <sergiusens> popey: only reason I don't add that is because everything on cdimage is in flux, used to have it when we used jenkins if you recall :-)
[20:34] <kaleo> mhall119, locomotive basic
[20:34] <kaleo> mhall119, like her dqd
[20:34] <kaleo> dad
[20:34] <sergiusens> asac: correct stuff at the tip of the uri... but let me get away with that
[20:34] <popey> sure
[20:34] <asac> popey: thats "old" images... i want random url images for our new approach of doing more and more topic/staging images for stuff like MIR
[20:34] <popey> same thing really
[20:34] <asac> or anyone who sets up a nice jenkins job to unpack, hack and repack the tarball
[20:35] <mhall119> kaleo: heh
[20:35] <mhall119> kaleo: as long as she doesn't fall in with the wrong crowds and start using perl
[20:35] <popey> wow locomotive basic, thats a blast from the past
[20:35] <sergiusens> asac: oh, it's a tarball and not an update.zip? I'll fix that
[20:35] <asac> sergiusens: we will will produce stuff on jenkins
[20:36] <kaleo> popey, getting old heh
[20:36] <asac> sergiusens: well use case is: i setup a jenkins job that takes our ubuntu flash, hacks around, repacks it and then i can use phablet flash to try it out or even easily add new utah jobs jobs etc.
[20:36] <asac> i dont know what an update.zip is :)
[20:36] <asac> I think whatever MIR preview jenkins job produces
[20:36] <sergiusens> asac: it has the deploy logic to work from recovery
[20:37] <kaleo> robru, around?
[20:37] <asac> ah. well. i really want to be able to flash such "branch/topic/preview" images
[20:37] <asac> just like we do normally. or is that not reasonable?
[20:37] <asac> let me show what i mean :)
[20:37] <asac> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/
[20:37] <asac> there are a bunch of zips
[20:38] <asac> or .imgs
[20:38] <asac> not sure...
[20:38] <asac> now i got pointed at jenkins job that just produce the saucy-preinstalled-touch-armhf.tar.gz
[20:38] <sergiusens> asac: I think I understand what you want
[20:38] <asac> i ythink
[20:38] <asac> so i want to be able to just use phablet-flash to flash any of such preinstalled tarball
[20:38] <asac> but still use current or 20130701 or whatever other parts i want :)
[20:38] <asac> (default current/latest)
[20:39] <sergiusens> asac: yeah, that tar would be better off for everyone if it were wrapped in an update.zip, so I'll be fixing that
[20:39] <asac> if we have that its super easy to just setup jenkins jobs
[20:39] <zeroconf> hi - I have some newbie questions
[20:39] <asac> that validate preview images... which for me is the mechanism we want to use more extensively to do something like developing bigger topics
[20:39] <zeroconf> can I install regular applications in Ubuntu Touch?
[20:39] <asac> ok ... think i was clear enough :)
[20:39] <sergiusens> asac: just keep in mind that those jenkins jobs are all private
[20:39] <asac> sergiusens: thats a seprate problem :)
[20:40] <asac> sergiusens: that why local file urls also should work
[20:40] <sergiusens> asac: ack
[20:40] <asac> and in the utah lab i think its not protected
[20:40] <zeroconf> I mean - does Ubuntu Touch have APT and Synaptic? Can I install LibreOffice for example?
[20:40] <asac> e.g. they can directly poll from private jenkins
[20:41] <sergiusens> asac: yes, it's the same network segment
[20:42] <bfiller> kaleo, boiko : https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1200371
[20:42] <bfiller> please add comments, suggestions, etc
[20:42] <AmEv> Quick question: Is there a daily self-updating torrent?
[20:42] <kaleo> bfiller, thank you
[20:43] <bfiller> kaleo: np
[20:45] <bfiller> kaleo: this one would be awesome to tackle soon as well (somewhat related to osk): https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1187321
[20:46] <kaleo> bfiller, right
[20:46] <kaleo> bfiller, linking to qtubuntu
[20:53] <thomi> Hello touch people - this morning I'm unable to flash my nexus 7, phablet flash prints: "Device detected as /system/bin/sh: getprop: not found" - any ideas?
[20:54] <sergiusens> thomi: update phablet-tools and if you are on an old flipped image you will need to use -d grouper
[20:54] <thomi> sergiusens: thankjs
[20:56] <mhall119> the Asus GetProp Not Found is an awesome device
[20:57] <sergiusens> mhall119: I can probably mask that, but then I wouldn't easily be able to root cause it
[20:58] <mhall119> sergiusens: ?
[20:58] <sergiusens> mhall119: the getprop device ;-)
[20:58] <mhall119> oh, that :)
[21:04] <WebbyIT> mhall119: do you have a minute? :)
[21:04] <mhall119> WebbyIT: sure
[21:04] <mhall119> just pinged balloons about your build failure
[21:05] <WebbyIT> mhall119: thanks :)
[21:05] <mhall119> I can't find out what caused the failure, so I'm enlisting his help
[21:06] <WebbyIT> mhall119: ok, thanks. My first problem is that I've port  8080 blocked '-.-
[21:09] <mhall119> hmmm, not sure what we can do about that...
[21:10] <thomi> sergiusens: still no luck - with latest phablet-tools i get this: http://paste.ubuntu.com/5866231/
[21:10] <WebbyIT> mhall119: nothing, I suppose, but I'll resolve it soon
[21:11] <mhall119> WebbyIT: who is blocking you from reaching port 8080?
[21:12] <WebbyIT> mhall119: my college, I'm in a residence, but i'm going to change location
[21:13] <mhall119> balloons: can we access that jenkins instance from another port? why not 80?
[21:13] <robru> kaleo, just got back from lunch. what's up?
[21:14] <kaleo> robru, <mterry> Kaleo, OK, I did sdk and apps stack (which doesn't have *all* the apps - I think phone and media are in their own stacks).  This will fix CI I believe, but daily-release will need another button push by didrocks <mterry> Kaleo, I gotta run, so hopefully that fixes you
[21:14] <kaleo> robru, the critical fix for the critical bug talked in emails landed in lp:ubuntu-ui-toolkit
[21:15] <robru> kaleo, oh, so you just want to make sure that the bugfix lands in saucy?
[21:15] <kaleo> robru, yes, before today's touch image is built
[21:15] <kaleo> robru, I suppose there is no real emergency
[21:15] <mterry> kaleo, gotta go
[21:16] <kaleo> mterry, have a nice on
[21:16] <kaleo> e
[21:16] <robru> kaleo, yeah, I don't know anything about the touch images. I just report to didrocks for the daily_release stuff. but I don't have permissions on the server, I just MP branches and then didrocks pushes all the buttons ;-)
[21:16] <kaleo> robru, didrocks does not have a backup?
[21:17] <robru> kaleo, so either jenkins will release it when it releases it, or didrocks will have to fix it when he wakes up (~8hrs)
[21:17] <kaleo> robru, like, when he sleeps?
[21:17] <kaleo> :)
[21:17] <kaleo> robru, I hope no critical bug fix is blocked by that I guess
[21:17] <robru> kaleo, well, I think kenvandine, cyphermox, and sil2100 also can.
[21:17] <kaleo> robru, in any of the apps blocked by the toolkit's bug
[21:17] <kaleo> robru, ah ah, just the day when they are not here :)
[21:17] <robru> kaleo, well I dont think it's a big deal if it takes one extra day for the fix to land.
[21:18] <kaleo> robru, yeah
[21:18] <kaleo> robru, ok, thank you
[21:18] <thomi> sergiusens: any ideas?
[21:19] <mhall119> didrocks sleeps?  who approved this?
[21:20] <sergiusens> thomi: oh, yeah, sorry, I know what it is, just thinking of a better way to solve this
[21:21] <robru> kaleo, actually, jenkins is smart enough to build SDK first before building the app stack so I think it should all publish just fine... I'm not actually sure what mterry thinks didrocks needs to manually do.
[21:21] <robru> unless he just meant to manually push the release ahead of schedule.
[21:21] <kaleo> robru, we should be all good then
[21:29] <pmcgowan> kaleo, did you get what you needed for the release?
[21:30] <kaleo> pmcgowan, yes
[21:30] <kaleo> pmcgowan, thanks for asking
[21:30] <pmcgowan> ok
[21:45] <mbybee> Hi All
[21:45] <mbybee> Just flashed my Galaxy Nexus - and WOW. That was the *smoothest* ROM I've ever installed. Really excellent work
[21:48] <johnes> Is there anyone here trying to port Ubuntu Touch on Galaxy S3 (i9300) ?
[21:52] <mbybee> So - seeing as I'm fresh eyes on this, and testing just every little thing I can find... where is the list of what works/doesn't work?
[21:52] <mbybee> I don't want to create any pointless bug reports lol
[21:52] <mbybee> Looking through launchpad to figure out what groups are doing what, etc
[21:53] <johnes> well, you mean this ? https://wiki.ubuntu.com/Touch/Install
[21:55] <andidevel> Hi. i have installed saucy first time on my nexus4 today, and there is no people lens. is it disabled in this daily image?
[22:02] <TroN-0074> Question, the phone I am planning on install ubuntu touch is with a carrier I dont care about, will installing Ubuntu touch unluck me from my carrier's network?
[22:03] <TroN-0074> anyone?
[22:03] <TroN-0074> in the house?
[22:04] <esigolo> TroN-0074: you mean is locked ??
[22:04] <andidevel> jup, but no idea ;)
[22:05] <esigolo> do you want to know if
[22:05] <dejello> hello all
[22:05] <esigolo> ubuntu touch install will unlock your phone
[22:05] <esigolo> dejello: Hello
[22:05] <esigolo> :)[]
[22:05] <TroN-0074> I think so, I just bought it from CL and it has cyanogen already installed
[22:06] <esigolo> TroN-0074: and what is the phone model?
[22:06] <TroN-0074> is the galaxy nexus
[22:06] <TroN-0074> currently under the sprint network
[22:07] <TroN-0074> spring is not good for me though
[22:07] <esigolo> TroN-0074: i'm not sure about that ! but you can take a backup and give it a try
[22:08] <TroN-0074> in case that doesnt work is there a place that I can download an image of stock android to re install it?
[22:08] <mbybee> @johnes - Yes, that guide is great, and the tools worked perfectly
[22:09] <esigolo> TroN-0074: yes sure ! just follow the how to https://wiki.ubuntu.com/Touch/Install
[22:09] <esigolo> TroN-0074:  any problem just ping here
[22:09] <TroN-0074> thank you
[22:09] <esigolo> TroN-0074: welcome
[22:14] <mbybee> So - I notice "Settings" is more of a stub, I guess?
[22:14] <mbybee> It's got sections, but many just go to a blank white screen
[22:16] <mbybee> Filed a bug report for that. Overall, this is better than Android was on the G1
[22:16] <esigolo> mbybee: it's kind of ! the content an real think will be add as the developers can
[22:16] <esigolo> :)
[22:17] <esigolo> real thing*
[22:17] <mbybee> Understood :)
[22:17] <mbybee> I'm planning to dev quite a bit for this platform myself
[22:18] <mbybee> The real key bits (phone/sms) seem to be working, so I look forward to seeing it grow
[22:18] <esigolo> mbybee: if you want some help just ping :)
[22:19] <esigolo> mbybee: i'm just waiting a little bit more to use it as daiyl
[22:19] <esigolo> daily
[22:20] <esigolo> brb
[22:20] <thomi> sergiusens: any ideas yet? I really need to get this device working... this is like the worst possible day for it to break.
[22:21] <sergiusens> thomi: can't you flash manually?
[22:21] <johnes> well... is there any "RIL Layer specialist" in here ? :D
[22:21] <mbybee> esigolo: Thanks, I'll be in here quite a bit :)
[22:23] <thomi> sergiusens: you mean with -b ?
[22:23] <thomi> sergiusens: of the "Manual installation" section from https://wiki.ubuntu.com/Touch/Install ?
[22:23] <sergiusens> thomi: no, as is in the wiki https://wiki.ubuntu.com/Touch/Install#Manual_Installation
[22:23] <thomi> gotchya, will try that now, thanks
[22:24] <andidevel> does anyone have an idea how to get the people lens visible? :)
[22:29] <sergiusens> popey: around?
[22:29] <mbybee> Anyone know how to force the keyboard up?
[22:29] <mbybee> For example, trying to tweet, no keyboard
[22:29] <sergiusens> mbybee: there's a bug open for it if doing it from the web
[22:30] <thomi> sergiusens: those instructions seem broken - it just says to push a zip file and reboot.. twice. surely I have to actually install the zip file at some point?
[22:30] <mbybee> sergiusens: Thanks
[22:30] <sergiusens> thomi: it's picked up automatically
[22:31] <thomi> not on my device. Having to select it manually
[22:31] <popey> sergiusens: ya
[22:33] <andidevel> thomi: it takes a few minutes. dont touch the device until it has finished... i thought too i have to choose it manually
[22:33] <sergiusens> thomi: have you ever done the -b thing?
[22:34] <dejello> yay, my ovation build boots today...  still no adb???  hrm...
[22:34] <thomi> sergiusens: I don't know, sorry
[22:34] <asac> guys... you are producing many images today.. .whats the trigger?
[22:35] <sergiusens> asac: I think earlier was a powerd/upstart issue
[22:35] <sergiusens> asac: new one might be stgraber experimenting with updates
[22:35] <asac> doanac`: ^^
[22:35] <mbybee> Hmm. Think I'm going to have to revert to Android, at least until I can set the time/date.
[22:35] <sergiusens> thomi: do you have an ubuntu logo in recovery?
[22:35] <mbybee> It's close though - I think it's going to be one heck of an OS soon!
[22:35] <sergiusens> asac: the new one is only in pending
[22:35] <thomi> sergiusens: nope
[22:36] <sergiusens> thomi: that means you never phablet-flash -b
[22:36] <thomi> ok, is that a bad thing?
[22:36] <sergiusens> thomi: don't do it today, not sure you will hit the fastboot bug (if you have a buggy bootloader)
[22:36] <thomi> heh, ok
[22:37] <sergiusens> thomi: your automation is just broken, not necessarily bad
[22:37] <dejello> and the display is 90 degrees off...merp
[22:37] <sergiusens> thomi: let's do it next week since you are in a hurry now
[22:37] <thomi> just pushing the big image... seems to take forever :-/
[22:42] <mbybee> Well. I shall return, probably next week, to flash again :)
[22:43] <mbybee> Seeya all
[22:45] <RobbyF> How difficult is it for a non-dev to port to sgs3 would someone say?
[22:51] <andidevel> RobbyF: there is a already a port?! https://wiki.ubuntu.com/Touch/Devices/i9300
[22:51] <RobbyF> I need one for i747m
[22:52] <RobbyF> I'm a nexus 4 user but I 'found' an extra sgs3 brand new at work.
[22:54] <andidevel> hmm give it back?!^^
[22:54] <RobbyF> was hoping to use it for this project.
[23:01] <stgraber> asac, sergiusens: yep, the latest one was to test the changes I did today
[23:06] <plars> sergiusens: something's wrong with this build I think, the .2 one for today
[23:07] <plars> sergiusens: it looks ok from the command line, I even see unity running, but on my mako it looks stuck at the "Google" boot screen
[23:08] <plars> ...and adb logcat appears to be broken
[23:09] <plars> I/ServiceManager(  517): Waiting for service SurfaceFlinger...
[23:09] <plars> F/SurfaceFlinger( 1721): couldn't create EGLContext
[23:09] <plars> F/libc    ( 1721): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 294 (SurfaceFlinger)
[23:15] <plars> https://bugs.launchpad.net/touch-preview-images/+bug/1200421
[23:17] <plars> hmm, surfaceflinger came up after I hard rebooted it
[23:19] <satchmo> hi there
[23:19] <satchmo> anyone out there?
[23:23] <satchmo> exit
[23:25] <cyphermox_> awe, still around?
[23:25] <cyphermox_> I'm having weird behavior from ofono when setting Powered on org.ofono.ConnectionManager
[23:25] <cyphermox_> http://paste.ubuntu.com/5866541/
[23:25] <cyphermox_> rsalveti: ^^
[23:27] <thomi> It seems there's no camera support on the n7 - is this a known issue?
[23:27] <cyphermox_> that's fixing the switch for Mobile data for now; it works locally here, but I'd like to know why it behaved that way to make sure we get disconnected right
[23:30] <cyphermox_> awe_: ok, after all it seems like the doc never mentions the contexts get deactivated, so I'm getting expected behavior
[23:30] <cyphermox_> and in fact, this is really good
[23:30] <sergiusens> plars: that's 'pending', right?
[23:30] <sergiusens> plars: mind giving https://code.launchpad.net/~sergiusens/phablet-tools/current-pending/+merge/174307 a go?
[23:31] <awe_> cyphermox_, ok.  missed your first ping to "awe"
[23:31] <sergiusens> plars: and happrove if ok, let's stop these from propagating
[23:31] <cyphermox_> awe_: ah, right
[23:31] <cyphermox_> awe_: well, it's still weird
[23:31] <awe_> that said, I thought that you were just going to deactivate the context?
[23:32] <cyphermox_> I keep a default route, but drop the DNS settings
[23:32] <cyphermox_> awe_: it really seems incorrect to deactivate the context when you toggle the killswitch
[23:33] <awe_> If you toggle Powered, seems that would prevent a separate MMS-specific context to be activated?
[23:33] <cyphermox_> possibly
[23:33] <awe_> well...we're talking apples & oranges
[23:33] <cyphermox_> but it will not deactivate an already activated MMS context either
[23:33] <awe_> NM has the concept of a WWAN disable
[23:33] <cyphermox_> right
[23:33] <awe_> whereas we're talking about a "don't send data over mobile"
[23:34] <cyphermox_> wwan disable is what gets triggered
[23:34] <awe_> airplane mode is a different story
[23:34] <cyphermox_> the UI changed WwanEnable
[23:34] <awe_> cyphermox_, sure...but that doesn't mean it's correct.  ;)-
[23:34] <cyphermox_> this is equivalient to "airplane mode" for mobile only
[23:34] <awe_> it's what was initially suggested to renato, and made sense at the time
[23:34] <cyphermox_> well, it still makes sense to me
[23:34] <cyphermox_> what if you have multiple radios?
[23:35] <awe_> sure, but again... if the ConnectionManager is powered off, then MMS can't activate a separate context
[23:35] <cyphermox_> can't ofono re-power it ?
[23:35] <awe_> mmsd could, but it's not designed to
[23:35] <cyphermox_> also, aren't we possibly expecting that mobile data also deactivates MMS, which is technically mobile data :)
[23:35] <awe_> if powered, it will try to activate an mms context
[23:36] <cyphermox_> Could you try to manually Powered = false, and see if ofono doesn't just do the right thing?
[23:36] <awe_> good poit
[23:36] <awe_> s/poit/point/
[23:36] <cyphermox_> this is getting really complicated and tricky really fast though :(
[23:36] <awe_> uh yea..  I'm about to give up on mms for the night
[23:37] <cyphermox_> I should check for Powered anyway, and triggering WwanEnable for NM should change powered, do we agree to that?
[23:37] <awe_> for now yes
[23:37] <awe_> however I need to think about it some more
[23:37] <awe_> brain == fried
[23:37] <cyphermox_> worst case we can change the UI to just disconnect the interface instead
[23:37] <awe_> definitely
[23:37] <cyphermox_> (at the NM level)
[23:37] <cyphermox_> ok
[23:37] <cyphermox_> so I'll keep testing this and upload later..
[23:37] <cyphermox_> or tomorrow morning
[23:38] <awe_> sounds good
[23:38] <cyphermox_> rsalveti: around for an upload / review?
[23:50] <asac> ouch ... i think it really happened... i lost core dev unnoticed once and for all (as i dont really have a reason get it back):)
[23:50] <asac> i am not even an ubuntu member anymore
[23:50] <asac> thats brutal :)
[23:51] <asac> wel... guess expiring three times without me noticing is reason enough to justify that :)
[23:54] <popey> asac: I'll write you a testimonial ㋛
[23:55] <asac> popey: is it really ok to get dropped out of ubuntu membership just because i dont upload anymore?
[23:55] <asac> i dont know the rules :)
[23:58] <asac> i must say i kind of like the debian policy better... they never would get the idea to kill my DD ... i hope :)
[23:58]  * asac goes and checks
[23:59] <popey> you get dropped out every 2 years
[23:59] <popey> you get a reminder mail though
[23:59] <asac> i know... last time someone nice came along and saved me
[23:59] <asac> because i dont get those emails
[23:59] <popey> heh
[23:59] <popey> unlucky
[23:59] <asac> anyway... dont need it... but ubuntu membership?
[23:59] <popey> sabdfl expired once iirc
[23:59] <asac> also expiring?
[23:59] <asac> from ubuntu membership? or being core dev?