[00:28] <RobbyF> I found rotation in terminal can be painfully slow
[00:28] <cjohnston> +1
[00:31] <mattwj2002> hi guys
[00:31] <mattwj2002> how is the ubuntu phone system coming along?
[05:22] <bkerensa> What is being used to currently do Ubuntu Touch image builds?
[07:20] <freeflying> dholbach: can I adb remount && adb shell then apt-get update && apt-get dist-upgrade to keep the phone updated?
[07:22] <dholbach> good morning
[07:23] <dholbach> freeflying, for the time being I think so, but I'm not sure how that's going to work with the image-based updates
[07:28] <freeflying> dholbach: thanks :)
[07:28] <ogra_> it isnt, apt is disabled on them
[07:29] <ogra_> but there is a developer mode that enables apt (which is a permanent change though, image updates will be disabled then)
[07:30] <freeflying> ogra_: can I update through system-settings now
[07:31] <ogra_> i'm not sure how far that is already
[07:31] <ogra_> (and i'm personally not running system images yet)
[07:32] <freeflying> uhmm
[07:32] <ogra_> you can definitely upgrade them from commandline
[07:34] <freeflying> by using the builtin terminal or via adb shell, guess they're the same approach
[07:34] <ogra_> yeah
[07:35] <freeflying> which command shall I run, btw
[07:36] <ogra_> https://www.stgraber.org/2013/07/20/introducing-the-ubuntu-touch-image-based-upgrader/
[07:37] <freeflying> thanks
[07:37] <ogra_> though thats not the default yet (as you can see
[07:37] <ogra_> )
[07:38] <ogra_> with the default you need to regulary re-flash (all data in the homedir is persistent and kept over re-flashes)
[07:38] <ogra_> if you want to be on the safe side ...
[07:39] <ogra_> or use apt if you are brave ... but there is always the risk that you mess it up (parts of some libs live in android and are not packaged, changes to them require both sides to be upgraded)
[07:39] <freeflying> it'll be fine, I use it for fun, not for daily using
[07:40] <freeflying> ogra_: I did use apt over the past couple of days, so far its running ok
[07:40] <ogra_> yeah, for daily usage the regular re-flash would be the only safe thing ... if you can bear that it might break use apt :)
[07:40] <ogra_> watch out for libhybris and platform-api
[07:40] <ogra_> if either of them is in the upgrade you most likely want to flash an update
[07:41] <freeflying> trying with system-image-cli now
[07:43] <Mirv> ogra_: hi. I wonder if (in absence of didrocks and seb128) you as a core dev could approve tvoss' packaging change so that I could publish it? http://pastebin.ubuntu.com/5987618/
[07:43] <seb128> Mirv, +1
[07:44] <Mirv> seb128: shouldn't you be having holiday as well? :) thanks
[07:44] <ogra_> Mirv, looks fine
[07:44] <Mirv> ogra_: thanks
[07:44] <ogra_> (i assume this has been testbuilt before ?)
[07:45] <Mirv> ogra_: yes, it's via the normal cu2d system, so built and tests run, we just have a deal that a core dev must +1 in case of packaging changes
[07:45] <ogra_> ah, k
[07:45] <Mirv> now just France and many other places have holiday today
[07:46] <ogra_> right, well, just go ahead
[07:47] <Mirv> did so, that unblocks well actually everything probably (platform, sdk, unity, apps) that was waiting
[07:47] <Mirv> well apps and unity have another run ongoing, but possibly after that
[07:49] <Mirv> unity8 has some test failures since yesterday evening, have to look at those / file bugs
[07:50] <seb128> Mirv, yeah, I'm going to be off soon, I was just doing some email/IRC checking in the morning
[08:04] <juliankreuz> hello
[08:04] <juliankreuz> could i ask if i install ubuntu touch preview does it wip internal storage parition?
[08:05] <juliankreuz> *wipe sorry typo
[08:05] <popey> juliankreuz: it wipes the device
[08:05] <ev> popey: you cannot reproduce the whoopsie 100% CPU bug now, correct?
[08:05] <popey> ev: i tend to flash my phone daily, just about to flash it now, will let you know.
[08:05] <ev> popey: cheers
[08:06] <juliankreuz> ok thank you
[08:06] <ev> if you can reproduce it, there's a version of whoopsie on its way into the archive (0.2.22) that has an option I'd like you to test.
[08:06] <ev> just as a heads up :)
[08:06] <popey> ok
[08:07] <ogra_> i just released 14.1 as current btw
[08:07] <popey> ☻
[08:07] <popey> just as I'm flashing --pending ☻
[08:07] <ogra_> (since there was one failure less)
[08:07] <popey> (which is 14.1) ☻
[08:07] <ogra_> well, yeah :)
[08:10] <juliankreuz> hi, also could i ask if there's any plans on bringing Ubuntu Touch Preview on Flo?
[08:11] <popey> Flo? is that the new nexus 7?
[08:11] <juliankreuz> yes
[08:11] <popey> we dont plan to, but anyone in the community could go ahead and port it
[08:11] <popey> we don't have any devices in the company making it hard ☻
[08:13] <juliankreuz> ok, thanks for the answer. :)
[08:18] <nhaines> So the good news is that I finally decided to try phablet-flash ubuntu-system to my Galaxy Nexus.
[08:18] <nhaines> It even installed properly!  The bad news is that there's no display now.
[08:33] <popey> ev: seems okay so far, been running for a while with autopilot tests running, rebooted a couple of times, no whoopsie
[08:33] <ev> whoop
[08:33] <popey> sie
[08:33] <ev> I'm assuming you mean no 100% CPU from whoopsie, rather than whoopsie just not being there
[08:33] <popey> correct
[08:33] <ev> yay
[08:33] <popey> whoopsie  1544  0.0  0.1  49864  3668 ?        Ssl  08:15   0:00 whoopsie
[08:34] <popey> whoopsie there, but not eating silicon
[08:34] <JamesTait> Good morning all, happy Lion Day! :-D
[08:36] <Mirv> popey: ha, you! you must know who could breath life into a QA machine that seems to have gone down?
[08:37] <ev> if anyone else is still having trouble with whoopsie (hi plars), do let me know. I've got some things I'd like you to try.
[08:38] <Mirv> I'm having hard time thinking of someone who would be awake and not on holiday due to the Assumption of Mary day (which I googled up) a lot of Europe is having
[08:54] <popey> Mirv: which machine, which datacentre?
[08:59] <Mirv> popey: QA lab intel machine, now I've progressed in finding people to the extent that it's just about guesswork on which machine to powercycle :)
[09:00] <popey> ah ok
[09:05] <tmoenicke_> mzanetti: ping
[09:12] <mzanetti> tmoenicke_: pong
[09:21] <Mirv> ok now we'd probably need someone physically around the machine, even powercycling does not seem to help
[09:31] <murgero> Hey guys!
[09:32] <murgero> Who here is amazing with porting Ubuntu Touch?
[10:06] <davmor2> ogra_: you poop glitter?  Now I'm really concerned about your well being :D
[10:06] <ogra_> hahaha
[10:07] <davmor2> ogra_: you really need to stop eating glitter for a start off, it's not good for you honest :)
[10:13] <ogra_> davmor2, no, no ... i *produce* glitter from munching phones indeed :)
[10:16] <davmor2> ogra_: that's even less healthy there are toxic substances and all sorts in phones.  You just stay exactly where you are till the nice men in white coats with the rear fastening jacket arrive ;)
[10:16] <brendand> is there any good guide to how to install cwm to a nexus 7? i somehow seem to have zapped the recovery image on mine
[10:16] <brendand> when i run adb reboot recovery i end up with a dead android
[10:17] <ogra_> hehe
[10:17] <ogra_> brendand, you can just manually flash a new recovery in fastboot mode
[10:17] <ogra_> adb reboot-bootloader ...
[10:18] <ogra_> wget http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130815/saucy-preinstalled-recovery-armel+grouper.img
[10:18]  * popey stabs ueventd
[10:18] <ogra_> sudo fastboot flash recovery /path/to/downloaded/saucy-preinstalled-recovery-armel+grouper.img
[10:19] <ogra_> and then boot into recovery
[10:31] <davmor2> popey: don't stab the messenger bah-dum-tish
[10:33] <popey> Don't quit the day job, comedy-dave
[10:38] <nhaines> Is there any known issue with the maguro image upgrades?
[10:49] <davmor2> popey: Thanks to quote Milton Jones that joke doesn't normally work :)
[10:50] <davmor2> popey: it looks to me like people are hating things that end in d more than they ever did with apps that start with p and end in audio :)
[11:26] <Hashtag> Can anyone one tell me where i can find a bug list for the Nexus devices? Thanks
[11:30] <nhaines> ivanka: beautiful design work on the phone.  :)
[11:37] <ivanka> nhaines, there is a whole team working on it: http://design.canonical.com/team/
[11:38] <ogra_> asac, http://paste.ubuntu.com/5988662/ ...
[11:38] <ogra_> to compare two dashboard results easily
[11:40] <asac> ogra_: whats the build id?
[11:40] <asac> oh got it
[11:40] <ogra_> ./get-utah-results.sh 20130814.1 20130815
[11:40] <ogra_> thats how i call it here
[11:41] <asac> well i needed to use the number from the URL
[11:41] <asac> 3526
[11:41] <asac> and 3536
[11:41] <ogra_> the columns with the id at the top show the error count ... the rest should be self explanatory
[11:41] <ogra_> why ?
[11:41] <asac> the dates didnt do
[11:41] <ogra_> it picks them from the dashboard
[11:41] <asac> just returned saying they are not good
[11:42] <asac> sh Development/ubuntu/dashboard.sh 20130815 20130814
[11:42] <asac> dashboard.sh <old build id> <new build id>
[11:42] <ogra_> what dates did you give ?
[11:42] <asac> sh Development/ubuntu/dashboard.sh 3526 3536
[11:42] <asac> works
[11:42] <asac> well not really :)
[11:42] <ogra_> err
[11:42] <ogra_> new id needs to be last (as the error message says)
[11:42] <asac> aha :)
[11:42] <asac> well, i thought comparing wouldnt matter :)
[11:43] <asac> just a diff i thought
[11:43] <ogra_> nah
[11:43] <ogra_> its more :)
[11:43] <ShapeShifter499> hi
[11:43] <asac> !!11!!	0		0		default
[11:43] <ogra_> it compares the test results line by line
[11:43] <asac> what does !!11!! mean? isnt good?
[11:43] <ogra_> see the elgend at the bottom :)
[11:43] <ogra_> *legend
[11:43] <asac> oh now i see :)
[11:43] <ogra_> that means you should take a closer look
[11:43] <asac> i didnt get that you display for all builds :)
[11:44] <ShapeShifter499> on ubuntu desktop the current stable 13.04 is code named Raring, what would the current version of Ubuntu Touch be called and what would be it's version number?
[11:44] <ogra_> total changed ... cant really automatically compare then
[11:44] <asac> ogra_: ignore... :)
[11:44] <asac> big brain farth here
[11:44] <ogra_> well, just run it if all tests are done and as long as there is no red we didnt regress
[11:45] <asac> ogra_: would be good to also see if a test that is in A is not in B?
[11:45] <asac> e.g. not yet or failed to run
[11:45] <asac> like marking the line red
[11:45] <asac> or something else nice
[11:45] <ogra_> that would show as !!nn!! again
[11:45] <ogra_> since the total was zero last run
[11:45] <asac> ogra_: nice: http://reports.qa.ubuntu.com/smokeng/saucy/image/3536/default/265277/
[11:45] <ShapeShifter499> anyone?
[11:45] <asac> :)
[11:45] <asac> systemsettle has landed
[11:46] <asac> so at that point there is nothing looping at least
[11:46] <ogra_> it still needs 3 runs ... intresting
[11:46] <asac> well we shoot for 99.25 idle average
[11:46] <asac> thats pretty high bar
[11:46] <asac> i thought i would have reduce it slightly
[11:46] <ogra_> ShapeShifter499, there is only a development version
[11:46] <ogra_> (of ubuntu touch)
[11:47] <ogra_> ShapeShifter499, Ubuntu Touch will have its first release with 13.10 ... which has the development codename "saucy"
[11:47] <asac> maguro also needed 3 runs
[11:47] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/3535/default/265363/
[11:47] <asac> e.g. 3 minutes
[11:47] <ogra_> yeah
[11:47] <ogra_> 3 minutes ?!?
[11:47] <ShapeShifter499> ogra_, that is what I meant, thank you
[11:47] <ogra_> wasnt it 10sec per loop ?
[11:48] <asac> one run is vmstat 6 10
[11:48] <asac> 6 repeats with 10 seconds
[11:48] <ogra_> ah, k
[11:48] <asac> then it calcs the average after throwing first sample away
[11:48] <asac> and sees if that average is better than 99.25
[11:48]  * ogra_ knew there were 10sec in the equation somewhere 
[11:48] <asac> 10 runs a 6 secs :)
[11:49] <asac> and we wait for at most 10 of those 1 minute runes
[11:49] <asac> ogra_: if we dont succeed at all to settle we will see tops dumbed from after each run
[11:49] <asac> dumped
[11:49] <asac> maybe i should just always dump them even if it succeeds
[11:49] <ogra_> if we dont settle at all we need to fail and reboot the device
[11:50] <ogra_> (and set a reboot counter, so it fully fails after a certain amount of reboots)
[11:50] <asac> ogra_: atm not... but if it fails i will ignore all the other failures
[11:50] <asac> because it doesnt really make sense to investigate those
[11:50] <ogra_> right, but having a reboot and fail count would help to see if its a race
[11:51] <asac> so it helps us not hunting down autopilot failures due to noisy system (which was claimed a few times during this week)
[11:51] <ogra_> i.e. if it passes after the reboot we found a race
[11:51] <asac> ogra_: oh ... well, we reboot before every autopilot ... and we will run it on every boot
[11:51] <asac> so you will get that
[11:51] <ogra_> err, i was told we dont reboot
[11:51] <ogra_> at all
[11:51] <asac> it will initially just not be nicely visualized (might even already happen ... check the autopilot runs)
[11:51] <asac> ogra_: we dont reflash
[11:51] <asac> but we seem to reboot
[11:52] <ogra_> hmm, i thought plars said we dont
[11:52] <asac> well, i thought we rebooted 2 or three times
[11:52] <asac> not every test
[11:52] <asac> e.g. after default,sk,securit, but not after each autopilot
[11:52] <asac> but i was told its really on every test
[11:52] <asac> *shrug*
[11:52] <asac> ogra_: i guess you should be able to find the bootlog in jenkins to confirm
[11:53] <ogra_> ah, well
[11:53] <asac> anyway... agreed is that it gets run before every test
[11:53] <asac> and i was told we reboot before every test
[11:53] <asac> so we get what we want :)
[11:54] <ogra_> well, in any case looking at my script output it seems like 0815 is publishing worthy
[11:54] <asac> all tests ran?
[11:54] <asac> ogra_: successfully tested?
[11:55] <ogra_> according to the script output it improved :)
[11:55] <ogra_> termial app passes one more
[11:55] <ogra_> adn default has a new test (your load thingie)
[11:55] <asac> ogra_: +1
[11:55] <asac> have you tested locally?
[11:56] <ogra_> yes, maguro seems fine
[11:56] <ogra_> ... and released
[11:56] <asac> plars: doanac`: so lets really run this before AND AFTER each test...
[11:56] <asac> if we reboot we won't see left over runaway processes after the test otherwise
[11:56] <asac> and i am currently seeing unity8 going crazy not after boot, but just after very light use
[11:57] <asac> so the after will bring us such bad issues
[11:58] <asac> ogra_: this tool is so nice ... can you also make it produce nice data that i can put in a spreadsheet to make nice drawings over time :)?
[11:58] <asac> lol
[11:59] <ogra_> sure, we can make it produce pie charts with candy and the like :P
[11:59] <asac> ogra_: can we maybe not use yellow and !! if we grew tests and those are still perfect? :)
[11:59] <asac> i guess green with a (+)
[11:59] <ogra_> (i can indeed improve it further to get long term data for a curve etc)
[11:59] <asac> or something would better reflect what happened with default
[12:00] <ogra_> sure, i can change that
[12:00] <ikillcypher> Hello
[12:00] <asac> well not important... i just have to learn what it means
[12:00] <asac> but ... i think everything that is green should be green here as well :)
[12:00] <ogra_> it is just that i tink we really should check manually if new tests are added
[12:00] <asac> and rather put NEW/FIXED/ etc.
[12:00] <ogra_> since even if the failure count didnt change it might be that suddenly you have different failures
[12:00] <asac> to annotate if we went green just now
[12:01] <ogra_> so manual check is needed
[12:01] <asac> or a NEW test was added
[12:01] <asac> ok
[12:01] <asac> well.. we should fail if there are less tests i agree
[12:01] <asac> adding new tests i like :)
[12:01] <ogra_> and i want to keep the output as simple as possible so you can easily see the improvements/regressions
[12:02] <asac> yeah right
[12:02] <asac> so scratch the thing about the all green
[12:02] <asac> just think how to best annote what changes
[12:02] <asac> you could just use NEW etc. and add a column to the left
[12:02] <ogra_> if we want more colums and/or more functions i would rather write another tool for that
[12:02] <asac> where you put those
[12:02] <asac> hehe
[12:02] <ogra_> this one is rather single purpose to make it easier to see at a glance if we got better
[12:02] <asac> well whatever, what i have now is good :)
[12:02] <asac> i can probably change it too  ;)
[12:03] <asac> so better work on more useful stuff for now
[12:03] <ogra_> it can surely grow in all directions or get new friends in a bzr tree :)
[12:03] <asac> maybe later we can think about long term data, but i hope utah is not loosing anything so we can do that anytime (not now)
[12:03] <ogra_> yeah
[12:04] <asac> gema_: whats the retention policy for the data we see on dashboard?
[12:04] <ogra_> after all ist justr a screen scraper for the dashboard
[12:04] <asac> will that get wiped after a month or so?
[12:05] <gema_> asac: right now we dont remove stuff
[12:05] <gema_> asac: we are considering removing for old releases, though
[12:06] <asac> gema_: how much storage do we have/use right now for the jenkins data?
[12:06] <asac> gema_: also, i assume we dont do backups?
[12:07] <gema_> asac: this is an IS machine, I am pretty sure we do backups
[12:07] <gema_> asac: on both, the dashboard and the external jenkins
[12:07] <asac> popey: is ueventd really looping right after boot? or does it take a while before you see this?
[12:07] <gema_> asac: I can check for the backup policy of the internal jenkinses
[12:07] <ikillcypher> ogra_, I releasing ubuntu-touch for my device on xda
[12:08] <ikillcypher> to allow open source contribution
[12:08] <popey> asac: tends to be soon after boot
[12:08] <asac> popey: what does soon mean? for me thats before you touch the device :)
[12:08] <popey> root@ubuntu-phablet:/# uptime 12:08:13 up  1:58,  1 user,  load average: 2.98, 3.08, 3.03
[12:08] <popey> root@ubuntu-phablet:/# ps aux | grep ueventd
[12:08] <popey> root       473 96.0  0.0    376   196 ?        R    10:09 113:51 /sbin/ueventd
[12:08] <asac> like before unlock or after?
[12:08] <ogra_> it doesnt loop
[12:08] <ogra_> it hangs
[12:08] <popey> i dont touch it
[12:08] <popey> i just flash then adb shell as soon as I can
[12:09] <popey> and very soon see ueventd
[12:09] <ogra_> popey, can you chekc the end of logcat ?
[12:09] <asac> ogra_: thought it eats CPU cycles?
[12:09] <ogra_> does it talk about sensorservice ?
[12:09] <ogra_> asac, it does .... but it doesnt loop
[12:09] <popey> how do i run logcat?
[12:09] <popey> command not found
[12:09] <ogra_> /system/bin/logcat -d | tail
[12:09] <asac> popey: interesting ... so before the lock screen is even there?
[12:09] <popey> ta
[12:09] <ogra_> see if there is a lot sensorservice
[12:09] <ogra_> noise
[12:10] <popey> http://paste.ubuntu.com/5988757/
[12:10] <popey> asac: lemme reboot now and test
[12:10] <ogra_> no, looks fine thanks
[12:10] <asac> ogra_: well, it maybe is in a busylock in the kernel?
[12:10] <asac> :)
[12:11] <ogra_> asac, well, its wrangling with udev about the devices ... can be busylock or some such, yeah
[12:11] <gema_> asac: we believe the external systems are backed up daily, the internal jenkins instances back up every hour
[12:11] <asac> popey: yeah. well, we only have one dashboard boot on mako, but there it looked like:
[12:11] <gema_> asac: just confirmed with retoaded
[12:11] <ogra_> its about time we get that upstart bridge
[12:11] <asac> popey: http://reports.qa.ubuntu.com/smokeng/saucy/image/3536/default/265277/
[12:11] <asac> so was good :)
[12:11] <asac> lets wait
[12:11] <asac> for more attempts
[12:12] <asac> ogra_: steve told me that we can fix our problems without that upstart part if we do what we need to do anyway for the solution :)
[12:12] <asac> ogra_: from what i know rsalveti has that fix already :/
[12:12] <ogra_> asac, which would be ?
[12:12] <ogra_> no, he hasnt
[12:13] <asac> hmm. lets wait for chicken
[12:13] <asac> steve wanted to give him th details
[12:13] <ogra_> the proper solution would be to have something like "udevadm settle" for ueventd
[12:13] <ogra_> but that means a lot of patching
[12:13] <asac> ogra_: steve said something about stopping ueventd after its done
[12:13] <ogra_> on the android side
[12:13] <ogra_> yes
[12:13] <asac> that thats the real fix :)
[12:13] <ogra_> the "it is done" part is the hard one
[12:13] <asac> he said if we do that alone we are already happy
[12:14] <ogra_> you need something like "ueventd settle"
[12:14] <popey> asac: http://showterm.io/0254cd08db04bb375a0a5  <- there you go
[12:14] <asac> right, but that seems to not involve upstart according to steve
[12:14] <asac> and rsalveit knows how to fix it
[12:14] <ogra_> that waits until it is done and then sends the event to the upstart bridge
[12:14] <ogra_> but afaik he didnt add it ... and we wanted to see if the upstart stuff is probably suffiicient
[12:15] <asac> popey: interesting
[12:15] <ogra_> but anyway, even if ueventd would have the patch ... we still dont have that info for udev on the ubuntu side
[12:15] <ogra_> we need the bridge in any case
[12:15] <asac> popey: and that doesnt goaway ... interesting
[12:16] <popey> yeah, it will stay forever
[12:16] <asac> popey: can you copy http://paste.ubuntu.com/5988768/ on your device and call it with 99.25 as argument?
[12:16] <popey> i went for a walk and it was still there 40 mins later
[12:16] <asac> just to see that it definitely will fail in automation :)
[12:16] <popey> sure
[12:16] <asac> popey: well, you can just run vmstat 5 10 and see if your idle ever goes above 90 :)
[12:16] <popey> oh ok
[12:17] <popey> in my experience once ueventd hits high CPU on boot, it _never_ comes back down
[12:18] <popey> I've left my phone for hours and its still running
[12:19] <ogra_> yeah, it wont
[12:19] <asac> popey: right... so vmstat also shows the same idle/busyness as top for you?
[12:19] <asac> ogra_: kill :)
[12:19] <popey> yeah, idle is 0
[12:19] <ogra_> that kills the container
[12:19] <popey> http://paste.ubuntu.com/5988789/
[12:20] <asac> ogra_: thats a bad thing? can we restart the container without rebooting the system?
[12:20] <asac> and it works?
[12:20] <ogra_> we can, but that takes all the other bits down with it
[12:20] <asac> ogra_: could we do that transparently?
[12:20] <asac> like without user noticing?
[12:20] <ogra_> no
[12:21] <asac> not even if we wanted?
[12:21] <ogra_> killing the container will kill the session
[12:21]  * asac takes a note
[12:21] <ogra_> unless you put the check before session statup ... which means a massive boot delay
[12:22] <asac> oSoMoN: who is doing browser?
[12:22] <annerajb> morning
[12:22] <asac> oSoMoN: bill talked about configs we could set so it behaves nicely in low memory environment
[12:22] <asac> oSoMoN: guess reducing caches etc.
[12:22] <asac> oSoMoN: do you know anything about it?
[12:22]  * ogra_ guesses we always want that 
[12:23] <ogra_> given how choppy and sloe the browser acts
[12:23] <ogra_> *slow
[12:23] <asac> ogra_: thats intentional atm
[12:23] <ogra_> ah, k
[12:24] <ogra_> i know we have slowness in javascript ... didnt know that we also should expect choppy scrolling etc
[12:24] <ogra_> (or as in case of G= no scrolling at all)
[12:24] <ogra_> *G+
[12:26] <asac> ogra_: well, does unity8 loop for you?
[12:26] <ogra_> no, should it >
[12:26] <ogra_> ?
[12:26] <asac> it does for me all the time
[12:26] <asac> ogra_: use your indicators once :)
[12:26] <asac> just pull down and look around
[12:26] <asac> i think that triggers it
[12:27]  * ogra_ isnt near his phone atm ... i can test in ~30min
[12:27] <asac> no need
[12:27] <ogra_> davmor2, ^^^
[12:27] <asac> just saying, you might have seen that problem
[12:27] <ogra_> nope
[12:27] <asac> when scrolling was super choppy
[12:27] <davmor2> asac: what image is that on?
[12:28] <ogra_> asac, it is always choppy and slow
[12:28] <asac> yesterdays for example
[12:28] <ogra_> and G+ scrolling doesnt work at all
[12:28] <ogra_> (two different bugs)
[12:28] <asac> ogra_: probably also a not-optimized rendering engine? maybe there is a hwaccell setting somewhere we can turn on
[12:28] <asac> which would use surfaces for scrolling etc.
[12:29] <ogra_> well, ltes wait for Mir and see how it os then
[12:29] <ogra_> *is
[12:29] <ogra_> *lets
[12:29] <ogra_> *sigh*
[12:29] <popey> Mir fixes everything \o/
[12:29] <ogra_> yeah
[12:29] <popey> "Shit canonical employees say"  tumblr...
[12:29] <ogra_> haha
[12:29] <pmcgowan> we also need the javascript fix, that will effect a lot, and the UA string fixes, with overrides
[12:30] <ogra_> yeah, the UA stuff is annoying
[12:30] <davmor2> UA?
[12:31] <pmcgowan> user agent
[12:31] <ogra_> user agent
[12:31] <pmcgowan> the bane of the internet
[12:31] <asac> pmcgowan: right. do you know who does our browser work?
[12:31] <pmcgowan> of course
[12:31] <asac> :)
[12:31] <pmcgowan> so do you
[12:31] <pmcgowan> oliver
[12:31] <davmor2> ah I'm thinking Ubuntu Android, Ubuntu Accessibility  etc
[12:31] <annerajb> ogra_, if my phone is not in a reboot loop and I pull off the battery and go into recovery the last_kmsg is the one from when it was stuck booting??
[12:32] <asac> ogra_: ^^ so when will we get that feature :-P
[12:32] <ogra_> annerajb, no, thats likely the current boot
[12:32] <asac> j.k.
[12:32]  * annerajb bangs his head against his desk
[12:32] <ogra_> annerajb, last_kmsg is a ram console ... if the device was power less it will be flushed
[12:32] <annerajb> i been using that since day one every time i got stuck
[12:33] <ogra_> asac, ask my clone :P
[12:33] <annerajb> ogra_, what alternative do i have is there a way to see kernel messages on screen?
[12:33] <ogra_> not really, unless you hack up your kernel to have a framebuffer console
[12:33] <davmor2> asac: I get no loop here
[12:33] <ogra_> but many android drivers dont allow that (since fbcon isnt an android feature)
[12:34] <annerajb> ogra_, oh boy so i have no way of knowing what the kernel is doing?
[12:34] <ogra_> fast fingers :)
[12:34] <ogra_> to get into recovery
[12:34] <davmor2> of course there is always blame popey that tends to fix a lot of things ;)
[12:34] <annerajb> dont get it? if it's stuck booting ie kernel panic
[12:34] <ogra_> it doesnt reboot after panicing ?
[12:35] <annerajb> no
[12:35] <ogra_> weird
[12:35] <annerajb> hence getting stuck
[12:35] <ogra_> it should
[12:35] <ogra_> it should either give you adb or reboot
[12:35] <ogra_> unless you changed kernel defaults
[12:36] <annerajb> i did change kernel stuff but it was enabling new flags like NS and such
[12:36] <ogra_> check what CONFIG_PANIC_TIMEOUT is set to
[12:37] <ogra_> that should be the reboot time on panic in seconds
[12:38] <annerajb> hmmm... wonder what happens if i have swap enabled on the kernel but not on my device....
[12:38] <ogra_> nothing
[12:38] <annerajb> as in i removed from the rootfs the swap
[12:38] <ogra_> it might fall over if there is a ram overcommit ... but that shouldnt happen unless you have ram hungry apps
[12:39] <w-flo> annerajb, my device booted to a black screen without adb once.. extracting the ubuntu rootfs failed halfway and I didn't notice (/data was out of disk space)
[12:39] <annerajb> ogra_, CONFIG_PANIC_TIMEOUT is set to 5
[12:39] <annerajb> w-flo, thanks i am using your script to modify the rootfs :D
[12:39] <ogra_> so it should reboot after 5 sec when it panics
[12:40] <w-flo> annerajb, you can't notice that issue since there's no error message, the untar just fails silently
[12:40] <w-flo> but some of the files (like adbd?) are missing
[12:41] <annerajb> w-flo, that dosnt seem to be he case (space wise) /dev/block/mtdblock3    918.8M    838.8M     79.9M  91% /data
[12:41] <annerajb> where should adb be in the rootfs?
[12:41] <annerajb>  /bin?
[12:42] <ogra_> /usr/bin/adbd iirc
[12:42] <annerajb> found it there
[12:42] <annerajb> ogra_, if i am getting into the rootfs by luck dosnt the rootfs write other log files like unit8.log and upstard.log?
[12:42] <annerajb> (on the sdcard)
[12:42] <ogra_> yes
[12:42] <asac> davmor2: open a few apps
[12:43] <asac> scroll around
[12:43] <diwic> ogra_, I don't want to flash the daily right now, so what package should I upgrade to get the /dev/socket/qmux_bluetooth fix?
[12:43] <asac> close again
[12:43] <ogra_> but i doubt yoou get that far
[12:43] <asac> davmor2: it always happens here on maguro
[12:43] <davmor2> ogra_: yay I just broke my apps screen
[12:43] <ogra_> diwic, uh, oh, sorry ... i havent added it yet
[12:43] <diwic> ogra_, no worries
[12:44] <ogra_> diwic, it will land in lxc-android-config  ...
[12:44] <annerajb> can the initrd be made so it writes log files to /sdcard?
[12:44] <plars> asac: run what?
[12:44] <ogra_> diwic, i'll make sure it lands today
[12:45] <annerajb> w-flo, do you use no_console_suspend on your device?
[12:45] <davmor2> asac: I can get my apps screen to do this http://ubuntuone.com/4Vpi2lKb4LLiIR9mFVzvXI
[12:45] <w-flo> annerajb, no_console_suspend=1 console=tty1   --- I just added the console=tty1, the no_console_suspend is from upstream
[12:45] <annerajb> CONFIG_CMDLINE="console=ttyFIQ0 no_console_suspend=1 datapart=/dev/mtdblock3"
[12:46] <annerajb>  that's how mine looks like
[12:46] <asac> plars: dunno, i usually do camera and clock
[12:46] <asac> and close them
[12:46] <plars> asac: ??
[12:46] <plars> asac: I was responding to "<asac> plars: doanac`: so lets really run this before AND AFTER each test..."
[12:47] <asac> plars: settle
[12:47] <asac> (sorry was in a different context :))
[12:47] <plars> asac: ahh, we decided to go a different route
[12:47] <asac> that is?
[12:47] <plars> asac: we are gathering a single top -n1 before running each test
[12:47] <ikillcypher> ENJOY : http://forum.xda-developers.com/showthread.php?t=2405815
[12:47] <ikillcypher> RELEASED
[12:47] <asac> plars: why?
[12:47] <asac> please use settle to wait for it to settle :)
[12:47] <plars> asac: running system settle before and after each test run will add 1 hour and 20 min or so (and growing)
[12:48] <asac> we can use 3 minutes instead of 10 for those runs
[12:48] <plars> asac: still needs a minimum of 2 min to run
[12:48] <w-flo> annerajb, I have it in BoardConfig.mk... BOARD_KERNEL_CMDLINE := no_console_suspend=1 console=tty1   the config actually has a conflicting option for console :o
[12:48] <plars> asac: so 40 min or so for running before each test run
[12:48] <asac> plars: we must wait till the system is quiet anyway
[12:48] <plars> asac: that's minimum
[12:48] <plars> asac: and usually it is
[12:48] <asac> so we run the right amount of time
[12:49] <asac> not too long :)
[12:49] <plars> asac: so we shouldn't wait 2 min. to find that out
[12:49] <diwic> ikillcypher, cool stuff! :-)
[12:49] <asac> plars: too much typing, we should have a call :)
[12:49] <plars> asac: what we did for now, was add this top.log at the beginning of each test run, so at least until we have a better method, we can see if there was some process adding a lot of load
[12:49] <asac> thats not what we want
[12:49] <asac> that doesnt meet engineering requirement
[12:51] <ogra_> annerajb, no_console_suspend=1 is a standard thing you find on many devices ...  whats missing is a console=tty1 at the end of that line :)
[12:51] <annerajb> ogra_, it does have console=ttyFIQ0 should i add two console= lines?
[12:52] <ogra_> you should add a tty1 console arg, yeah
[12:52] <ogra_> (the last one is always handed over to init ... the first one defines what the kernel uses when producing output)
[12:56] <oSoMoN> asac: re browser config, I am doing the browser, and I have a work item on my list to investigate how to limit memory usage, haven’t really started investigating though
[12:57] <pmcgowan> oSoMoN, asac would be nice to get some help with that
[12:57] <annerajb> ogra_, is tty1 the right number if not how do i know which tty is the one for my device?
[12:58] <ogra_> tty1 should be right (if your kernel has the necessary changes indeed)
[13:00] <thumperest> hello all
[13:03] <nhaines> ikillcypher: congrats!
[13:04] <plars> balloons: looks like your fixes for terminal-app are working great :)
[13:05] <balloons> plars, indeed.. everything left is a known issue
[13:05] <balloons> so no surprises today.. :-)
[13:09] <annerajb> ogra_, still nothing shows on the screen.
[13:09] <annerajb> no adb either
[13:10] <ogra_> give it some time ... on my S2 the adbd startup takes about 2min
[13:10] <ogra_> (no idea why and i didnt have the time to debug)
[13:13] <annerajb> i think i am going to start soldering a usb serial console for the phone
[13:14] <ikillcypher> no changelog for nightly releases ?
[13:14] <ikillcypher> http://cdimages.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/raring-preinstalled.changelog
[13:14] <annerajb> ikillcypher, they where working on them
[13:14] <ikillcypher> ?
[13:15] <annerajb> when i was a few days ago they (canonical) said they where working on gettnig them implemented ie. they dont exist yet
[13:15] <annerajb> was=ask*
[13:15] <brendand> is it in a known bug in the latest images that i don't get prompted for my WPA2 PSK when trying to connect?
[13:27] <thumperest> hi all, i fres installed ubuntu 13.04 i86 to my laptop, after the updates an neceserry installations, when i try to make this command work phablet-flash (cdimage-touch|cdimage-legacy|ubuntu-system|community) -b it gives me error like bash: syntax error near unexpected token cdimage-touch do you know any solution ?
[13:28] <nhaines> thumperest: what you gave isn't a command.
[13:28] <nhaines> You're suppose to pick which command between the parentheses () you want.
[13:28] <nhaines> What phone do you have?
[13:28] <thumperest> nexus 4
[13:29] <nhaines> Try 'phablet-flash cdimage-touch -b'
[13:29] <thumperest> ok thanks ;)
[13:30] <nhaines> No problem.  By the time Ubuntu 13.10 comes out, it'll be 'ubuntu-system', not 'cdimage-touch'.  And for the community-based ports, it's.. well, 'community'.  Different ways to support different devices.
[13:31] <nhaines> Anyway, you should be all set with the rest of the instructions.  Just remember any time you see brackets something's optional, and when you see choices separated with a pipe (|) it means you have a choice of one.
[13:31] <nhaines> Works with pretty much all Linux docs and tutorials.  :)
[13:32] <nhaines> Next time you update with Ubuntu already there, leave off the -b.
[13:32] <nhaines> And don't forget to have fun.  In about 5 minutes, you'll be holding the future.  :)
[13:34] <thumperest> i know :) i wached all the videos on youtube :) i accualy work on LG but it's Turkey brand. Because of that  I want to show them the new operating system.
[13:37] <w-flo> any idea why maliit-server segfaults? in ua_ui_display_get_native_type (), in libubuntu_application_api.so.1.. something with libhybris?
[13:37] <davmor2> asac: is there a bug with individual steps to reproduce that I could work through?
[13:57] <ShapeShifter499> hi
[13:58] <ShapeShifter499> so I ran into this error on compiling.... any ideas? http://pastebin.com/UVg98Qgy
[13:59] <asac> ev: gema_ might have someone who can help you reproducing and testing the whoopsie thingy
[13:59] <ev> thanks
[13:59] <gema_> ev: so what do you need exactly?
[14:01] <ev> gema_: First, confirmation that you're able to reproduce it in the latest images. Then, to try with whoopsie 0.2.22. If that still has the problem, add --assume-online after exec whoopsie in the upstart job and try again. If it's still showing up after that, I'll ask you to run valgrind over it.
[14:01] <gema_> ev: ok, let me find something that can do this
[14:02] <ev> thanks!
[14:02] <ev> very much appreciated
[14:02] <w-flo> never mind, the maliit crash is probably caused by a very outdated platform api bzr checkout (somehow I assumed envsetup.sh would take care of that)
[14:03] <plars> ev: I'm flashing today's image locally right now
[14:03] <ShapeShifter499> *reposting in case anyone who just joined knows*    so I ran into this error on compiling.... any ideas? http://pastebin.com/UVg98Qgy
[14:03] <ev> awesome
[14:03] <sergiusens> dholbach: mhall119 fyi, I wrote up some quick notes here: http://sergiusens.github.io/posts/click-packages-included-on-ubuntu-touch.html
[14:03] <plars> ev: I didn't see it all day yesterday, but it's hit or miss. There's no 100% way to reproduce it that I've been able to find - just reboot and sometimes it shows up, sometimes not
[14:04] <dholbach> sergiusens, woohoo
[14:04] <dholbach> sergiusens, I'll mention it on the @ubuntudev social media channels in a bit
[14:04] <ev> plars: that was my initial experience as well, but I've rebooted *a lot* and haven't seen it in quite a while.
[14:04] <sergiusens> dholbach: ack, I'm always shy of those :-P
[14:04] <ev> hard to debug under those circumstances
[14:04] <dholbach> sergiusens, no no no :)
[14:05] <plars> ev: indeed - or to prove if it's "fixed" :)
[14:05] <ev> valgrind, cppcheck, clang's static analyser, and my own eyeing through the code all come up clean :)
[14:05] <ev> yeah
[14:07] <plars> ev: asac was thinking it was the ueventd eating 100% + upowerd segfault + whoopsie trying to do something with the .crash file on an already busy system, but I don't see it the last times I've had the .crash with 100% ueventd
[14:07] <ev> yeah, same experience here
[14:07] <ev> I've had that ueventd crash lots
[14:08] <ogra_> crash ?
[14:08] <asac> plars: so we have reports that whoopsie goes crazy without a .crash file
[14:08] <asac> thats the main issue i am concerneda bout
[14:08] <asac> beyond that we should disable whoopsie to automatically run anyway i believe
[14:08] <ev> I don't think it's in any way related to processing crash files
[14:09] <asac> also because you definitelydont want to have this run while you are on battery
[14:09] <plars> asac: sure, it's just that ev and I are both having trouble reproducing it yesterday and today
[14:09] <plars> asac: so if you know of someone who is able to get it still, would love to hear from them
[14:09] <ev> the spinning at 100% happens inside the glib event loop
[14:09] <ev> very early on
[14:09] <asac> plars: i know.
[14:09] <asac> at same time i hear what ev says, so... :)
[14:10] <asac> ev: do we see in the strace if its a write or read poll?
[14:10] <ev> whoopsie has been super-stable on the *cough cough*-illion or so machines reporting into daisy.ubuntu.com
[14:10] <asac> ev: those are not phones though ... :)
[14:11] <asac> hehe
[14:11] <ev> :)
[14:11] <asac> anyway. so I would like to see this nailed doown
[14:11] <ev> yeah definitely
[14:11] <asac> and then put whoopsie in manual mode on our phone image though
[14:11] <ev> mm why?
[14:11] <ShapeShifter499> anyone? I think I'm close to building but that error is in my way
[14:12] <ev> we may find that this issue was entirely not whoopsie
[14:12] <asac> ev: well, first i think it consumes quite some resources if a big process crashes
[14:12] <ev> that something broke glib's brain
[14:12] <asac> ev: so if on battery it should sit still anyway :()
[14:12] <asac> so next option is to make it battery aware ... but since i believe thats harder than just setting it to manual mode for now, i felt that would be better
[14:12] <ev> asac: if it's consuming a lot of resources processing a big crash, please do file a bug and raise it with me
[14:12] <ev> that's not by design
[14:13] <ev> it's mostly in a sleep state, save network topology changes
[14:13] <ShapeShifter499> :/
[14:13] <asac> ev: so you say we really want whoopsie processing and submitting crashes while on battery?
[14:13] <ev> I think it's perfectly reasonable for it to submit crashes while on battery so long as it's on wifi
[14:13] <ev> and that's what it does today
[14:13] <ev> it will not send a crash if only on 3G or whathaveyou
[14:14] <asac> grmpf. i really feel any minute of my battery time won is precious
[14:15] <asac> so if it consumes more than 1 minute of battery we should not run stuff that we can have wait for an adapter :)
[14:15] <asac> you can tell if thats the case or not'
[14:15] <annerajb> Shapeshifter, did you remove the compile target for libandroid runtime?
[14:15] <annerajb> and NookParts
[14:15] <annerajb> I believe that error is because of NookParts still being on your Device.MK inside device
[14:15] <ogra_> asac, normal people dont really run around with a charger attached .... if you would only report while on charger and on wlan we wouldnt get many reports
[14:16] <asac> ogra_: the .crash files get saved
[14:16] <asac> just not processed until you are connected
[14:16] <gema_> asac: you should be able to configure that
[14:16] <ogra_> yes, so you collect ten crash files ... plug your phone into the charger and it gets unusable for 10min
[14:16] <gema_> asac: that's a setting on the settings screen for mpt to consider
[14:17] <ev> brb
[14:17] <cyphermox> ChickenCutlass: got indicator-network on my phone now... it mostly works
[14:17] <asac> i dont know. if we have such a crash submission config, then maybe
[14:17] <ogra_> mostly
[14:17] <ogra_> :)
[14:17] <cyphermox> just having an issue with the authentication dialog now
[14:17] <asac> otoh, we dont loose much by just not submitting when on battery
[14:17] <asac> without having user be able to opt in :)
[14:18] <plars> ev: we're gathering top data at each test run now, and I've looked through almost 40 test runs across 2 different types of devices so far, and none of them had the whoopsie issue so far
[14:18] <asac> ogra_: i am sure the device should never be unusable while it processes crashes
[14:18] <asac> if it is, it shouldnt run automatically, but only if user explicitely wishes
[14:18] <asac> like manual
[14:18] <ogra_> asac, if all cores go to 100% it will be unusable
[14:19] <asac> sure, if thats the expected behaviour, then lets go straight to manual submission through cmline and later crash notification
[14:19] <ogra_> (or if your IO gets to bad)
[14:19] <gema_> asac: I don't think people will like that
[14:19] <gema_> asac: that would be a deterrent for some users, imo
[14:20] <gema_> asac: and may end up sending some user data that is illegal without user permission in many countries
[14:20] <asac> gema_: what exactly? automatically sending? or manually sending?
[14:20] <gema_> asac: automatically sending
[14:20] <asac> cool. so we have our answer
[14:20] <gema_> asac: you need to give the users a way to opt out
[14:21] <plars> in android, it's something you are forced to decide when you boot the phone for the first time, and it can also be turned on/off in settings
[14:21] <gema_> plars: yep, because it is a legal requirement to let people choose what their phone sends
[14:22] <plars> gema_: not sure if you saw what I posted earlier, the new top stuff we added gives us logs that show whoopsie hasn't dont the cpu killing to us at all today so far
[14:22] <gema_> plars: didnt' see it, ev ^^
[14:23] <plars> gema_: of course it's hard to call it "fixed", but at least across the 10 or so reboots I've done here today alone, plus lots yesterday, plus 40 or so from this morning's automated builds, it's not easily reproducible at the moment
[14:24] <gema_> plars: om26er was telling me one of our upstream merger phones died of it
[14:24] <gema_> om26er: what image where you using?
[14:24] <plars> om26er: "died"?
[14:25] <ShapeShifter499> annerajb, no, no I did not
[14:26] <annerajb> Shapeshifter, give that a try
[14:27] <annerajb> ShapeShifter499, https://gist.github.com/bbelos/5078404#file-patch_device_epicmtd_ubuntu YOu should have a codename.mk file and there is a target that says codenameParts
[14:27] <om26er> gema_, latest (from 2days), I guess. I sent an email to rfowler
[14:27] <om26er> plars, died as in vanished
[14:29] <annerajb> ogra_, is it ok that i add that to the wiki?
[14:29] <gema_> om26er: it may be time to reimage if the problem is solved
[14:31] <ShapeShifter499> annerajb, I'm not seeing that file
[14:31] <pmcgowan> ChickenCutlass, cyphermox re bluetooth entering the build, which use cases do we think we will/can target right now
[14:32] <annerajb> What's your device codename?
[14:32] <ShapeShifter499> annerajb, oo wait
[14:32] <ShapeShifter499> xD
[14:33] <ShapeShifter499> annerajb, I have a file called full_hummingbird.mk     it does not have a line in it with any version of "hummingbirdParts"
[14:33] <annerajb> you dont have a hummingbird.mk?
[14:34] <ShapeShifter499> annerajb, it's the Nook HD, the code name is Hummingbird
[14:34] <ShapeShifter499> annerajb, no
[14:34] <ogra_> pmcgowan, bluettooth will be in this evenings build
[14:34] <ogra_> well, bluetooth-touch will ... no indicator yet
[14:35] <annerajb> ShapeShifter499, then i am not sure what to do. here is my devices codename.mk file https://github.com/CyanogenMod/android_device_samsung_epicmtd/blob/gingerbread/epicmtd.mk
[14:35] <pmcgowan> ogra_, cool
[14:36] <annerajb> ShapeShifter499, are you sure cyanogen mod supports hummingbird? The readme of that repository says nothing here yet dont get excited
[14:36] <annerajb> so it may not be supported
[14:36] <ShapeShifter499> annerajb, it's supported in nightlybuilds
[14:37] <ShapeShifter499> nightly builds*
[14:37] <popey> ev / gema_ / plars - I wrote a script to reboot the phone N times and report vmstat for a while, I see nothing gobbling cpu anymore... http://paste.ubuntu.com/5989256/
[14:37] <ryukafalz> Just flashed my Nexus 7 with Ubuntu Touch, I see the wifi network list works now, but is there not yet an option to enter keys for a WPA2 network?
[14:39] <mfisch> beuno: ping
[14:40] <ogra_> popey, so we should just ship yoour script then
[14:40] <popey> hah
[14:40] <plars> popey: ueventd does still often go for the cpu buffet
[14:41] <plars> popey: but the whoopsie one seems unreproducible now
[14:41] <dobey> mardy: what's the way to propose brnches to lp:signon and such? it appears some stuff is on google code and some stuff not, so it's not clear what is the correct way to propose changes
[14:41] <popey> http://bazaar.launchpad.net/~popey/+junk/phablet-flash-wrapper/revision/22#test-reboot.sh   is my manky script
[14:41] <popey> don't all laugh
[14:42] <popey> mine has had software installed, lemme run it again after a clean flash
[14:42] <sergiusens> popey: so if it's just the one you are ok with the lols? :-P
[14:42]  * sergiusens jokes early today
[14:42] <popey> ☻
[14:42] <ShapeShifter499> annerajb, if you have anymore possible ideas on this issue could you please PM them, I'll be idle for a while
[14:42] <popey> comedy gold
[14:42] <popey> which I have seen both whoopsie and ueventd crash more on - a clean flash
[14:44] <ev> gema_: we're already cleared legally on sending data
[14:44] <ev> asac: ^
[14:44] <ev> I've had conversations with Katherine about it
[14:44] <popey> \o/ Send all the data
[14:45] <ev> without data we're flying blind
[14:45] <ev> you can't control what you can't measure and all that jazz
[14:45] <ogra_> get a guiding dog then :)
[14:45] <ogra_> asac pays
[14:45] <gema_> ev: ack
[14:46] <ev> specifically: https://docs.google.com/a/canonical.com/document/d/1JHFd_6mYdUTd0RpR-Sm7-WnX-06rY8r58K3Cz32mhJg/edit#heading=h.ldl3hf7jg66m
[14:50] <popey> aha!
[14:51] <popey> first boot after flashing, I get ueventd 100%
[14:51] <popey> but the previous 10 reboots I didn't
[14:52] <ev> I definitely understand that we want to be as battery sensitive as possible, but I'm also acutely aware that the more we delay whoopsie running, the more space we put between the OS and it running, the more issues we're not going to get error reports for. Issues we'll be entirely blind to.
[14:52] <ev> If whoopsie is heavy on your system, let me know about it and I will fix it. It's written to be a very lightweight, down to the metal process.
[14:52] <ev> popey: just ueventd?
[14:52] <popey> yes
[14:54] <ev> I'm going to flash with an older image that we know to be broken and see if I can figure out what's causing whoopsie so much pain (it hasn't changed in the time we stopped seeing the issue, so I'm assuming it's something else knocking it over from here).
[14:56] <ev> could someone kindly just confirm that the image I'm after is this one: http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130812/
[14:58] <mfisch> Saviq: is there someone on your team I can talk to about customizing the launcher icons?
[14:59] <Saviq> mfisch, better wait for it, it's coming soon
[14:59] <Saviq> mfisch, but mzanetti|otp is the one
[14:59] <ogra_> ev, how would we know ... if you are after the flipped image from august 12th thats the right one though :)
[14:59] <ev> ogra_: to clarify. Is that an image we knew to have ueventd and whoopsie spinning at 100%
[15:00] <ev> I'm pretty sure it is, but I don't want to go off testing for hours and find out I was wrong :)
[15:01] <ogra_> ev, all images have the ueventd issue ... and i think the weekendish ones had the whoopsie one
[15:01] <ogra_> 12th should still be broken ... 11th might be safer
[15:01] <mfisch> Saviq: thanks, mzanetti|otp: can I get some directions on how to interact with it?
[15:01] <Saviq> mfisch, you can't yet
[15:02] <ev> okay, I'll grab the 11th. Thanks ogra_!
[15:02] <mfisch> Saviq: right, but we're making plans so I'd like to have a general idea
[15:03] <Saviq> mfisch, let me fwd you a design video
[15:03] <mfisch> Saviq: perfect
[15:03] <w-flo> using the GUI to connect to my wifi network used to work, but now it doesn't ask for my WPA key (20130814.1). is that a known issue? Can't find a bug report
[15:04] <dednick> who do i talk to to get some seeds for ubuntu-touch changed?
[15:04] <ChickenCutlass> pmcgowan, re: bluetooth.
[15:05] <ChickenCutlass> pmcgowan, all depends on what settings UI is implemented
[15:05] <ChickenCutlass> pmcgowan, BT is now enabled and can be used however we want
[15:05] <pmcgowan> ChickenCutlass, I found some emails and notes, will work on a list
[15:05] <jedidiah> w-flo: I've been having the same problem.
[15:05] <pmcgowan> ChickenCutlass, right agreed
[15:06] <w-flo> jedidiah, maybe we should open a bug report
[15:06] <dobey> mardy: https://code.launchpad.net/~dobey/signon/dynamic-plugins-lib/+merge/180355
[15:21] <popey> another 10 reboots post clean flash.. http://paste.ubuntu.com/5989397/ - no whoopsie
[15:21] <popey> (no whoopsie cpu nomming)
[15:23] <mzanetti> mfisch: what exactly do you want to do?
[15:23] <mzanetti> Saviq: what do you think about this? https://code.launchpad.net/~unity-team/unity8/unity8.background-gsettings-fix/+merge/179884
[15:24] <mzanetti> Saviq: seems the merge is actually ok, but it increases chances of some crash in some other part :/
[15:24] <Saviq> mzanetti, crash is fixed already in https://code.launchpad.net/~mhr3/unity/only-valid-filters
[15:24] <Saviq> mzanetti, just not released yet
[15:24] <mzanetti> Saviq: you sure it's the same one?
[15:25] <Saviq> mzanetti, well we don't have cores
[15:25] <Saviq> mzanetti, but yes, I'm positive
[15:25] <Saviq> mzanetti, I've had 10 crashes in ~150 runs of the shell
[15:25] <mzanetti> Saviq: ok then. I think the background one can be merged now. as I wrote half of it someone else must approve
[15:25] <Saviq> mzanetti, all the same
[15:25] <mfisch> mzanetti: we're working on defining image customization, so imagine that your carrier or OEM wants to ship some special app and wants it to be in the launcher
[15:25] <Saviq> mzanetti, and fixed by the unity fix
[15:25] <Saviq> mfisch, gsettings override
[15:26] <ev> hm, is phablet-flash cdimage-touch --base-path ~/Downloads/phablet-flash/ubuntu-touch/20130811 not what I want for flashing an old image? It seems to ignore it and go for today's
[15:26] <Saviq> mfisch, same key as on desktop
[15:26] <mzanetti> mfisch: right... we will use gsettings
[15:26] <mzanetti> mfisch: so the customization will be able via a default config
[15:26] <mfisch> mzanetti: perfect, we have a solution for that, we can drop in a 2nd dconf db
[15:26] <mzanetti> mfisch: it's not implemented yet tho
[15:27] <mzanetti> mfisch: there are 2 merge proposals for the launcher in review currently and once those are merged, the next step is the gsettings stuff
[15:27] <mzanetti> mfisch: so work on it should start beginning of next week
[15:28] <mfisch> mzanetti: as long as we have a plan we can work with your schedule
[15:28] <mfisch> mzanetti: is the wallpaper setting part of that work too?
[15:28] <mzanetti> Wellark: mfisch: you 2 might want to sync about this
[15:28] <mzanetti> mfisch: don't think so... but that one uses gsettings too as soon as this is merged: https://code.launchpad.net/~unity-team/unity8/unity8.background-gsettings-fix/+merge/179884
[15:29] <mzanetti> mfisch: I don't know if its the same db or such. (I'm new to gsettings)
[15:30]  * mzanetti is off to the next meeting
[15:30] <mfisch> mzanetti: I've got dconf/gsettings figured out as long as you're using it ; )
[15:31] <ev> ah, it's a bug
[15:33] <cyphermox> pmcgowan: re: bluetooth do you mean how it can be used right now?
[15:34] <cyphermox> what we will be able to do is add system tests now to make sure bluetooth comes up and mostly works
[15:34] <pmcgowan> cyphermox, yes, I want to reconrd  the priorites for profiles
[15:34] <cyphermox> oh ok
[15:34] <pmcgowan> such as handsfree, a2dp
[15:34] <cyphermox> that's different
[15:34] <pmcgowan> right whats exposed
[15:34] <cyphermox> right now, you can do all that, but it's all manual, since there is no UI
[15:35] <cyphermox> but you'll be able to do handsfree, a2dp, hid, etc.
[15:35] <cyphermox> Saviq: ping?
[15:36] <cyphermox> Saviq: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1017/  <--- some unity8 test failures, could you please look into them?
[15:36] <Saviq> cyphermox, bug #1212580
[15:37] <cyphermox> ack
[15:37] <Saviq> cyphermox, need unity to release
[15:37] <cyphermox> ok, that should be happening in the next few minutes
[15:37] <cyphermox> (hopefully)
[15:41] <balloons> m-b-o, what is the dependency for Components.Storage module "QtQuick.LocalStorage"
[15:46] <m-b-o> balloons: qtdeclarative5-localstorage-plugin
[15:46] <m-b-o> balloons: it's missing, right?
[15:46] <annerajb> does anyone know if adbd is blocking??
[15:47] <balloons> m-b-o, yes I'd guess so as the tests don't run in the virtual sandbox complaining about that dependency
[15:47] <m-b-o> balloons: okay, will try to add this today :)
[15:48] <rtg_> when trying to flash an N4, what does this mean ?
[15:48] <rtg_> rtg@x120e:~$ adb root
[15:48] <rtg_> adbd cannot run as root in production builds
[15:49] <balloons> m-b-o, ok, yea a quick check for any missing dependencies would be good
[15:51] <annerajb> rtg, did you sudo adb root?
[15:51] <rtg> nope, didn't used to have to do that.
[15:51] <annerajb> some people where having trouble yesterday and they fixed it by sudoing
[15:51] <rtg> no difference
[15:52] <sergiusens> rtg: you shouldn't need that to flash.... but it means your device is not rooted (missing su)
[15:52] <rtg> sergiusens, so phablet-flash -b should work ?
[15:52] <sergiusens> rtg: yes
[15:52] <sergiusens> rtg: phablet-flash cdimage-touch -b
[15:53] <sergiusens> rtg: if you get <waiting for device> or adb errors when in recovery it means that the udev rules aren't doing the right thing (they do if you have seat)
[15:54] <m-b-o> balloons: https://code.launchpad.net/~martin-borho/ubuntu-weather-app/missing_dependency/+merge/180368 there you go :)
[15:55]  * sergiusens goes for lunch for real now
[15:55] <rtg> sergiusens, that looking better. forgot the '-b' option on prior attempts
[15:56] <sergiusens> rtg: yeah, you miss using a workable recovery image with no -b
[15:57] <rtg> segastep, well, also I was replacing the factory android image
[15:57] <rtg> sergiusens, ^^ (stupid tab completion)
[15:58] <segastep> :D
[15:58] <segastep> got a fright like, errmm, who would be highlighting me in here :O only been in here 2 days
[16:02] <balloons> m-b-o, let me re-run before we merge the commit
[16:05] <rtg> I'm sort of underwhelmed by the inability to enter a password into a WPA protected wifi network
[16:06] <ogra_> rtg, attach to a laptop and use phablet-network-setup
[16:06] <ogra_> that copies the wlan config over
[16:06] <nhaines> rtg: it worked a couple of days ago.  :)
[16:06] <nhaines> rtg: It's pretty annoying, though.
[16:06]  * ogra_ saw someone else complain about it today 
[16:07]  * w-flo and jedidiah complained earlier
[16:07] <rtg> ogra_, will do
[16:07] <gema_> asac: ping
[16:07] <dednick> ogra_: ping
[16:08] <ogra_> dednick, hey
[16:08] <m-b-o> balloons: okay, will be off next 2h
[16:08] <dednick> ogra_: hi. we need to change ubuntu-touch seed to replace indicator-time with indicator-datetime, and indicator-battery with indicator-power
[16:09] <mhall119> sergiusens: ping
[16:09]  * ogra_ hugs dednick .... you wont belive how long i waited for this ping :)
[16:09] <ogra_> dednick, so everything is in the archive ?
[16:10] <asac> gema_: ouch
[16:10] <asac> gema_: dont wait 10 minutes
[16:10] <asac> before pinging ... brt
[16:10] <gema_> asac: we are , wanna postpone?
[16:10] <asac> NONONON :)
[16:10] <gema_> asac: no worries we were fixing other stuff
[16:10] <dednick> ogra_: yep, as far as i know!
[16:10] <asac> just 2 minutes for getting rid of this IRC noise :)
[16:11] <dednick> ogra_: well, it's the same we use on saucy, so i guess so.
[16:11] <ogra_> good
[16:13] <ogra_> dednick, have they been tested to not fail the tests ?
[16:13] <ogra_> i.e. by a manual test run on the phone
[16:13] <nhaines> Wait, what's this about a phablet-network-setup?
[16:14] <ogra_> nhaines, phablet-tools ships it ... it copies wlan configs from host to the phone
[16:14] <dednick> ogra_: we're removing tests from unity8
[16:14] <ogra_> dednick, is that talked through with asac ?
[16:14] <nhaines> ogra_: grr, I didn't know that.  Would've saved some time!  What other fun things have I missed?  Thanks.  :)
[16:15] <ogra_> dednick, packages that break tests or add regressions to teh image tests are not allowed in
[16:15] <ogra_> (or need an approval from asac or rickspencer3)
[16:16] <dednick> ogra_: um. ok. we're removing the tests for battery i mean. as it's not going to exist anymore.
[16:16] <ogra_> thats fine i guess
[16:16] <dednick> ogra_: but i guess we have to do that before, as it will break image tests if battery goes first
[16:16] <ogra_> the above is more about regular tests for existing stuff indeed :)
[16:19] <ogra_> dednick, will the test removal happen today ?
[16:20] <dednick> ogra_: just speaking with Saviq about it
[16:20] <ogra_> k
[16:20] <ogra_> i assume its just a matter of deleting code :)
[16:23] <dednick> ogra_: we're going to do it all tomorrow. too late in the day. :)
[16:23] <ogra_> ok
[16:36] <annerajb> ogra_, i changed the touch script to start adb on the first 5 lines but not panic. that provided interesting results. dmesg is full of ecc and bad blocks thought not sure if that's normal. thought i am still fixing some issues with adb spawning.
[16:37] <annerajb> it's like when i join thought gdb my whole /root has been deleted so no commands work
[16:37] <ogra_> uh
[16:37] <annerajb> adb*
[16:37] <annerajb> but ubuntu is mounted
[16:37] <ogra_> sounds like your flash is really unhappy
[16:38] <annerajb> ogra_, kinda i read that that's a normal amount of bad blocks.
[16:38] <ogra_> well, probably it needs a special way of formatting it
[16:39] <ogra_> or can only handle certain filesystems
[16:39] <annerajb> why? bad blocks is suppose to be normal. since it's because of the wear levelling algorithm on the nand controller
[16:39] <annerajb> i read a post on people reporting 8-15 bad blocks the first day of getting the phone.
[16:41] <ogra_> well, if it is empty ...
[16:41] <ogra_> and you see badblocks and ecc messages ...
[16:42] <annerajb> ogra_, i dont understand how the process of handling over to the rootfs works. but i think this is what happening (is it plausible). My initrd started ADB stays hanging around AFTER the rootfs has been mounted. When i switch to the rootfs "chroot" i am connecting to the old adb
[16:42] <annerajb> but the initrd is unmounted hence me seeign no files
[16:42] <ogra_> no
[16:42] <ogra_> first /data is mounted ... then /data/ubuntu is bindmounted to /root
[16:43] <ogra_> then run-init switched to /root as /
[16:43] <annerajb> but what happens if adb was spawned before the bind mount will it go into this weird state?
[16:44] <ogra_> it shouldnt
[16:44] <annerajb> ok
[16:44] <ogra_> but its adb, you never know :)
[16:44] <annerajb> lol
[16:44] <ogra_> (its an android binary compiled on a normal linux system)
[16:44] <ogra_> (there can indeed be bugs nobody knows about yet)
[16:45] <annerajb> if this adb spawning dosnt work i was thinking of mounting /sdcard/ in the touch script and printing out a bunch of output to it
[16:45] <ogra_> you know that you can add beark= to the kernel cmdline yo bring up adb in different stages of the initrd ?
[16:45] <annerajb> no
[16:45] <Hashcode> ogra_ When did the cmdline datapart= parameter get added? :))
[16:45] <annerajb> so i can add to the cmdline break=adb
[16:45] <ogra_> i would revert the change and try something like break=mount
[16:46] <annerajb> ok
[16:46] <annerajb> how do i continue after i am breaked or paused?
[16:46] <ogra_> Hashcode, yesterday ... but there is still support for systempart= needed that i didnt get to yet
[16:46] <Hashcode> ogra_ very nice!
[16:47] <ogra_> annerajb, sadly you cant in this setup (on a PC you would just exit the shell which makes it continue booting, with adb that runs a daemon thats not possible)
[16:47]  * annerajb that usb serial console starts sounding tempting again
[16:47] <ogra_> annerajb, but break=mount should give you the shell at a stage where the complete mounting is done and where you are rigth before the switch to the new root
[16:48] <ogra_> so exactly the point you want to inspect ...
[16:48] <annerajb> i would have to spawn adb before the mount so i can connect to it correct?
[16:48] <ogra_> no
[16:48] <ogra_> leave the script as it origianlly is wrt adb
[16:48] <ogra_> remove all your changes
[16:49] <ogra_> (apart from the sleep and the hardcoded device name)
[16:50] <ogra_> then boot with break=mount ... and you should be able to inspect whats in /root and if you get any dmesg errors etc
[16:53] <annerajb> ogra_, how do i connect to the shell that break will gime me. ie. how do i see that shells output and interact with it?
[16:54] <ogra_> adb shell ?
[16:54] <annerajb> ok
[16:57] <mhall119> pmcgowan: what's going on with HUD?  One day I have browser actions in it, the next day they're gone again :(
[16:58] <ogra_> HUD is overrated
[16:58]  * mhall119 loves the HUD
[16:58] <pmcgowan> mhall119, better than me I never have any
[16:58] <ogra_> use gestures
[16:58] <mhall119> IMO, HUD is the most under-rated thing we've got going on in Unity
[16:58] <mhall119> and I want to see *more* of it
[16:59]  * ogra_ only sees the hud if he accidentually hits the alt key
[16:59] <pmcgowan> mhall119, I think ites getting a design "improvement"
[16:59] <ogra_> (and thats mostly annoying)
[16:59] <mhall119> ogra_: OMG, you have to try it on Gimp or Inkscape
[17:00] <mhall119> or even QtCreator when it's working with global menu
[17:00] <ogra_> well, i rarely use these :)
[17:00] <clouder_> hello, is there anyone who could help me with an odd issue while installing Ubuntu Touch on a Nexus 4?
[17:00] <mhall119> I liked it on the phone with webbrowser-app too
[17:00] <mhall119> for adding bookmarks
[17:00] <mhall119> clouder_: what's the issue?
[17:00] <ogra_> bookmarks ?
[17:01] <mhall119> ogra_: yeah, we have bookmarks now
[17:01] <ogra_> i wasnt aware it can ...
[17:01] <mhall119> 12:58 < mhall119> ogra_: OMG, you have to try it on Gimp or Inkscape
[17:01] <mhall119> ogra_: during the brief times when HUD was working, there was an "Add to Bookmarks" action
[17:01] <ogra_> nice
[17:01] <mhall119> and you could get to them from the Activity view
[17:01] <ogra_> i must admit i dont even test the HUD much ... since i got used to it being always empty
[17:02] <mhall119> it was nice, but without HUD it's useless
[17:02]  * ogra_ would like to have the close action back though
[17:02] <mhall119> me too
[17:02] <ogra_> i really liked it ... and the new way is so painful
[17:02] <clouder_> mhall119: well, actually the device is unlocked but when i try installing via "phablet-flash cdimage-touch -b" it goes to reboot and the terminal says "Device needs to be unlocked for the following to work" and starts bootloader
[17:02] <mhall119> I also want to know what to do with the other HUD toolbar actions
[17:03] <mhall119> clouder_: did you unlock the bootloader?
[17:04] <clouder_> mhall119: yes, i did -> "LOCK STATE - unlocked"
[17:05] <mhall119> and did you enable USB debugging in the android settings?
[17:05] <ogra_> https://wiki.ubuntu.com/Touch/Install#Step_3_-_Initial_Device_Setup
[17:05] <clouder_> mhall119: of course, i had to initialize the flashing with the usb debugging
[17:06] <ogra_> just go throug all these steps one by one again
[17:06] <ogra_> to make sure you didnt miss anything
[17:06] <clouder_> could it be that i have to run the commands as root?
[17:07] <ogra_> that would result in a different error message
[17:07] <ogra_> do you see an open lock under the google logo when booting ?
[17:08] <clouder_> yes
[17:10] <clouder_> maybe it is because of hardware version rev_11, are there known issues with newer devices, it's a replacement device for an older one
[17:10] <ogra_> would be the first time i hear of it
[17:10] <annerajb> ogra_, if i flash a boot.img would that include all changes to kernel and initrd?
[17:10] <ogra_> what else does it print beyond the message above
[17:11] <chrisd_> hi guys
[17:11] <annerajb> hi
[17:11] <ogra_> annerajb, depends on the device :) on my galaxy S2 the noot.img is actually the kernel only
[17:11] <ogra_> *boot
[17:11] <annerajb> ok
[17:11] <chrisd_> I created a site dedicated to ubuntu touch. long live the phablet user http://bit.ly/14NRxpm
[17:11] <ogra_> (and i still havent figured out how it installs the initrd)
[17:12] <clouder_> http://pastebin.com/XeyDPE60
[17:12] <clouder_> that's the complete action
[17:13] <ogra_> < waiting for device >
[17:13] <ogra_> thats your issue
[17:13] <clouder_> and with waiting for device it goes to bootloader and stays tere
[17:13] <ogra_> the rest are just infos and warnings
[17:13] <clouder_> *there
[17:14] <ogra_> sergiusens, doesnt phablet-flash do privilege escalation at that point ? ^^^
[17:14] <sergiusens> ogra_: no, it relies on the udev rules
[17:14]  * ogra_ thought it would ask for the sudo PW to run fastboot to flash
[17:14] <ogra_> oh, ok
[17:14] <clouder_> no, it doesn't
[17:14] <ogra_> clouder_, then try with sudo i guess
[17:15] <clouder_> but it seams to be the issue
[17:15] <clouder_> yes, it does something :)
[17:15] <sergiusens> ogra_: people with custom udev rules or not the packaged ones will land in failure
[17:15] <sergiusens> or with devices with unlanded udev rules
[17:15] <ogra_> sergiusens, we need to go through these rules ... i cant belive all these people have manually created udev rules
[17:15] <ogra_> (one day that is ... )
[17:16] <sergiusens> ogra_: oh, well popey for example didn't have seat
[17:16] <sergiusens> as in not logged in
[17:16] <ogra_> in PK ?
[17:16] <ogra_> wow
[17:16] <popey> was a laptop sat next to me, not logged into desktop
[17:16] <ogra_> well, might be the seat concept vanished with logind ?
[17:16] <popey> I was lazy, ssh'ed into it to do the phablet-flash
[17:16] <ogra_> ah
[17:16] <ogra_> ssh ...
[17:17] <sergiusens> ogra_: not sure what the best, secure and friendly approach is here...
[17:17] <popey> i wanted to have a machine I could leave running doing phablet-flash and testing
[17:17] <popey> so i set it to autologin instead ☻
[17:17] <ogra_> sergiusens, sudo :)
[17:18] <sergiusens> ogra_: yeah, maybe it is...
[17:18] <sergiusens> :-P
[17:18] <clouder_> Error; Command adb push returned non-zero exit status 1   doesn't sound good :/
[17:19] <clouder_> stucks at Google logo
[17:19] <ogra_> clouder_, hmm, is your /data partition full ?
[17:19] <clouder_> ogra_ how to empty?
[17:19] <sergiusens> --wipe
[17:20] <ogra_> well, he is doing -b
[17:20] <sergiusens> oh...
[17:20] <ogra_> i thought that implies --wipe ?
[17:20] <sergiusens> yes
[17:20] <sergiusens> full logs?
[17:20] <ogra_> (thats a mako btw)
[17:22] <clouder_> when it is flashed with Ubuntu Touch, does it stills how the Google Logo?
[17:22] <clouder_> *show
[17:22] <ogra_> yes
[17:23] <clouder_> ok, I guess i'll wait a few minutes, maybe it boots… some day
[17:24] <ogra_> well, is it doing something in your terminal ?
[17:24] <Wellark> mfisch: please, drop me an email on your requirements or something so I don't forget
[17:25] <ogra_> if you just expect it to boot after the above error i doubt you will get lucky
[17:25] <clouder_> the terminal finished the flashing command with the error adp push returned non-zero exit status 1
[17:25] <mfisch> Wellark: will do
[17:25] <ogra_> rightm that means it didnt flash
[17:26] <mfisch> Wellark: but if it's in dconf we'll be fine I think
[17:26] <clouder_> DOWNLOAD MODE
[17:28] <sergiusens> clouder_: logs?
[17:28] <sergiusens> pastebin stdout
[17:28] <clouder_> of my computers terminal?
[17:28] <sergiusens> yes
[17:28] <ogra_> yes, like the one you pasted before
[17:30] <clouder_> http://pastebin.com/kuF8f8au
[17:30] <Wellark> mfisch: as long as you don't have a requirement that the user is not allowed to remove the predefined apps from the launcher
[17:30] <mfisch> Wellark: that's a good question, I still need to figure that out
[17:30] <annerajb> ogra_, i think the break mount is hitting a earlier mount point it dosnt even print the (echo "initrd: mounting $path" >/dev/kmsg || true)
[17:30] <mfisch> Wellark: we can lock the key but then nothing can change
[17:31] <sergiusens> clouder_: protocol failure
[17:31] <ogra_> protocol failure
[17:31] <sergiusens> ogra_: seems we have one more user with this problem
[17:31] <ogra_> bad cable ?
[17:31] <clouder_> original one
[17:31] <ogra_> sergiusens, yeah plars said he sees them too during tests
[17:32] <sergiusens> ogra_: it can be: cables, adb mishap, fiddling with the device mid push
[17:32] <ogra_> yeah
[17:32] <mfisch> Wellark: I'm meeting with Richard Collins on Monday and I'll know more then
[17:32] <sergiusens> clouder_: stay in recovery and run the same command but add -d mako
[17:33] <sergiusens> clouder_: and don't touch the device
[17:33] <sergiusens> unless the command line output tells you too
[17:33] <ogra_> annerajb, hmm. probably it is postmount then ...
[17:33] <sergiusens> to -o
[17:33] <w-flo> can I add something to my phablet-flash manifest.json to ensure there's more than x mb of free space on /data and make phablet-flash show an error message otherwise? Or maybe a manifest flag to force wiping? Right now the device gets bricked every time I forget to --wipe
[17:33] <ogra_> annerajb, gimme a sec
[17:33] <annerajb> ogra_, mk
[17:33] <ogra_> annerajb, break=bottom
[17:34] <ogra_> sorry, my fault
[17:34] <sergiusens> w-flo: we can add a wipe check ... but lets not do it automatically
[17:34] <clouder_> ok, but first i have to get android started xD
[17:34] <ogra_> mount srops exactly before the mounting
[17:34] <sergiusens> clouder_: no, just go into recovery
[17:34] <ogra_> *stops
[17:34] <clouder_> ok, ill try
[17:36] <clouder_> but what the hell is download mode ? o.ô
[17:36] <sergiusens> clouder_: it's another provisioning mechanism
[17:36] <plars> sergiusens: I think it's just a bug or flakiness in adb, I don't think any of those potential causes are affecting us in the lab
[17:36] <balloons> boiko, mihir, calculator is now gated :-)
[17:36] <sergiusens> plars: actually, I thought of one and you casually weren't in the dailies that day
[17:36] <boiko> balloons: great! thanks
[17:37] <w-flo> sergiusens, a wipe check sounds like a good idea. Basically it's a requirement for some devices
[17:37] <plars> sergiusens: I sometimes have overlapping meeting, sorry :( I'm there when I can be
[17:37] <sergiusens> plars: doanac` mentioned something to me which raised a spark... he mentioned the he might be doing an adb kill-server, adb start-server to avoid an issue with rebooting into recovery and being able to use wait-for-device
[17:38] <sergiusens> plars: if you kill the server mid op, you get protocol error
[17:38] <sergiusens> plars: and since you run jobs in parallel, might be the cause
[17:38] <sergiusens> plars: does my assumption hold?
[17:40] <plars> sergiusens: no, we are not doing kill-server
[17:40] <plars> sergiusens: also, we've been getting the protocol errors much longer than that
[17:40] <sergiusens> plars: then my assumption does not fall through...
[17:41] <plars> sergiusens: what he was talking about was killing adbd on the device
[17:41] <ogra_> for the rndis stuff, yeah
[17:41] <sergiusens> plars: ok, so during the sprint we can probably stress this case and find out where it is
[17:41] <ogra_> i think its adbd
[17:41] <clouder_> it worked :)
[17:41] <jono> Saviq, hey
[17:41] <sergiusens> ogra_: adbd tends to fail from time to time
[17:41] <ogra_> clouder_, congrats !
[17:41] <Saviq> jono, oi!
[17:41] <clouder_> thatnk's for your awesome help
[17:41] <jono> any idea when the click scope will land in the device images?
[17:41] <clouder_> *thank's
[17:42] <ogra_> sergiusens, right
[17:42] <sergiusens> ogra_: I might just need to add a retry strategy
[17:42] <ogra_> jono, it is seeded since two weeks or so
[17:42] <annerajb> ogra_, reboot loop :( ima reflash again in case i broke something
[17:42] <plars> sergiusens: so... launching with upstart no longer works for me, on click and non-click packages. Could be that we are just still missing pieces that tedg described?
[17:42] <ogra_> jono, but i think there is backend integration missing
[17:42] <jono> ogra_, aha
[17:42] <jono> any idea when that might be resolved?
[17:43] <sergiusens> plars: yeah, that's what I think I mentioned in that meeting we had... it didn't work for me, I didn't have time to research on it though
[17:43] <ogra_> jono, nope, i dont even know who works on it
[17:43] <jono> ogra_, np
[17:43] <plars> sergiusens: I tried last night when I was trying to help thomi, and even launching from unity didn't work. But this morning that works, just upstart launching fails
[17:43] <sergiusens> jono: ogra_ I think it's ralsina 's team
[17:43] <ogra_> ah
[17:44] <annerajb> ogra_, cant get into recovery :(
[17:44] <ogra_> annerajb, did you force the kernel cmdline in your kernel config ?
[17:44] <annerajb> ogra_, yes
[17:44] <ogra_> the bootloader sets it dynamically on samsung devices ....
[17:44] <sergiusens> plars: oh, so launching from unity required an updated image (20130813.1 I think it was)
[17:45] <ogra_> annerajb, then you wont be able to use recovery ... it needs the flag from the bootloader
[17:45] <annerajb> ogra_, why doesn the datapart cmdline get's removed too?
[17:45] <annerajb> it was when i added the break bottom
[17:45] <sergiusens> plars: so you did something like /sbin/initctl start application APP_ID=com.ubuntu.dropping-letters_0.1.12 iirc
[17:46] <ogra_> annerajb, where did you add it ?
[17:46] <plars> sergiusens: yeah, I tried that, except with /sbin/start
[17:46] <ogra_> to the kernel cmdline in the kernel config ?
[17:46] <plars> sergiusens: /sbin/start application APP_ID=phone-app used to work for me, but now does not
[17:46] <plars> sergiusens: did that as a sanity check, since it's not click
[17:46] <annerajb> ogra_, CONFIG_CMDLINE="console=ttyFIQ0 no_console_suspend=1 datapart=/dev/mtdblock3 console=tty1 break=bottom"
[17:46] <sergiusens> plars: should be the same I think... so that's the issue I was having in the meeting that I mentioned to tedg ... the upstart logs complained about zeitgeist
[17:47] <sergiusens> plars: any clues in the upstart log btw?
[17:47] <ogra_> annerajb, well, if you set it to force it will ignore the bootloader settings and just use this
[17:47] <annerajb> how do you set it to forced?
[17:47] <ogra_> in the kernel config
[17:47] <ogra_> something_CMDLINE_FORCE
[17:47] <ogra_> if thats set it will only use this one
[17:49] <plars> sergiusens: just that it terminated with status 1
[17:50] <mardy> dobey: thanks, but I'm afraid we really need the static library when building the plugins
[17:50] <sergiusens> plars: cat .cache/upstart/application-click-com.ubuntu.dropping-letters_0.1.2.2.log
[17:50] <sergiusens> plars: http://paste.ubuntu.com/5989899/
[17:51] <mardy> dobey: that stuff is rather old (and wrong) and I'm afraid it's impossible to fix without breaking the current plugins
[17:51] <sergiusens> plars: that's my error
[17:51] <awe> cyphermox, ping
[17:51] <plars> sergiusens: ah, ok
[17:51] <plars> sergiusens: yes I'm getting some zeitgeist error too
[17:53] <annerajb> ogra_, i see CONFIG_CMDLINE_FORCE=y (it has it enabled)
[17:53] <ogra_> right
[17:53] <annerajb> is that the line you where referring too?
[17:53] <ogra_> yes
[17:54] <annerajb> ok i am going to compile a kernel with that i made the cmdline shorter by removing a console=tty0 i had there.
[17:54] <annerajb> just in case is running out of space on the buffer.
[17:54] <ogra_> it is a selection option ... there are three and only one of them can be set at a time
[17:54] <annerajb> the only one set is forced
[17:54] <annerajb> the other two are not set
[17:54] <ogra_> upstart wont work withot a console=tty1 at the end
[17:55] <ogra_> (of the cmdline)
[17:55] <annerajb> ok i put it back in.
[17:55]  * annerajb goes get water for hot chocolate while it builds 
[17:55] <ogra_> no, stop it
[17:55] <ogra_> dont build yet
[17:56] <dobey> mardy: how so?
[17:58] <clouder_> is it just me or isn't it possible to connect to a WPA2 network?
[17:58] <dobey> mardy: whether the lib is static or not shouldn't "break" anything
[17:58] <ogra_> annerajb, http://paste.ubuntu.com/5939625/ you most likely need this kernel patch ... and use CONFIG_CMDLINE_EXTEND=y (with CONFIG_CMDLINE_FORCE and CONFIG_CMDLINE_FROM_BOOTLOADER unset)
[18:00] <sergiusens> plars: so we are similar :-)
[18:00] <w-flo> clouder_, use phablet-network-setup (GUI appears to be broken currently)
[18:01] <annerajb> ogra_, ok
[18:02] <plars> sergiusens: yep, I don't recall though, is that something that tedg said he is already aware of and should be fixed once upstart-app-launch lands?
[18:02] <ogra_> annerajb, CONFIG_CMDLINE_EXTEND would usually add your config to the front of the cmdline ... but that way you cant have console=tty1 at the end ... the patch flips that so the cmdline snipped from the kernel config gets appended instead of prepended
[18:03] <ogra_> it might need adjustment for your kernel :)
[18:03] <ogra_> (the patch that is)
[18:03] <annerajb> ok i applied the path
[18:03] <annerajb> patch*
[18:03] <ogra_> oh, it just applied ? no moaning ?
[18:03] <ogra_> nice
[18:03] <annerajb> i did it by hand lol
[18:03] <ogra_> ah
[18:04] <annerajb> ogra_, so i switch the console at the end to the start? http://pastebin.com/digGbhUr
[18:05] <thumperest> hi all, i installed ubuntu touch today, but i cannot get my sms messeges. is therer a known bug or something?
[18:05] <ogra_> annerajb, your commandline was totally fine ...
[18:05] <m1fs> ubuntu on samsung galaxy nexus i9250
[18:06] <ogra_> annerajb, the only important part is that console=tty1 is the last console= arg
[18:06] <thumperest> LG Nexus 4
[18:06] <annerajb> ogra_, ok i am going to build now.
[18:06] <ogra_> ok
[18:06] <ogra_> you switched from force to extend ?
[18:06] <annerajb> yes for is unset extend is set
[18:06] <annerajb> force is unset*
[18:07] <ogra_> ok
[18:07] <ogra_> then you should be able to boot ubuntu and still have the recovery mode (if the patch works :) )
[18:07] <m1fs> "ubuntu on samsung galaxy nexus i9250"
[18:08] <ogra_> m1fs, do you want to tell us something ?
[18:08] <sergiusens> plars: tedg just told me the syntax is $(pkg)_$(app)_$(ver)
[18:08] <ogra_> (speaking in while sentences helps sometimes)
[18:08] <ogra_> *whole
[18:09] <m1fs> ubuntu on samsung galaxy nexus i9250 how to ezy way.
[18:09] <annerajb> need to reflash with odin since I can't get into recovery lol
[18:09] <ogra_> m1fs, look at the devices wikipage, if it is not there you might have to do a port yourself
[18:09] <ogra_> !devices | m1fs
[18:10] <m1fs> thanks @ogra
[18:10] <ogra_> annerajb, heh, yeah ...
[18:11] <smoku> hi
[18:12] <smoku> I'm porting to Dell Streak and the generated image borks during boot on E/PrintK  (    1): <3>init: cannot find '/system/bin/app_process', disabling 'zygote'
[18:12] <smoku> no wonder.. there is no /system/bin/app_process
[18:13] <smoku> should it even try to start sygote service?
[18:14] <annerajb> isnt zygote a android service?
[18:14] <ogra_> smoku, nope
[18:14] <m1fs> https://wiki.ubuntu.com/Touch/Devices/toro is this for ? samsung galaxy nexus i9250
[18:15] <sergiusens> tedg: plars with the correct appid: http://paste.ubuntu.com/5989985/
[18:16] <m1fs> iff it is then no Install instructions ?
[18:16] <tedg> sergiusens, Yeah, I mentioned that to jdstrand yesterday.  It needs updating in apparmor-click
[18:16] <smoku> so, I should prepare custom init.rc?   I was under impression that I can use CyanogenMod device as-is
[18:17] <tedg> sergiusens, It's trying to execute qtchooser
[18:17] <annerajb> smoku, you cannot use cyanogen mod you have to flash a rootfs and initrd for your device
[18:17] <jdstrand> actually, it needs an update to apparmor-easyprof-ubuntu
[18:18] <annerajb> smoku, but if the device is supported in cyanogen mod is "theoretically easy" to get supported in ubuntu touch
[18:18] <jdstrand> lucky for us, I fixed it yesterday: https://launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/1.0.16
[18:18] <jdstrand> sergiusens, tedg: ^
[18:18] <sergiusens> jdstrand: oh, so /me just needs updating...
[18:19] <jdstrand> sergiusens: update and run 'sudo click hook remove apparmor && sudo click hook install apparmor'
[18:19] <smoku> annerajb, so this is what Porting guide mean in "As we're using CyanogenMod, we can easily take advantage of all the devices that are officially supported there."
[18:19] <annerajb> smoku, yes that if it works in cyanogenmod with some changes you can get ubuntu touch to work
[18:20] <sergiusens> jdstrand: ty!
[18:20] <smoku> ok. thanks.  I need to look inside supported device repo then :)
[18:20] <annerajb> smoku, http://forum.xda-developers.com/showthread.php?t=2173045
[18:20] <sergiusens> plars: ^^
[18:21] <smoku> annerajb, yup. seen that. but I'm on streak 5
[18:22] <smoku> annerajb, just got mislead by that sentence in Porting guide, so I started with CM device repo and got pussled by missing zygote
[18:23] <annerajb> smoku, btw if you are going to port it to streak 5 i suggest you take a look at the changes the guy that ported the other one did to get yours working
[18:23] <m-b-o> balloons: has it worked?
[18:23] <annerajb> usually is really easy to port to similar devices
[18:23] <smoku> annerajb, already cloning. thanks :)
[18:23] <balloons> m-b-o, http://91.189.93.70:8080/job/generic-mediumtests/359/
[18:25] <m-b-o> balloons: yes, already saw that.... they changed it once again, will change that assert
[18:25] <plars> sergiusens: still get zeitgeist error after running '/sbin/initctl start application APP_ID=com.ubuntu.dropping-letters_dropping-letters_0.1.2.2'
[18:25] <balloons> m-b-o, perfect :-) with that I'll turn on gated commits
[18:26] <balloons> fginther, can you enable gated commits for weather too? looks good
[18:26] <sergiusens> ogra_: zygote is an android service (we removed it though)
[18:26] <fginther> balloons, yep
[18:26] <m-b-o> balloons: this was the only missing test?
[18:26] <ogra_> sergiusens, i know :)
[18:27] <sergiusens> ogra_: ack, then I missread :-)
[18:27] <balloons> m-b-o, yes.. the only failure is what you see there
[18:27] <ogra_> yeah, wasnt me :)
[18:31] <sergiusens> plars: I get the app to launch but it launches below unity8
[18:32] <ogra_> its shy
[18:33] <m-b-o> balloons: I'VE updated the pending MP
[18:36] <mhall119> having only 1.2GB on / on my Nexus 4 is very limiting
[18:36] <mhall119> is there any way to get more?
[18:36] <mhall119> any *easy* way I mean
[18:37] <mhall119> trying to enable developer mode keeps using up all the space
[18:40] <balloons> m-b-o, http://91.189.93.70:8080/job/generic-mediumtests/363/
[18:40] <fginther> balloons, done
[18:41] <m-b-o> fginther: does this mean, the tests must all pass before merge?
[18:41] <fginther> m-b-o, yes
[18:41] <balloons> hehe :-)
[18:42] <m-b-o> ah, ok. First "needs-fixing" maill arrived :)
[18:43] <balloons> m-b-o, you can a clean build
[18:43] <balloons> *you got
[18:44] <m-b-o> balloons: cool :)
[18:49] <annerajb> ogra_, the bootline arguments are not there apparently it needs the force
[18:54] <ogra_> annerajb, well, more likely the patch doesnt work, but yeah
[18:56] <annerajb> the patch is to address the console for upstart right?
[18:56] <ogra_> the patch is to append to the botloader commandline instead of prepending
[18:56] <ogra_> when you use "EXTEND"
[18:57] <annerajb> ok but that should only affect upstart or will that also affect break?
[18:58] <ogra_> it doesnt matter where break is on the cmdline as long as it is there
[18:59] <annerajb> ok i wanna debug why it's not starting to hand it over to the rootfs later ill deal with upstart (once i actually get the rootfs mounted)
[19:05] <ogra_> i'm pretty sure it mounts and dies on upstart
[19:05] <ogra_> (and the break=bottom shoulld confirm that)
[19:08] <mfisch> sergiusens: how do I manually install a click package?
[19:08] <mfisch> sergiusens: click install wants the sdk installed
[19:09] <ogra_> there is an override switch you need to use
[19:09] <sergiusens> mfisch: click install --user=phablet --force-missing-framework package.click
[19:10] <ogra_> --force-missing-framework
[19:10] <ogra_> ah
[19:10] <ogra_> bah
[19:10] <ogra_> i'm slow
[19:10] <mfisch> this beats trying to install the SDK on the phone and filling the entire filesystem
[19:11] <mfisch> sergiusens: AFAIK that's not in any docs, can you add it to your blog?
[19:12] <sergiusens> mfisch: sure, you aer also supposed to be able to use pkcon but I haven't attempted, and I'm also waiting for the scope :-)
[19:12] <mfisch> sergiusens: there will be a special scope for click packages?
[19:13] <sergiusens> mfisch: yes, it will be seen in the app lens and you'll be bale to install apps from the store there
[19:14] <sergiusens> mfisch: the ubuntu-sdk-1310 thing is more like an API level thing in android (I wish to believe at least)
[19:14] <mfisch> ok
[19:14] <sergiusens> ogra_: I had the copy/paste handy (I can't seem to remember that switch)
[19:14] <mfisch> I tried installing it on the phone after the error ;)
[19:15] <sergiusens> mfisch: it's not finished yet either, this is a stop gap solution
[19:15] <ogra_> sergiusens, ah, i ran click install --help on the phone :)
[19:15] <mfisch> so I should see my app now or do I need to reboot?
[19:23] <mfisch> sergiusens: even after installing 2 packages "click list" returns no results
[19:23] <sergiusens> mfisch: click list --user=phablet or as the phablet user
[19:23] <mfisch> ah
[19:24] <mfisch> sergiusens: perfect, now should I expect to see them in the apps lens?
[19:25] <sergiusens> mfisch: it's not refreshed automatically yet.
[19:48] <Chocanto> mhall119: If you want to do a meeting, i'm here :)
[19:49] <Chocanto> or popey
[19:50] <thumperest> hi all :) i have Nexus 4 installed latest build and i have some questions. is anybody to help ?
[19:52] <thumperest> or bugs i think
[20:10] <houseofbean> thumperest:  I've got it installed on my Nexus 4.  But I've been doing the apt-get update & upgrade.  I haven't flashed in about a week.  Not sure if I'd be much help as I have questions too.
[20:12] <popey> thumperest: wassup?
[20:14] <houseofbean> Dropping letters is addictive!
[20:27] <houseofbean> From what I've read, I'm assuming the full way to update is to flash your device.  Lately, I've just been using apt-get update/upgrade.
[20:32] <jamesh3> Hello everyone - Ubuntu Edge campaign is about 39k off crowdfunding record - Canonical needs your help now http://igg.me/at/ubuntuedge/x/4040308
[20:34] <jdstrand> kalikiana: hey, I didn't get back to you. I think you have some questions regarding appliation paths and application confinement?
[20:34] <annerajb> ogra_, apparently i broke it and after 10 builds the forced cmdline dont work anymore :( now i dont get any of the datapart cmdline arguments
[20:35] <jdstrand> tedg: hey, jenkins complained about my merge request. is there something I need to do?
[20:36] <tedg> jdstrand, Fix your merge request :-)
[20:36] <tedg> Let me look.
[20:36] <jdstrand> tedg: the tests passed :)
[20:36] <jdstrand> this happened to me once before. I must not be doing something right
[20:36] <tedg> jdstrand, Just set the commit message: https://code.launchpad.net/~jdstrand/upstart-app-launch/prepare-env/+merge/180387/+edit-commit-message
[20:37] <tedg> jdstrand, That's the message that gets put into the debian/changelog
[20:37] <jdstrand> I thought I did that
[20:37] <jdstrand> ah, no I guess not
[20:37] <tedg> There's two things, the description and the commit message.
[20:37] <jdstrand> tedg: complete with [ Jamie Strandboge ] style?
[20:37] <tedg> The proposal page only has the commit message if you open the entry at the bottom.
[20:37] <tedg> jdstrand, No, the tool will do that.
[20:38] <jdstrand> tedg: should I use 78 char wide debian/changelog formatting?
[20:38] <tedg> jdstrand, Hmm, I always just write a sentence and let it wrap it for me.  I'm not sure how it processes all that.
[20:39] <tedg> cyphermox may know
[20:39] <jdstrand> I guess we'll see! :)
[20:42] <jdstrand> tedg: ok, we'll see how that goes. thanks :)
[20:43] <tedg> np
[20:43] <geek2076> Allo
[20:45] <geek2076> Hello
[20:46] <geek2076> I need help
[20:47] <geek2076> On nexus 4 ubuntu touch work good now
[20:47] <mfisch> sergiusens: I have no networking on the latest image. Is that a known issue?
[20:48] <geek2076> No
[20:48] <geek2076> For me it ok
[20:49] <geek2076> Whit n4 and nexus to
[20:50] <geek2076> You have what phone
[20:50] <mfisch> n4
[20:50] <mfisch> when I connect to wifi it just spins instead of prompting me for a password
[20:51] <geek2076> Ok i try 3 time
[20:51] <geek2076> And its ok
[20:51] <geek2076> N4
[20:52] <geek2076> I flash 2 zip and go
[20:53] <geek2076> I have the file again
[20:53] <geek2076> For n4
[20:55] <geek2076> I work a bit on the image and now wifi work
[20:56] <geek2076> For nexus 4 owner what the best rom
[20:57] <geek2076> Like 23000 on benchmark
[20:57] <geek2076> Have got 21000
[20:59] <geek2076> Who have a problème whit wifi on ubuntu touch
[20:59] <geek2076> On n4
[20:59] <popey> works here
[20:59] <geek2076> What
[21:00] <popey> what what?
[21:00] <geek2076> Work no
[21:00] <geek2076> Popey
[21:00] <popey> I'm running the latest image of ubuntu touch on my nexus 4, and wifi works
[21:00] <popey> what's the problem?
[21:00] <geek2076> Thanks
[21:01] <geek2076> You have a link
[21:01] <geek2076> Please
[21:02] <popey> https://wiki.ubuntu.com/Touch/Install
[21:02] <geek2076> Thanks
[21:03] <cyphermox> jdstrand: in the launchpad stuff commit message and all you can just write it as you want, it will get wrapped for you
[21:04] <cyphermox> it's in fact not really used so much in changelog either, what lands in changelog is usually the bug title if there is a bug linked to the merge request/branch
[21:13] <kalikiana> jdstrand: my quest(ion) is to sort out if we a) can have per-app XDG_ environment variables based on app id (and it wasn't clear who is working in that area) b) if we need to patch Qt5 instead if the former isn't viable - we need a solution that works on the desktop and doesn't require confinement-only api
[21:35] <balloons> fginther, can you have a look? I think when you added the ci checks for everything, it's not printing :-( https://code.launchpad.net/~mdspencer/ubuntu-filemanager-app/fix-autopilot-tests/+merge/180430
[21:38] <balloons> iBelieve, can you add the bit about not running the open file on non-desktop devices for now
[21:38] <iBelieve> balloons, what do you mean? just comment it out?
[21:39] <fginther> balloons, looking
[21:41] <jdstrand> kalikiana: a) per app XDG_ env vars based on app id - unfortunately no. we feel this will break on the converged device
[21:42] <jdstrand> kalikiana: b) sure
[21:42] <jdstrand> kalikiana: let me direct you to https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement#Launching_applications
[21:42] <jdstrand> kalikiana: are you looking at the bugs I filed regarding these?
[21:43] <jdstrand> kalikiana: cause I am fixing the /tmp/*.sci by setting TMPDIR
[21:43] <jdstrand> kalikiana: so you can skip that one
[21:44] <jdstrand> kalikiana: the /var/tmp/etilqs* is weird. I can't reproduce it but hopefully it will also honor TMPDIR
[21:45] <jdstrand> kalikiana: if not, then the library should be fixed for it (that is easily upstreamable)
[21:46] <jdstrand> kalikiana: I would strongly argue that bug #1197051 and bug #1197056 upstream is doing the wrong thing
[21:48] <kalikiana> jdstrand: the problem is that these bugs make perfect sense on the desktop - you expect to share caches/ data, not just qt but for example other webkit flavours/ ports do that by default
[21:48] <mfisch> popey: if wifi is working for you, don't upgrade
[21:48] <mfisch> ssweeny: unless this wifi failure is an image-update only issue
[21:48] <popey> mfisch: oh?
[21:48] <sergiusens> wifi input box seems to be broken with the new indicators
[21:49] <ssweeny> might it have to do with the new stacking in the indicator interface?
[21:49] <kalikiana> jdstrand: and yes, I am looking at these as well. it depends a bit on the preferred approach to fix it, so I'm not diving into patches just yet
[21:49] <mfisch> popey: yeah, we don't get a password prompt
[21:49] <jdstrand> kalikiana: I'll concede that on bug #1197056
[21:49] <mfisch> I'll do the old manual way, I think it's still in the wiki
[21:49] <sergiusens> mfisch: awe was going to followup with dednick
[21:49] <mfisch> sergiusens: cool
[21:49] <jdstrand> kalikiana: but that is not the case with bug #1197051
[21:50] <mfisch> ssweeny: you'll need to add /opt to the writable-paths to install stuff
[21:50] <ssweeny> mfisch, ack
[21:50] <jdstrand> kalikiana: eg: ~/.local/share/Qt\ Project/QtQmlViewer/QML/OfflineStorage/Databases/11474b32865dbdb4426621e50b908f3b.ini
[21:50] <jdstrand> kalikiana: that is not a reusable path
[21:51] <mfisch> ssweeny: what are the odds that chown works in the initrd?
[21:52] <jdstrand> well, maybe it is-- it might be an md5sum-- buit it is very odd
[21:52] <mfisch> ssweeny: probably it can't figure out the userids
[21:52] <ssweeny> mfisch, it might with numerical ids
[21:52] <ssweeny> mfisch, but the initrd probably won't know the names of any users
[21:52] <mfisch> right
[21:52] <jdstrand> kalikiana: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html references that other specifications dictate $XDG_DATA_DIRS/subdir/filename
[21:53] <jdstrand> kalikiana: sorry, $XDG_DATA_HOME/subdir/filename
[21:53] <kalikiana> jdstrand: it's due to qmlscene being "the same application" and it's fairly recent that it got api for qml to distinguish it as an "application"
[21:53] <jdstrand> which is what we want. subdir=APPNAME
[21:53] <jdstrand> kalikiana: anyway-- I'm not trying to be difficult, just expressing my point of view
[21:54] <jdstrand> kalikiana: ah, well, that sounds promising then
[21:54] <kalikiana> jdstrand: so the question here would be - if we find that qmlscene can be fixed, how/ where does it get the correct app name set?
[21:55] <jdstrand> kalikiana: yes-- that was actually waht I was ging to mention
[21:55] <kalikiana> something that works on the desktop especially
[21:55] <jdstrand> kalikiana: for click, we are using the click package name
[21:56] <awe> sergiusens, I emailed him...
[21:56] <jdstrand> "name": "com.ubuntu.developer.user.pkgname"
[21:56] <kalikiana> jdstrand: are developers expected to use the package name anywhere in their qml?
[21:57] <jdstrand> kalikiana: I noticed that MainView has the concept of "applicationName"
[21:57] <kalikiana> right
[21:57] <jdstrand> kalikiana: hehe, you type faster than I :)
[21:57] <kalikiana> which I think is pretty much the .desktop file I think
[21:57] <kalikiana> but I'm not sure that is the same as the package
[21:57] <fginther> balloons, I'm confused by the message being incorrect. I'll keep looking.
[21:57] <jdstrand> kalikiana: I think you are right
[21:57] <jdstrand> kalikiana: let's back up a step
[21:58] <jdstrand> there is this concept of APP_ID floating through click, application lifecycle and application confinement
[21:58] <jdstrand> the APP_ID is $pkgname_$appname_$version
[21:59] <jdstrand> kalikiana: for confinement, we use $pkgname from the APP_ID
[21:59] <jdstrand> kalikiana: so that you don't lose settings, etc when upgrading to a new version
[22:00] <jdstrand> kalikiana: we actually export two variables you could use, but I'm not sure that is the best cause it is not upstreamable
[22:00] <jdstrand> kalikiana: ie, APP_ID=com.ubuntu.developer.user.appname_appname_version
[22:00] <jdstrand> UBUNTU_APPLICATION_ISOLATION=1
[22:01] <jdstrand> kalikiana: so a short term solution would be to see if those two are set, and if they are, do $APP_ID.split('_')[0]
[22:01] <jdstrand> that won't break kde, etc
[22:02] <jdstrand> that is very Ubuntu specific though
[22:02] <jdstrand> if the $pkgname could be declared in the qml, like how applicationName is, then that could be used instead
[22:02] <kalikiana> jdstrand: would it be feasible to require that applicationName is equal to $pkgname so that it could be used to derive ~/.local/share/$pkgname
[22:03] <kalikiana> or possibly another variable with the same effect
[22:03] <jdstrand> kalikiana: from my perspective, sure. I just don't know how application_name is used in the sdk
[22:03] <jdstrand> sorry
[22:03] <jdstrand> applicationName
[22:03] <kalikiana> it's used to let Unity tell what app is the same and belongs to what .desktop
[22:04] <kalikiana> that's why the basename must match
[22:04] <jdstrand> kalikiana: but if upstream had a variable that could be set, such that everything works (webkit notwithstanding, we can talk about that in a moment):
[22:04] <jdstrand> someName: com.ubuntu.developer.username.appname
[22:05] <jdstrand> such that the paths all end up being:
[22:05] <jdstrand> $XDG_CACHE_HOME/$someName
[22:05] <jdstrand> $XDG_DATA_HOME/$someName
[22:05] <jdstrand> $XDG_CONFIG_HOME/$someName
[22:05] <jdstrand> $XDG_RUNTIME_DIR/$someName
[22:05] <jdstrand> then we would be set
[22:06] <jdstrand> kalikiana: I think something like that is conceivably upstreamable
[22:06] <jdstrand> because it isn't ubuntu-specific
[22:06] <jdstrand> heck, if that someName variable isn't defined, it can fallback to current behavior
[22:08] <jdstrand> that's my thinking on it
[22:08] <kalikiana> jdstrand: there is https://qt-project.org/doc/qt-5.0/qtcore/qcoreapplication.html#applicationName-prop if that is set it affects the folder name used below ~ /.local/share/
[22:08] <jdstrand> ohh
[22:08] <kalikiana> I need to verify if we can set that in qml, I don't think it is exposed
[22:08] <kalikiana> but we could find a way to override it
[22:09] <kalikiana> leaving only the cases where desktop might expect a different behavior eg. sharing caches
[22:09] <jdstrand> so something like that would work fine from my perspective
[22:10] <jdstrand> the sdk could default to setting it because it already knows how to generate a manifest
[22:10] <jdstrand> so it is in a position to pre-fill it
[22:11] <jdstrand> kalikiana: did you want to talk about the non-qtwebkit paths more, or shall we move on?
[22:11] <kalikiana> ideally we'll have a way to verify if it is set correctly when creating the package… since it should be set in code
[22:11] <ryukafalz> mfisch: I'm having the same WiFi issue on my Nexus 7 with the latest image
[22:11] <jdstrand> kalikiana: yeah. that should be doable if it is in the mainView
[22:13] <jdstrand> kalikiana: are you subscribed to ubuntu-appstore-developers
[22:13] <kalikiana> jdstrand: I think I'm fine with this plan then; by non-qtwebkit you mean like /dev/shm/? I was planning to focus on app data & cache first, the other kinds of files seem more like bugs to fix in qt
[22:13] <kalikiana> yes I am
[22:13] <jdstrand> kalikiana: a very apropos discussion is happening there :)
[22:14] <jdstrand> kalikiana: see "Summary: Planning going live" from alecu
[22:15] <kalikiana> looking
[22:15] <jdstrand> kalikiana: so, let me get the bug list
[22:15] <jdstrand> kalikiana: bug #1197047 I am fixing by setting TMPDIR
[22:16] <Jrlocoboy> I have a question: ANyone else expiriencing wifi problems on Saucy Ubuntu touch
[22:16] <jdstrand> kalikiana: bug #1197049 I can't reproduce. it might be fixed by setting TMPDIR. it is likely an easy upstreamable fix to honor TMPDIR if not
[22:17] <jdstrand> kalikiana: bug #1197051 - that's the one we've been talking about
[22:17] <w-flo> Jrlocoboy, like not being able to enter a WPA passkey?
[22:17] <Jrlocoboy> YEah
[22:18] <jdstrand> kalikiana: that leaves bug #1197060 and bug #1197056
[22:18] <w-flo> Jrlocoboy, quite a few people (including me) have that issue. It used to work last week. A fix is probably being worked on :)
[22:18] <Jrlocoboy> k thanks. I tought i installed Ubuntu wrong
[22:19] <Jrlocoboy> thought*
[22:19] <kalikiana> jdstrand: wrt mailing list, yes that is what I was thinking of. I think the plan is to have uploads initiated by qtcreator so in the best case we will have one place (QtC) to double-check the id in all places
[22:19] <w-flo> Jrlocoboy, you can use phablet-network-setup to copy the wifi config from your desktop/lapto
[22:19] <kalikiana> the main hindrance this is just time
[22:19] <kalikiana> to implement it
[22:19] <jdstrand> kalikiana: maybe the /dev/shm access is just a bug like you say. I think the way to handle the QtWebkit shared databases is to look at UBUNTU_APPLICATION_ISOLATION and parse APP_ID and distro patch it
[22:19] <Jrlocoboy> can you explain how to. Im sort of a noob
[22:20] <w-flo> sure, just open a terminal in ubuntu and type "phablet-network-setup", it will ask for your password. make sure your device is plugged into USB
[22:20] <Jrlocoboy> k thanks
[22:20] <jdstrand> kalikiana: the reason why I say disto patch there is because sdk apps will be using the chromium content api backend (Oxide) instead of QtWebkit
[22:21] <jdstrand> kalikiana: we want to have that in place for 14.04, so there is no point fighting upstream or being clever. Oxide will support different profile that put the cache in different places
[22:21] <jdstrand> kalikiana: chrisccoulson/ChrisCoulson has the details
[22:23] <jdstrand> kalikiana: wrt QtC checks-- sure. people can get it right manually for a bit. so long as we have decent docs, that should be sufficient
[22:23] <jdstrand> kalikiana: what do you think about my suggestion on qtwebkit?
[22:26] <kalikiana> jdstrand: I think we can propose a patch upstream and distro-patch in any event
[22:26] <jdstrand> kalikiana: well, it would help everyone-- I'll leave it up to you
[22:27] <jdstrand> kalikiana: (meaning, fixing qtwebkit to do the same as the others could help everyone, but oxide is coming if you want the distro-patch shortcut :)
[22:27] <jdstrand> kalikiana: so, sorry I didn't get back to you sooner. do you feel unblocked now?
[22:28] <kalikiana> hmm you mean oxide would do what we need regardless of qtwebkit upstream?
[22:28] <kalikiana> I thought it would be based on the same API
[22:28] <kalikiana> but I haven't heard about it much for a while so I don't know all of it
[22:28] <jdstrand> kalikiana: yes. oxide will be alongside qtwebkit. so, for example, kde would just keep using qtwebkit
[22:29] <jdstrand> kalikiana: but the sdk and canonical supported apps would use oxide
[22:29] <kalikiana> so applications opt-in to oxide api?
[22:29] <jdstrand> depends how you define opt-in :)
[22:29] <jdstrand> but yeah. pick one or the other
[22:29] <jdstrand> chrisccoulson has a preliminary webview working via qml
[22:30] <jdstrand> kalikiana: don't feel bad about not knowing about it-- quite a bit has happened there but it has had to be a one man job to get it to the point where others can jump in
[22:31] <jdstrand> kalikiana: we are there now and I've got a todo to round up people to help out chrisccoulson :)
[22:31] <chrisccoulson> :)
[22:32] <kalikiana> I think I'd still like to see qtwebkit fixed then, we want to be nice with upstream api
[22:32] <jdstrand> kalikiana: we might need some support from qml to make oxide put the files in the right place. chrisccoulson could say more-- I imagine we would want to support both shared and isolated scenarios
[22:32] <jdstrand> kalikiana: sure, again, I'll leave that up to you :)
[22:32] <jdstrand> kalikiana: are you unblocked now?
[22:33] <kalikiana> jdstrand: absolutely, yes. it was worth replying after midnight :-D
[22:33] <kalikiana> thanks a lot
[22:33] <chrisccoulson> sorry, i think i'm lacking context (i missed the start of the conversation)
[22:33] <jdstrand> kalikiana: oh gosh, I didn't know it was so lot
[22:33]  * jdstrand hugs kalikiana 
[22:33] <jdstrand> kalikiana: I'm glad I could help and thank *you* for your work on this :)
[22:34] <kalikiana> jdstrand: no worries. I am keen to getting much closer to solving this. it's one of the things that people say now and then and it just needs a little persistence to get done
[22:34] <kalikiana> partly in finding the right person to talk to
[22:35] <kalikiana> chrisccoulson: your name came up in context of oxide - I was a bit behind in the latest and greatest developments there ;-)
[22:35] <chrisccoulson> ah :)
[22:36] <jdstrand> kalikiana: it will be huge for our application confinement to have this fixed. right now apps can tamper with each other cause there isn't a way to separate their files in policy
[22:36] <chrisccoulson> oh, we're talking about where webkit stores its files?
[22:36] <kalikiana> jdstrand: yeah. in context of the app contest it also came up "where do I put u1db files" and such questions
[22:36] <jdstrand> kalikiana: I marked bug #1197047 won;t fix for ubuntu-ui-toolkit
[22:36]  * jdstrand nods
[22:37] <jdstrand> I am fixing that via TMPDIR
[22:37] <kalikiana> great
[22:37] <jdstrand> I'll add a comment to 1197049
[22:37] <jdstrand> (/var/tmp/etilqs_* )
[22:38] <jdstrand> I'[d like to know what is creating that so I can test TMPDIR with it :)
[22:38] <kalikiana> I think it is used by webkit2 communication between processes, you should probably see it using the browser app
[22:39] <kalikiana> just open some stuff
[22:39] <jdstrand> bzoltan said it came from src/3rdparty/sqlite/sqlite3.c I see
[22:39] <jdstrand> I'll check the source
[22:39] <jdstrand> (qtbase-opensource-src)
[22:40] <kalikiana> my mistake, I confused it with another bug
[22:41] <kalikiana> jdstrand: so as it's kind of late here: feel free to assign to me if we have to fix/ patch qt to use the right path
[22:41] <kalikiana> and I'll look into it soonish
[22:44] <jdstrand> kalikiana: awesome, thanks! sleep well :)
[23:05] <elkng> what is "Ubuntu Linux phone" ?
[23:06] <elkng> is its architecture similar to android or its real linux ? with real tools instead of busybox ?
[23:08] <elkng> what video player will be preinstalled on it on its release ? mplayer ?
[23:49] <jono> awe, hey
[23:50] <jono> looks like connecting to a wireless networking might be broken on mako
[23:50] <awe> hey jono, wha's up?
[23:50] <awe> nahh, worse
[23:50] <awe> it be broken on all
[23:50] <jono> oh?
[23:50] <awe> ;(
[23:50] <jono> bummer
[23:50] <awe> yea
[23:50] <jono> ok, nm
[23:50] <jono> good to know it isn't just me :-)
[23:50] <awe> we discussed earlier during our network/telephony meeting
[23:50] <jono> this is not covered by our test infrastructure?
[23:50] <awe> ted pointed me to dednick
[23:51] <awe> but he's offline, so I emailed him about it
[23:51] <jono> cool
[23:51] <awe> AFAIK, no it's not covered by our test infrastructure
[23:51] <jono> gotcha
[23:51] <awe> I have plans to discuss system testing with sergiusens on Mon
[23:51] <jono> cool
[23:51] <elkng> anyone here ?
[23:52] <awe> primarily to talk about telephony, but we may also discuss wifi as well
[23:52] <cjohnston> jono: which build?
[23:53] <awe> this morning
[23:53] <awe> the password/passphrase dialog is busted
[23:53] <jono> cjohnston, today
[23:53] <jono> elkng, I think I am
[23:54] <cjohnston> awe: ahh... so if you supply a network file it would work?
[23:54] <sergiusens> awe: make that Tuesday, I just recall I have a national holiday on Monday
[23:54] <awe> cjohnston, yes
[23:54] <awe> sergiusens, ack
[23:54] <cjohnston> awe: that explains why all the tests worked
[23:54] <awe> sergiusens, can you schedule a meeting?
[23:55] <cjohnston> I guess sergiusens didn't like that. heh
[23:55] <awe> cjohnston, we've been waiting on the new networking indicator for awhile now.  I'm sure there was a conscious decision not to invest in auto-testing the old indicator UI
[23:55] <awe> ;)
[23:56] <cjohnston> :-)
[23:56] <cjohnston> awe: I'd be happy if I could get 3g working on mine
[23:56] <cjohnston> (or whatever the slowest internet is)
[23:57] <awe> cjohnston, what device?
[23:57] <cjohnston> mako
[23:57] <awe> are you running the latest image?
[23:57] <awe> there are know problems with data provisioning, and there's also a known race between NM and ofono that's being worked on
[23:57] <awe> try restarting NM, and see if that does the trick
[23:58] <awe> if not, then the next thing to check is whether or not you have a valid data context
[23:58] <cjohnston> 20130814.1
[23:58] <awe> you can check by running the ofono script 'list-contexts' ( in /usr/share/ofono/scripts )
[23:58] <cjohnston> I saw yesterday I think about the bug being filed about the race but a restart wasn't working..
[23:58] <cjohnston> lemme see what happens with those