[02:19] <rekado> Tried it again and it just worked this time... oh well.
[03:59] <lotuspsychje> should i buy the google nexus7 or the asus nexus 7 2013 for ubuntu touch?
[07:07] <robert[con]> anyone using Touch on the Nexus 7 (2013)
[07:07] <robert[con]> ?
[07:08] <zsombi> cwayne: hey, I've commented on the bug, seems we have some autopilot issues there. However, the MainViewStyle is also broken in a ense that the artwork is not found, and there are some components referenced that are not found. You have a binding which is not necessary at all.
[07:18] <infinity> didrocks: I thought there was some conclusion last cycle that the spreadsheet needed to be phased out.  Now it's part of infrastructure and needs firewall holes and automation?
[07:18] <infinity> Erm, ECHAN.
[07:19] <didrocks> infinity: the spreadsheet as it was needed to be phased out (it was all manual)
[07:19] <didrocks> infinity: then, I was asked (with a few days credit to build everything) to do CI Train alone
[07:19] <infinity> didrocks: Driving our infrastructure from gdocs is not sane.
[07:20] <didrocks> agreed, and that's not what will happen once the CI team will build the Airline
[07:20] <didrocks> meanwhile, we took the cheapest decision to have sso integration, ui driving and automated refresh
[07:32] <dholbach> good morning
[08:56] <JamesTait> Good morning all; happy Monday, and happy Bunsen Burner Day! :-D
[09:19] <didrocks> pitti: hey! It seems we can't get any crash file on the phone anymore
[09:19] <didrocks> pitti: that's maybe due to new lxc/apparmor, the apport logs are: http://paste.ubuntu.com/7183953/
[09:20] <didrocks> pitti: I guess, this is a consequence of: http://paste.ubuntu.com/7183958/
[09:26] <dholbach> JamesTait, yeehaw!
[09:31] <pitti> didrocks: the crash was fixed in apport recently, I can upload the fix todayh
[09:31] <didrocks> pitti: do you know what triggered it into saturday's image?
[09:31] <didrocks> pitti: as we didn't get it and apport was working before
[09:32] <pitti> dholbach: not exactly; supposedly some new apparmor restrictions?
[09:32] <didrocks> (but yeah, getting the fix ASAP would be nice, we don't have any image view on the numerous crashers we have for 3 days)
[09:32] <dholbach> pitti, eh?
[09:32] <pitti> dholbach: sorry, I meant didrocks
[09:32] <didrocks> pitti: I guess so, I'll ask jdstrand to add that to his testsuite then
[09:32] <dholbach> ah, yes :)
[09:32] <pitti> didrocks: bug 1296026 FTR
[09:33] <didrocks> pitti: great! do you think you can upload it soon so that we rekick an image and see what current crashers we have?
[09:33] <pitti> didrocks: yes, I can; I didn't last week due to the freeze and forgot on Friday (too many meetings and couldn't type well, etc.)
[09:33] <didrocks> pitti: no worry, thanks a lot! :)
[09:38] <didrocks> plars: FYI ^ (no need to bisect I guess)
[09:42] <zsombi> didrocks: bonjour :)
[09:42] <zsombi> didrocks: are the click-app AP tests working?
[09:42] <didrocks> zsombi: hey! yeah, nothing to signal in that front, why?
[09:43] <zsombi> didrocks: we are trying to test UITK PPA for calendar-app, and we are getting crash for the phablet-click-test-setup
[09:44] <didrocks> zsombi: I guess Mirv is currently running them manually, and I saw him discussing about parameters, maybe he can help you? ^
[09:44] <didrocks> zsombi: but to be clear: on the infra, it's working
[09:45] <zsombi> didrocks: ok, thx!
[09:45] <didrocks> yw ;)
[09:45] <Mirv> zsombi: pastebin?
[09:46] <zsombi> Mirv: pastebin what? error?
[09:47] <Mirv> zsombi: there might be something going on, but you could edit /usr/bin/phablet-click-test-setup lines 65-66 and make it like at the top of: http://pastebin.ubuntu.com/7184049/ - as you don't need unity8/uitk tests downloaded for click testing
[09:47] <zsombi> Mirv: http://pastebin.ubuntu.com/7183954/
[09:47] <Mirv> zsombi: well yes if you need help
[09:47] <Mirv> zsombi: oh, that's indeed a known problem when you're testing UITK from landing PPA. in that case you really need to what I pasted to not have the click test setup try download uitk itself
[09:48] <Mirv> I don't actually even know why it tries to do that, since both unity8 and UITK autopilot tests come from .deb packages
[09:49] <Mirv> zsombi: after changing those lines it should work
[09:50] <popey> Mirv: i think it does it because the phone is RO
[09:50] <popey> the idea is you can run phablet-test-run without making your phone RW
[09:51] <Mirv> popey: oh, right, makes sense. it just doesn't understand it'd need to get the tests from a PPA and fails since the version being tested is not in archives.
[10:09] <davmor2> Morning all
[10:11] <lotuspsychje> should i buy asus nexus7 or google nexus 7 2013 to run ubuntu touch on?
[10:13] <popey> lotuspsychje: the nexus 7 2012 is no longer supported, but the nexus 7 2013 is
[10:14] <lotuspsychje> popey: so that would be the google nexus 7 2013 i need to buy right?
[10:15] <popey> there's two, the nexus 7 2012 with a lower resolution screen, and the newer nexus 7 2013 with the higher resolution screen, the 2013 is the one we support
[10:15] <lotuspsychje> http://www.tabletcenter.be/product/359870/category-206965-nexus-7/nexus-7-32gb-2013.html
[10:15] <lotuspsychje> this one ok?
[10:16] <popey> thats the nexus 7 2013
[10:16] <lotuspsychje> popey: ok great tnx for info mate
[10:50] <zyga> hey, quick question, I'm in progress of flashing the devel channel onto a flo device, any ideas on how long it takes, ubuntu-device-flash has exited about 10 minutes ago, I see what looks like the ubuntu boot loader ot the screen (volume keys are responsive) and no progress, I can adb in and top shows no process consuming significant amount of CPU time
[10:50] <zyga> is that expected? I read https://wiki.ubuntu.com/Touch/Install but it dones't say how long the process takes
[10:51] <zyga> or should one eactually select something form the boot loader at the end
[11:23] <zyga> anyone?
[11:25] <popey> zyga: what command did you use to flash it?
[11:26] <popey> zyga: and what was it running before you ran the command?
[11:26] <zyga> popey: ubuntu-device-flash --channel=devel --bootstrap
[11:26] <zyga> popey: it was running stock android that it came with (just freshly out of the box)
[11:26] <zyga> popey: it was in the unlocked bootloader
[11:27] <zyga> popey: this is the log from the flash process: http://paste.ubuntu.com/7184405/
[11:27] <popey> whats on screen now? Ubuntu logo?
[11:27] <zyga> popey: should I select something from the menu on the screen of the device now?
[11:27] <popey> there's a menu?
[11:27] <zyga> popey: the boot men, reboot system now, install zip, etc...
[11:27] <zyga> popey: yes
[11:28] <popey> hmm, odd.
[11:28] <zyga> I can navigate with the volume keys
[11:28] <popey> I'd be inclined to try a reboot first
[11:28] <zyga> popey: I did, once, it then goes to be stuck displaying the google logo
[11:28] <zyga> popey: I can try again
[11:29] <popey> when its displaying the google logo, leave it
[11:29] <popey> it takes a while
[11:29] <zyga> popey: the menu says, 'recovery v6.0.4.6' FYI
[11:29] <zyga> ok
[11:29] <zyga> rebooting
[11:29] <popey> you may need to re-flash if you rebooted while it was doing its stuff
[11:29] <zyga> popey: I can adb shell immediately
[11:29] <zyga> popey: and this is 'ps'
[11:30] <zyga> http://paste.ubuntu.com/7184412/
[11:30] <zyga> popey: it looks suspicuious
[11:30] <zyga>   223 0         1548 S    {adbd} /bin/sh /scripts/panic/adbd
[11:30] <popey> I'd re-run the flash and leave it alone
[11:30] <zyga> specifically this, it does nothing more than that
[11:30] <zyga> popey: I did, this is the third run now
[11:30] <popey> and leave it
[11:30] <zyga> popey: I cannot find any images on the /media partition
[11:50] <cwayne_> is devel-proposed borked for anyone else
[11:59] <ogra_> cwayne_, borked ?
[12:00] <zyga> ogra_: hey, could you have a look at the backlog and tell me if the flash instructions are borked or is the image/tool borked?
[12:01] <ogra_> zyga, i flashed multiple times today, no issues here with the same command
[12:01] <cwayne_> ogra_, stuck at google log
[12:01] <cwayne_> logo*
[12:01] <ogra_> bcwthats not helpful ... there are tons of conditions where it can be "stuck at google logo" :)
[12:01] <zyga> ogra_: ok, trying again
[12:01] <ogra_> do you have adb ?
[12:02] <zyga> ogra_: if it fails, can I poke you for some help? I can adb in and do anything you may need me to
[12:02] <cwayne_> ogra_, nope
[12:02] <ogra_> zyga, so what does the prompt show in adb ?
[12:03] <zyga> ogra_: I'm flashing it now but before I was stuck on the 'ubuntu recovery bootloader' screen and on the device I had something process with 'panic adb' in the name, probably because stuff failed and adb popped up as a last resort
[12:03] <zyga> ogra_: 13:30 < zyga>   223 0         1548 S    {adbd} /bin/sh /scripts/panic/adbd
[12:04] <zyga> ogra_: I wiped my .cache/ubuntuimages and am getting the data again, just in case
[12:04] <zyga> ogra_: this is on flo, btw
[12:04] <ogra_> if it panics in the initrd it could not find a root disk
[12:04] <ogra_> oh., i havent tried flo todsay
[12:04] <zyga> ogra_: :)
[12:04]  * zyga would love if you could
[12:04] <ogra_> check if your disk is full
[12:04] <zyga> ogra_: the device is fresh out of the box
[12:05] <zyga> ogra_: just got it a few hours ago
[12:05] <ogra_> (there are a bunch of logging bugs that make the kern.log grow gigantically)
[12:05] <zyga> ok
[12:05] <zyga> ogra_: first thing after I'm out of adb
[12:05] <zyga> er
[12:05] <zyga> fastboot
[12:05] <ogra_> zyga, and did it ever run ubuntu before?
[12:05] <zyga> ogra_: nope
[12:05] <ogra_> you know you need to boot once into android completely ?
[12:05] <zyga> ogra_: I didd
[12:05]  * ogra_ is sure the install page says so 
[12:05] <ogra_> hmm
[12:06] <zyga> ogra_: got to the home screen and started the process from there
[12:06] <ogra_> ok, that should be fine ...
[12:06] <zyga> ogra_: ok, flashing now
[12:06] <zyga> ogra_: this is what I have so far, looks normal: http://paste.ubuntu.com/7184505/
[12:07] <zyga> ogra_: offtopic, is it possible to fix adb shell to return the process exit code? :) (there's an open bug about that on google and untouched for a few long years)
[12:08] <ogra_> you mean to the host PC ?
[12:08] <zyga> ogra_: I see this now http://paste.ubuntu.com/7184511/
[12:08] <zyga> ogra_: adb shell false; echo $?
[12:08] <zyga> ogra_: I mean the exit code is useless
[12:08] <zyga> ogra_: the scren has spinning ubuntu logo
[12:08] <ogra_> zyga, very tricky, adb does not sccess the device itself, there is a proxy
[12:08] <sergiusens> zyga: ogra_fwiw; after unlocking, boot once into android before flashing
[12:09] <zyga> sergiusens: hey, glad to see you
[12:09] <zyga> sergiusens: I have goodies for you later
[12:09] <ogra_> sergiusens, yes, he apprently did
[12:09] <zyga> sergiusens: I did boot once, all the way to home screen
[12:09] <ogra_> thats why i asked :)
[12:10] <sergiusens> sure, I'm eavesdropping and haven't read through the whole cycle
[12:10] <zyga> ogra_: back to 'recovery v6.0.4.6'
[12:10] <sergiusens> zyga: sounds good :-)
[12:10] <ogra_> zyga, thats odd, it should boot into normal mode after uncompressing (teh dancing logo)
[12:11] <zyga> so what now?
[12:11] <ogra_> sergiusens, any idea ?
[12:11] <ogra_> thats a brandnew flo
[12:13] <sergiusens> ogra_: zyga check the logs in /cache/recovery/
[12:14] <zyga> checking
[12:14] <zyga> http://paste.ubuntu.com/7184534/
[12:14] <zyga> that /cache/recovery/log btw
[12:15] <zyga> (before killing android I did enable developer mode)
[12:15] <zyga> (I hope that is booting enough)
[12:16] <zyga> if you need any of the other log files then please tell me
[12:16] <ogra_> you need to enable dev mode and unlock the bootloader ... then boot once into android and you should be fine
[12:16] <zyga> ogra_: I did all of that
[12:17] <ogra_> right
[12:17] <zyga> ogra_: including the bootloader unlock
[12:17] <ogra_> there seems to be a stale autodeploy.zip
[12:18] <ogra_> I:using /data/media for /sdcard/autodeploy.zip.
[12:18] <ogra_> W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (Invalid argument)
[12:19] <zyga> ogra_: anything actionable for me?
[12:20] <ogra_> try removing it in recovery mode ... but i'd liek to hear what sergiusens thinks ... he is more familiar with the recovery logs
[12:20] <zyga> ogra_: remove what? autodeploy.zip? I cannot see it from adb shell
[12:20] <ogra_> under sdcard ?
[12:20] <zyga> ogra_: /sdcard is empty
[12:20] <ogra_> ok
[12:20] <ogra_> then thats moot :P
[12:21] <zyga> it's a symlink to /data/media btw
[12:24] <janimo> stgraber, ogra_ are the any known issues with using container overrides? I could place files in the rootfs using them, but not overwrite init.rc, I had the phone (not a nexus) lock up on boot if I tried that
[12:24] <ogra_> janimo, hmm, works for me usually
[12:26] <janimo> ogra_, ok thanks. Another file I tried overwriting in system/etc, while it did not get there on the rortfs at least that did not block the boot
[12:26] <ogra_> janimo, ah !
[12:26] <ogra_> janimo, you didnt say /system ;)
[12:27] <janimo> ogra_, well both init.rc which is in root
[12:27] <ogra_> thats indeed impossible without hacking up the mount code in initrd
[12:27] <janimo> and one under system/
[12:27] <zyga> sergiusens: can you help me out with this, is there anything I should/could do or should I ask you some other day?
[12:27] <ogra_> system is mounted readonly from the initrd
[12:27] <janimo> ogra_, init.rc was weird even if I tried replacing using the same copy of init.rc it would hang on boot
[12:27] <janimo> hence my asking whether there are known gotchas specific to touch
[12:27] <ogra_> thats indeed weird, were the permissions correct ?
[12:28] <ogra_> (for the file you copied in place)
[12:28] <sergiusens> ogra_: zyga no need for dev mode to flash
[12:28] <ogra_> sergiusens, oh, indeed, we should remove that from the instructions i guess
[12:28] <janimo> ogra_, +x on AFAIK, yes. I will try again though
[12:28] <sergiusens> ogra_: zyga that autodeploy zip is just a warning; nothing else; rsalveti made me keep it for his debugging; it's obsolete for anyone else ;-)
[12:29] <ogra_> janimo, yeah, +x they should be
[12:29] <ogra_> sergiusens, well, any idea why zyga cant boot then ?
[12:29] <sergiusens> zyga: this is what I'd do: oem unlock; boot android; reboot to bootloader; ubuntu-devce-flash --channel devel --bootstrap; wait
[12:30] <zyga> sergiusens: that's exactly what I did 20 minutes ago, arriving here
[12:30] <sergiusens> zyga: from your logs it seemed it bootstrapped fine though
[12:30] <zyga> sergiusens: any other log I can pull out for you?
[12:30] <sergiusens> lines 321 to 334 from the first pastebin
[12:31] <sergiusens> zyga: hmmm, only thing I can think of is flashing stock android before
[12:31] <sergiusens> zyga: might be some partition label mess; ogra_back to you :-P
[12:31] <zyga> sergiusens: ok, let my do that now
[12:33] <ogra_> stgraber, around ?
[12:33] <zyga> thanks, I'll stay in touch, ping you back when android is up again
[12:38] <zyga> quick sanity check: https://developers.google.com/android/nexus/images#razor <= that's flo?
[12:38] <zyga> razor is nexus 2013?
[12:38] <zyga> nexus 7 2013
[12:39] <zyga> sergiusens: ^^
[12:39] <sergiusens> zyga: yes
[12:39] <zyga> thanks
[12:39] <zyga> flashing
[12:39] <sergiusens> zyga: os build vs hw
[12:39] <zyga> ok, android seems to work
[12:39] <zyga> sergiusens: ah, I see
[12:52] <zyga> sergiusens: ok, android restored
[12:52] <zyga> sergiusens: I guess trying to flash ubuntu again won't do anything new
[12:52] <zyga> sergiusens: do you want me to poke around the system that I'm running now for clues?
[12:52] <zyga> sergiusens: runnin android 4.4.2 now
[12:53] <sergiusens> zyga: I was expecting you to flash ubuntu now ;-)
[12:53] <zyga> sergiusens: wait, you asked me to restore android before, didn't you?\
[12:53] <sergiusens> zyga: yeah, stock :) and then ubuntu
[12:53] <zyga> sergiusens: ok, doing ubuntu again
[12:54] <zyga> sergiusens: do I need the PPA on trusty?
[12:54] <zyga> sergiusens: that's one of the steps I didn't do
[12:54] <sergiusens> nope
[12:56] <ogra_> rsalveti, stgraber, i would like to drop the unpacking of the android initrd from lxc-android-config and instead merge it into the gzipping the initrd already does ... http://paste.ubuntu.com/7184677/ ... what do you guys think ?
[12:57] <zyga> sergiusens: hmm, it doens't turn back on
[12:57] <ogra_> (saves us one gzip run during boot)
[12:58] <zyga> sergiusens: it seems to be dead
[12:58] <zyga> sergiusens: I just powered it off from android
[12:58] <zyga> sergiusens: and now it's gone
[12:58] <sergiusens> zyga: no juice?
[12:58] <zyga> sergiusens: ah, it's on again :|
[12:59] <zyga> sergiusens: no, it was charged
[12:59] <zyga> sergiusens: I don't know what happened, I got scared for a second
[12:59] <zyga> sergiusens: I thought I wiped the bootloader somehow and that reboots weren't rebooting enough
[12:59] <zyga> ok, it is working
[12:59] <zyga> back to boot loader
[12:59] <zyga> and flashing again
[13:00] <zyga> sergiusens: is secure boot a problem?
[13:00] <mterry> ogra_, when you get a chance, https://code.launchpad.net/~mterry/ubuntu-touch-session/move-lightdm/+merge/211445 will help OEM customization of boot by letting them override lightdm config files with /custom ones
[13:00] <zyga> sergiusens: or modemmanager? (poking at all the serial lines)
[13:02] <zyga> sergiusens: ok, it's unpacking the tarball on the device now
[13:03] <zyga> sergiusens: ok, it's making SWAP,
[13:03] <zyga> sergiusens: and rebooted
[13:03] <zyga> sergiusens: and....
[13:04] <zyga> sergiusens: it seems to work :D
[13:04] <zyga> sergiusens: I wonder what the problem was
[13:04] <zyga> sergiusens: adb shell looks much better than before
[13:05] <zyga> sergiusens: click installs stuff
[13:05] <zyga> ahhh
[13:05] <zyga> the beauty :)
[13:05] <zyga> sergiusens: it booted ok
[13:06] <ogra_> :)
[13:07] <cwayne_> stgraber, ping
[13:08] <ogra_> mterry, looks fine (as long as it works) ... i assume it needs changes to writable-paths too if the customization teams wants to put stuff into that dir ?
[13:08]  * cwayne_ perks up
[13:11] <mterry> ogra_, I feel like the customization team is already on top of that?  They've been planning to use /custom for all sorts of stuff for a while, right cwayne?
[13:12] <ogra_> i wouldnt know why they need to modify the greeter startup though
[13:12] <ogra_> i dont think we have anything writable in there yet
[13:12] <cwayne_> mterry, yeah, we're allowed to write there, but once the phone's booted its r/o
[13:13] <cwayne_> wait i dont see anything in that MP about /custom..
[13:14] <mterry> cwayne_, right.  But what it does is move a file to a directory that is read before /custom is.  So that you can actually override its contents with your own file if you want
[13:15] <mterry> ogra_, well, once we have a boot animation going, the lightdm config may be a convenient place to override that.  Or whatever.  I don't want to pre-judge what lightdm changes are going to be needed
[13:15] <ogra_> ah, that makes more sense :)
[13:19] <cwayne_> fginther, ping
[13:21] <fginther> cwayne_, pong
[13:23] <cwayne_> fginther, hm sorry, never mind :)
[13:26] <fginther> cwayne_, just for future reference, please try to ping the ci vanguard in #ubuntu-ci-eng for ci requests or questions
[13:30] <dpm> hi, does anyone know how to put a N7 in landscape mode for testing purposes? I think there is a device-specific flag somewhere, but I'm not sure where it is
[13:32] <popey> dpm: /etc/ubuntu-touch-session.d/
[13:32] <popey> but I dont think it works..
[13:33] <dpm> popey, so assuming it'd work, what would I need to change in that dir?
[13:35] <popey> dpm: the one for the device, in your case, flo.conf
[13:35] <popey> but it already says landscape, which makes me think it doesn't work
[13:36] <dpm> ah, ok, thanks popey
[13:36] <ogra_> right
[13:36] <ogra_> it needs corresponding unity8 changes we dont have
[13:38] <cwayne_> sergiusens, hey, any idea why my custom tarball isn't being applied?
[13:39] <sergiusens> cwayne is this a new problem?
[13:39] <cwayne_> yeah
[13:39] <cwayne_> and it only seems to happen with trusty-proposed-customized-demo
[13:40] <cwayne_> my /cache/recovery is still completley populated too, looks like nothing was applied
[13:43] <cwayne_> sergiusens, ^
[13:44] <sergiusens> cwayne is it too big?
[13:44] <sergiusens> he customization; the recovery partition is not that huge
[13:44] <sergiusens> the*
[13:44] <sergiusens> wow
[13:44] <sergiusens> skipped words like crazy
[13:45] <sergiusens> cwayne is the customization done bigger than before; the recovery partition size is not that great
[13:45] <cwayne_> ah, yeah, this particular custom image is much larger
[13:45] <cwayne_> as it's got all the demo bits in it
[13:46] <cwayne_> sergiusens, what's the size limit?
[13:46] <sergiusens> ogra_: have that info handy? ^^
[13:47] <ogra_> nope
[13:48]  * sergiusens looks for a device
[13:48] <ogra_> seems to be 220M
[13:48] <ogra_> err
[13:48] <sergiusens> /dev/disk/by-partlabel/cache    552M   11M  542M   2% /android/cache
[13:48] <ogra_> sorry that was totally off
[13:48] <ogra_> yeah
[13:49] <sergiusens> cwayne ^^
[13:49] <sergiusens> you can't use all of it either
[13:49] <stgraber> cwayne_: pong
[13:50] <davmor2> pmcgowan: bug of the day https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1300236
[13:50] <cwayne_> stgraber, im having problems with trusty-proposed-customized-demo but i think it might just be because of the size
[13:50] <stgraber> ogra_: so that'd work, however note that this means that rebooting the Android container may not work then (we obviously don't do that automatically but some developers might)
[13:51] <ogra_> stgraber, rebooting it will work just not replacing the content
[13:51] <AskUbuntu> while installing ubuntu phone | http://askubuntu.com/q/441513
[13:51] <stgraber> ogra_: mounting a clean tmpfs at every container boot was done to simulate Android's ramfs as closely as possible (where if you reboot a standard Android system, you loose the content of the ramfs)
[13:51] <ogra_> stgraber, right, but we waste .5 seconds to running gzip twice
[13:52] <ogra_> and if there are no massive drawbacks i'l like to make that change, just looking for thiongs i could overseee here
[13:53] <stgraber> ogra_: so long as developers always powercycle the whole device when they want to test an Android change, I don't see any obvious drawback with that change
[13:53] <ogra_> wow, our lxc-android-config job needs quite some changes to fail gracefully (instead of hanging hard)
[13:53] <ogra_> stgraber, well, developers could even stop the container, unzip a new initrd and start it again
[13:54] <ogra_> its a rw tmpfs after all
[13:54] <ogra_> just one step more for them ... but one less for us on boot :)
[13:54] <cwayne_> sergiusens, did this size change recently?
[13:54] <sergiusens> zyga: hey, good to know it worked; not sure if the OEMs put in some stuff that we don't know about to break us; so flashing stock images always clears that up and runs/puts blobs we know about
[13:55] <zyga> sergiusens: yeah
[13:55] <sergiusens> cwayne you change check the ogra stats; not sure
[13:55] <zyga> sergiusens: though this is google :)
[13:55] <zyga> sergiusens: so it should be oem-free
[13:56] <ogra_> stgraber, so the CPU issue ... i think when we dont use cpu cgroups the kernel allocates two cores by default to teh container, i'll try to enable that in a test kernel to see if i can force it to all four (for the boot)
[13:56] <ogra_> stgraber, oh, and another thing, lxc-android-config has: "start on started cgroup-lite" did i see that being removed with a recent upload ? do we need to adjust anything ?
[13:57] <sergiusens> zyga: right; but google doesn't put in the real factory image on ;-) I bet there are deltas
[13:57] <stgraber> ogra_: no, if you don't specify any cgroup limit, you inherit from the root cgroup which is unlimited
[13:57] <ogra_> stgraber, hmm, then i dont get why it only uses 50%
[13:58] <stgraber> ogra_: cgroup-lite still technically exists, however it's correct that it's not longer required as we now use cgmanager. So you could replace "start on started cgroup-lite" by "start on started cgmanager" and then then drop the cgroup-lite dependency since cgmanager is already a dependency of liblxc1
[13:58] <ogra_> i wonder if the fact that we use an android kernel might change that inheritance
[13:58] <ogra_> stgraber, will do
[13:59] <stgraber> ogra_: it shouldn't, but there may be a scheduler setting that may help, let me try to find it
[14:00] <stgraber> ogra_: you may want to try "echo 0 > /proc/sys/kernel/sched_autogroup_enabled"
[14:01] <ogra_> root@ubuntu-phablet:/# cat /proc/sys/kernel/sched_autogroup_enabled
[14:01] <ogra_> cat: /proc/sys/kernel/sched_autogroup_enabled: No such file or directory
[14:02] <stgraber> without that (and for mostly good reasons), the task scheduler considers a whole LXC containers as a single process, so during a busy boot, this may impact boot performance when there are boot dependencies between the host and the container
[14:02] <stgraber> ah, then I guess it's off :)
[14:02] <ogra_> i guess we miss a kernel option here
[14:03] <stgraber> it may depend on the scheduler in use, not sure
[14:03]  * stgraber looks at the code
[14:03] <ogra_> stgraber, oh, looking at cgmanager.conf, can http://paste.ubuntu.com/7184917/ be dropped from lxc-android-config.conf ?
[14:04] <stgraber> probably, yes
[14:04] <stgraber> #ifdef CONFIG_SCHED_AUTOGROUP
[14:04] <stgraber> if that option isn't set, you get the equivalent of = 0
[14:05] <ogra_> ok
[14:06] <ogra_> hmm, no /dev/cpuctl when i remove the code
[14:06] <ogra_> so i guess we'll keep it
[14:07] <ogra_> :)
[14:07] <Saviq> ogra_, it feels like we need a dep between lxc-android-config and ubuntu-touch-session, the ones that disable surfaceflinger, don't we?
[14:07] <ogra_> well ...
[14:08] <cwayne_> stgraber, hey, how often does system-image get updated with new builds
[14:08] <ogra_> theoretically we do ... practically nobody uses these packages standalone :)
[14:10] <stgraber> cwayne_: every 5 minutes
[14:11] <stgraber> ogra_: well, that code won't work once you drop cgroup-lite...
[14:11] <stgraber> ogra_: you'll need to mount cgroupfs yourself if things actually expect it to be mounted in /dev/cpu
[14:12] <ogra_> stgraber, hmm, whats the drawback to keep it as is ... the start of the container has significant influence on the overall boottime
[14:12] <cwayne_> stgraber, hm ok, still waiting on custom-demo-45 to show up, will wait for it
[14:12] <ogra_> starting only after cgmanager will add significant delay i fear
[14:13] <Saviq> ogra_, yeah, but I just mean that upgrading only one or the other will break
[14:13] <Saviq> ogra_, or do you mean that we're not at the point when we care about such dep intricacies and just rely on the silo to land everything together?
[14:13] <Saviq> OTOH you can't upgrade lxc-android-config anyway...
[14:14] <stgraber> ogra_: why? both cgroup-lite and cgmanager share the same start condition so the actual boot time difference should be negligible (in either direction, I'm not actually sure which would be faster)
[14:14] <ogra_> Saviq, lxc-abdroid-config only puths the file in place, it can well be chnaged and uploaded after the session stopped using the file
[14:14] <stgraber> ogra_: your existing mount --bind could be replace by "mount -t cgroup cgroup /mnt -o cpu" and the "[ -d /sys/fs/cgroup/cpu ]" dropped
[14:15] <mhall119> bzoltan: will you be able to help me build Trojita in click chroot? I'm still getting an error about it not finding GLESv2
[14:17] <mhall119> [10:17:13] CMake Error at /usr/lib/arm-linux-gnueabihf/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:16 (message): Failed to find "GLESv2" in "" with CMAKE_CXX_LIBRARY_ARCHITECTURE "arm-linux-gnueabihf".
[14:17] <mhall119> I'm on Saucy, click choot is for Trust
[14:18] <mhall119> Trusty
[14:22] <davmor2> mhall119: is a choot like a chroot /me wonders off quickly ;)
[14:22] <ogra_> stgraber, right, no difference when i change the start condition to cgmanager (just quickly did two bootcharts)
[14:22] <Saviq> ogra_, it also disables surfaceflinger
[14:22] <Saviq> ogra_, does it not?
[14:23] <ogra_> Saviq, yes, but it does that based on the file it puts in place
[14:23] <ogra_> which it does now anyway
[14:23] <Saviq> ogra_, yeah, but if someone removed it
[14:23] <ogra_> later the check for the file will be dropped
[14:23] <Saviq> ogra_, it will now disregard it
[14:23] <ogra_> yes
[14:23] <Saviq> ogra_, and disable surfaceflinger anyway
[14:23] <ogra_> like it will in the future
[14:24] <ogra_> the package the file creates also uses teeh check
[14:24] <ogra_> *the
[14:24] <stgraber> ogra_: good to hear!
[14:24] <Saviq> ogra_, while non-upgraded ubuntu-touch-session would still set up env to expect surfaceflinger running
[14:24] <Saviq> ogra_, I think this is what  should happen: http://pastebin.ubuntu.com/7184985/
[14:24] <ogra_> Saviq, right, lxc-android-config needs to land after your changes
[14:24] <Saviq> ogra_, disregard the first three, just look at l-a-c and u-t-s
[14:24] <Saviq> ogra_, no, it actually needs to land together
[14:24] <davmor2> Who is the best person to talk to about how app descriptions are rendering in the apps scope?
[14:25] <ogra_> Saviq, huh ? why ?
[14:25] <ogra_> Saviq, you drop all code that cares for the file from the session
[14:25] <Saviq> ogra_, yeah, but if l-a-c still does care
[14:25] <Saviq> ogra_, surfaceflinger will start
[14:25] <ogra_> so it doesnt matter when l-a-c loses it
[14:26] <Saviq> ogra_, and mir will fail to start
[14:26] <ogra_> why would sf start ?
[14:26] <Saviq> ogra_, if someone has the file removed
[14:26]  * ogra_ doesnt get it 
[14:26] <ogra_> *we*put the file in place
[14:26] <ogra_> on boot
[14:26] <ogra_> from the very same package
[14:26] <Saviq> ogra_, the last change you uploaded to l-a-c, does it not check for .display-mir?
[14:26] <ogra_> ?
[14:27] <ogra_> i did not upload any l-a-c changes regarding that
[14:27] <ogra_> only to your silo
[14:27] <Saviq> ogra_,    * always force-disable surfaceflinger from
[14:27] <Saviq>     /var/lib/lxc/android/pre-start.d/ when starting up teh android container,
[14:27] <Saviq>     we use Mir only now
[14:27] <ogra_> right
[14:27] <Saviq> ogra_, that's what I mean, yes
[14:27] <Saviq> ogra_, so, if you remove the file in ~phablet
[14:27] <ogra_> but thats in no way tied to your changes
[14:27] <Saviq> ogra_, upgrade l-a-c
[14:27] <Saviq> ogra_, reboot
[14:27] <ogra_> they can land together or l-a-c can land that chnage later
[14:28] <ogra_> it cant land *before* your changes are in
[14:28] <Saviq> ogra_, landing later or earlier does not force things to upgrade together, does it
[14:28] <ogra_> but i doesnt need to land together
[14:28] <Saviq> ogra_, so even if it lands later, you'll be able to upgrade l-a-c
[14:28] <ogra_> it doesnt matter, you dont use the file anymore
[14:28] <ogra_> so it doesnt matter of l-a-c creates it or not
[14:29] <Saviq> ogra_, not if you only upgrade l-a-c
[14:29] <ogra_> (it only matters for l-a-c itself)
[14:29] <Saviq> ogra_, let's start from scratch
[14:29] <Saviq> ogra_, you flash a device, you remove the file and upgrade l-x-c, you reboot
[14:29] <ogra_> it should just not land before your changes
[14:30] <dbarth> ./away
[14:30] <Saviq> ogra_, order of landings does not matter, if you upgrade stuff manually, that's what I asked initially - do we care at all
[14:30] <cwayne_> stgraber, hey, can you check and make sure nothing's gone wrong with import custom-demo build number 45?  it's been 45 mins and not seeing it on pool yet
[14:30] <Saviq> ogra_, on next boot, surfaceflinger won't be started (l-a-c will force-stop it), but the rest will still want to use sf, and fail
[14:31] <stgraber> cwayne_: checking now
[14:31] <ogra_> Saviq, right, we can add a dep if you feel better with it :)
[14:31] <Saviq> ogra_, I'm just trying to make sure that upgrading l-a-c will also force upgrade of u-t-s, and in effect unity8 and all
[14:31] <Saviq> ogra_, \o/ :)
[14:31] <Saviq> ogra_, didrocks says ok, too :D
[14:32] <Saviq> ogra_, so, Breaks: ubuntu-touch-session (<< 0.107) please :)
[14:32] <ogra_> ok
[14:32] <pmcgowan> davmor2, I see that in 266, probably came with the new previews last week
[14:33] <stgraber> cwayne_: there's a new image being imported at the moment (30min into the import), it may be that yours will show up in the same batch
[14:33] <davmor2> pmcgowan: indeed just talking to alecu about it on another channel
[14:34] <ogra_> Saviq, still silo 15 ?
[14:36] <cwayne_> stgraber, ah, okay
[14:36] <alecu> pmcgowan, davmor2: I just got confirmation from saviq that this is a dash issue
[14:36] <cwayne_> so soonish it should show up then?
[14:37] <stgraber> cwayne_: looking at the log, it picked up build 45 and generated a delta for that
[14:38] <Saviq> ogra_, yes
[14:39] <cwayne_> stgraber, hm, any idea why its not showing up then? or is it just still going
[14:39] <ogra_> bah, complains that it cant accept the UNRELEASED distro :P
[14:39]  * ogra_ fixes
[14:39] <stgraber> cwayne_: still going
[14:40] <didrocks> jdstrand: stgraber: hey! FYI, it seems one of lxc/apparmor upload (I couldn't decouple them in the bisecting) aggravieting the fact that we couldn't get crash file from apport (it segfaulted). Now we have apport with https://code.launchpad.net/~xnox/apport/fix-cgroup/+merge/212282, so fixed! But I think it would be nice if you can include in your test plan the fact to simulate a sigsegv and ensure we
[14:40] <didrocks> get a crash file out of it.
[14:40] <alecu> davmor2, pmcgowan: on triple checking, it seems that it might be the click scope after all. I'm debugging it right now
[14:41] <cwayne_> stgraber, ack, thanks. sorry for being impatient :)
[14:42] <stgraber> didrocks: lxc doesn't do anything apport-specific so I don't think this would belong in our testsuite
[14:42] <didrocks> stgraber: it seems to be cgroups related (creating the crash), so maybe the cgmanager?
[14:43] <didrocks> if lxc doesn't touch cgroups, yeah, fine then :)
[14:43] <stgraber> well, I'd argue that if apport reads the cgroup information from processes, then apport itself should test that feature in its testsuite
[14:43] <stgraber> it's not like it's reading any file coming out of cgmanager, it's parsing the kernel's cgroup file
[14:44] <didrocks> yeah, so it was for you a wrong way of apport to read it? something regressed it though (and maybe aggraviated the wrong behavior)
[14:45] <pitti> it currently tries to determine the session startup time by stat'ing /sys/fs/cgroup/systemd/' + my_cgroup
[14:45] <pitti> reading that might not be allowed any more?
[14:47] <Saviq> davmor2, didrocks, it's not unity8 for sure as it works fine in e.g. the music scope
[14:48] <didrocks> Saviq: ok, thanks for the check! all info on bug? (feel free to reassign if not done already)
[14:49] <davmor2> Saviq: indeed I have been told multiple times by different people though that displaying of scopes is handled by unity8 hence targeting that :)
[14:49] <Saviq> davmor2, yes, that's fine
[14:49] <davmor2> Saviq: hence the first line in the bug :)
[14:49] <Saviq> davmor2, I'm not complaining :)
[14:49] <Saviq> davmor2, just delegating
[14:50] <davmor2> haha
[14:50] <Saviq> alecu, https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1300236
[14:51] <Saviq> alecu, actually https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1298327 is the first one
[14:52] <rickspencer3> dpm, kyleN hey, so I am actually making search results in my scope now! however, my previews just say "title/author" :)
[14:52] <stgraber> cwayne_: how are things looking now?
[14:52] <alecu> Saviq: thanks
[14:53] <cwayne_> stgraber, much better, thanks :D
[14:54] <dpm> rickspencer3, do you have some code in a +junk branch for us to have a look at? I say "we", but I'll probably defer it to kyleN, as after this week he's much more a scopes expert than I am :)
[14:54] <rickspencer3> dpm,  I could put it there, but I has assumed there was a part of the tutorial I have not looked at yet ;)
[14:57] <kyleN> rickspencer3, i am working on the docs now. I expect them done by the end of the day
[14:57] <rickspencer3> kyleN, ok, I guess I can wait :)
[14:57] <kyleN> rickspencer3, the trick is understanding the mapping between attr values in your result and connecting them to the preview widgets
[14:58] <kyleN> it is somewhat obscure - but the mapping does exist ;)
[14:58] <rickspencer3> kyleN, ok, I'll wait for our docs
[14:58] <rickspencer3> meantime, I have to figure out how to extract links to images in a QString
[14:58] <rickspencer3> that should keep me busy :)
[14:58] <kyleN> rickspencer3, if you want a working ex, you can bzr branch lp:ubuntu-sdk-tutorials and go to scope/
[15:04] <jr_machado> Bom dia pessoal!
[15:04] <jr_machado> Aqui é o Canal Ubuntu Touch né?!
[15:05] <jr_machado> Estou usando um Cliente IRC para Android chamado Yaaic e ele não deixa muito claro onde é que eu estou.
[15:05] <dobey> english please
[15:07] <jr_machado> Here is Ubuntu Touch Channel? Because the cliente IRC who i using no say where i'am.
[15:07] <asac> jr_machado: yes :)
[15:07] <ogra_> yes, this is the Ubuntu channle for phone and tablet
[15:08] <jr_machado> I using Yaaic onde client IRC for Android.
[15:08] <Brayan> Hi
[15:08] <jr_machado> one*
[15:10] <jr_machado> My spell check are in portuguese, sorry by the erros.
[15:12] <jr_machado> Ubuntu Touch is expected to compatibility with Android applications?
[15:14] <tshirtman> no, the android api is not there, afaik
[15:14] <davmor2> jr_machado: No, It is expected that developers will at least initially have an easy way to port an android app to Ubuntu.  But initial plans are not to have a compatibility layer.
[15:16] <mhall119> davmor2: :-P
[15:17] <davmor2> mhall119: hahahaha
[15:17] <jr_machado> I understand, but if someone wants to develop something similar to Wine to put Android apps will be allowed?
[15:19] <jr_machado> Because you're laughing?
[15:19] <jr_machado> It's a only ideia.
[15:20] <rsalveti> ogra_: Saviq: another MR to drop SF: https://code.launchpad.net/~rsalveti/powerd/drop_support_sf/+merge/213340
[15:20] <rsalveti> should we include it as part of the big landing?
[15:21] <Saviq> rsalveti, yeah, let's
[15:21] <jr_machado> Maybe could be an asset Ubuntu Touch have interoperability with Android.
[15:21] <ogra_> rsalveti, noooo dont hold up Saviq P
[15:22] <Saviq> rsalveti, or well, this looks very separate
[15:22]  * ogra_ has lxc-android-config stuff starting to pile up
[15:22] <ogra_> i want that silo to land :P
[15:22] <Saviq> OTOH it does look at .display-mir, and if we don't create that file on mir...
[15:22] <rsalveti> we can land it separately, but only after you landed your silo
[15:23] <rsalveti> right, that's why I removed the check
[15:23] <rsalveti> Saviq: are you planning to land this today?
[15:23] <Saviq> rsalveti, ogra_, yeah, we need to land it together IMO
[15:23] <Saviq> rsalveti, yes
[15:24] <ogra_> doit then :)
[15:24]  * Saviq adds
[15:24] <rsalveti> alright :-)
[15:25] <ogra_> Saviq, do you think you can land that today ?
[15:25]  * ogra_ assumes it needs a new round of testing 
[15:27] <Saviq> Mirv, can we please get a reconfigure on silo 015?
[15:30] <Saviq> rsalveti, bump changelog on powerd please, and ogra_ please Breaks powerd (<< 0.14), too?
[15:30] <ogra_> hmpf
[15:30] <rsalveti> don't think we need a breaks
[15:30] <Saviq> rsalveti, we do
[15:30] <Saviq> rsalveti, if l-a-c gets upgraded, and people were using surfaceflinger
[15:31] <Saviq> rsalveti, sf won't be there, but powerd will still try and blank/unblank through it
[15:31] <rsalveti> but how adding a breaks into powerd will actually help that?
[15:31] <Saviq> rsalveti, not in powerd
[15:31] <Saviq> rsalveti, in l-a-c
[15:32] <rsalveti> oh, then yeah
[15:32] <Saviq> rsalveti, will force upgrading powerd as part of the l-a-c upgrade
[15:32] <rsalveti> let me bump the version
[15:32] <Saviq> ogra_, sorry, I want to land this asap, too, but I also don't want to make a boo boo
[15:32] <ogra_> indeed
[15:33] <ogra_> gimme 10min and i can add the breaks
[15:33] <ogra_> (not close to the machine with the l-a-c shource atm)
[15:33] <davmor2> ogra_: no don't break stuff it's bad enough with the ones we got ;)
[15:33]  * Saviq starts thinking the (non)existence of that file was a bad way to switch between mir and sf :D
[15:33] <ogra_> davmor2, blame Saviq he asked me to add that :P
[15:34]  * Saviq wears the blame like an armor
[15:34] <davmor2> haha
[15:34] <ogra_> Saviq, it was a quick hack ...
[15:34] <Saviq> ogra_, as always :)
[15:34] <ogra_> it did well for being duct tape and strings :)
[15:35]  * davmor2 understands why Saviq needs the armour with ogra_ quickly hacking at him
[15:35] <rsalveti> Saviq: bumping to 0.14-0ubuntu1 should be enough, right? I believe CI train will bump with the proper format later on
[15:35] <Saviq> davmor2, well now, ogra_ is nice and fluffy, the most he'd hack at me is a teddy-bear-paw
[15:35] <Saviq> rsalveti, yup
[15:35] <ogra_> lol
[15:35] <rsalveti> great
[15:38] <ogra_> Saviq, uploaded
[15:41] <Saviq> ogra_, thanks
[15:42] <Saviq> rsalveti, can you reconfigure silo 015 please? powerd wasn't a component there before
[15:42] <rsalveti> I think I can, 1 sec
[15:43] <rsalveti> Saviq: hm, can't change the list of projects
[15:44] <Saviq> rsalveti, interesting, weren't you meant to be one of the US landing team little helpers?
[15:45] <rsalveti> Saviq: yes, but I don't have access to all the keys yet
[15:45] <Saviq> cyphermox, can you? reconfigure silo 015 for us?
[15:45] <rsalveti> I'm pinging didrocks at #ubuntu-ci-eng
[15:57] <rsalveti> stgraber: hey, the generic_x86 image is now published at http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/
[15:57] <rsalveti> stgraber: would you mind adding it to the system-image server later on?
[15:57] <rsalveti> together with the x86 rootfs
[16:01] <stgraber> rsalveti: ok, added to my todo, that may take a small code change to system-image so not exactly trivial
[16:01] <stgraber> (server side only tweak, the client should be fine)
[16:21] <rsalveti> stgraber: sure, no worries, thanks
[16:23] <cyphermox> Saviq: yes
[16:24] <Saviq> cyphermox, it's done already, sorry
[16:24] <cyphermox> ok
[16:28] <Saviq> rsalveti, we can still install powerd alone... we should add a Breaks: there, but Breaks: what... :D
[16:29]  * Saviq thinks ubuntu-touch-session maybe
[16:29] <Saviq> rsalveti, wdyt?
[16:38] <Saviq> ogra_, any idea what pulled unity8-fake-env onto the device?
[16:38] <ogra_> Saviq, unity8-autopilot ?
[16:38] <ogra_> iirc its a dep
[16:38] <Saviq> ogra_, it's not installed
[16:40] <ogra_> thsn i dont know
[16:40] <Saviq> ogra_, apt-cache rdepends only mentions unity8... but then I can purge unity8-fake-env and nothing else goes
[16:40] <Saviq> weeeird
[16:40] <ogra_> i'm sure it comes from some autopilot part
[16:50] <Saviq> mhr3, a bug for you: bug #1300304
[16:50] <Pa^2> Acer laptop running 13.10 suspends correctly from upper right menu, when suspended via lid close touch screen does not work.  Any thoughts?
[16:51] <mhr3> Saviq, expected, there's invalidation on install/uninstall
[16:51] <Saviq> mhr3, I know, that's why it's for you (i.e. model diffs)
[16:52] <mhr3> Saviq, Wishlist? :)
[16:52] <RobertNexusS> hello =). My name is Robert and I am trying out ubuntu touch on my nexus S. I am at the point when I am in bootloader mode and typing the command in the terminal, but I get this response: Device herring not found on server https://system-image.ubuntu.com channel devel. Whats up with this? :S
[16:52] <popey> RobertNexusS: nexus s is not one of our supported devices.
[16:53] <popey> there may be a community port..
[16:53] <popey> !devices | RobertNexusS
[16:53] <Saviq> Pa^2, this channel is for Ubuntu phones and tablets, not yet for touch-enabled laptops, you'd be better off going to #ubuntu-desktop
[16:53] <popey> that page has details.
[16:53] <Pa^2> ty
[16:54] <RobertNexusS> popey: oh. So that makes it impossible to do then? I can add that this phone is junk anyways. I am just trying to learn new things. The planet will not stop rotating if I fail =)
[17:00] <ogra_> RobertNexusS, check the devices wikipage, there might be an image for that device ... but you will have to do a manual install (most likely following a guide on the xda-developers forum) and most of the external ports are way behind
[17:01] <RobertNexusS> Thanks ogra. i will check into it!
[17:02] <ogra_> tedg, did you see my two bugs from the weekend ? hud needs to fix its upstart job and indicator-messages doesnt use upstart yet
[17:03] <tedg> ogra_, No, haven't gotten there yet. The indicator-messages MR is queued, haven't looked at the HUD one.
[17:03] <ogra_> looks like a simple copy/paste error
[17:03] <ogra_> the pre-start script is in the job twice
[17:04] <tedg> ogra_, https://code.launchpad.net/~ted/indicator-messages/startup-cleanup/+merge/207775
[17:04] <tedg> ogra_, Ah, probably a merge error.
[17:04] <ogra_> yeah
[17:04] <ogra_> trivial to fix i guess
[17:04] <ogra_> megre-> awesome !
[17:06] <ogra_> tedg, it might also be interesting to know why the evolution pieces start so late http://people.canonical.com/~ogra/touch-bootcharts/ubuntu-phablet-trusty-269.png
[17:06] <ogra_> though thats not an urgent thing
[17:07] <tedg> ogra_, Guessing the evo calendar is started by datetime
[17:07] <ogra_> yeah, that might be
[17:07] <ogra_> datetime eats some CPU cycles on its own startup
[17:07] <tedg> ogra_, That's because you have too many hot dates ;-)
[17:07] <ogra_> haha
[17:18] <BrayanSteve> olá pessoal
[17:21] <BrayanSteve> Teriam como me esclarecer uma dúvida?
[17:26] <BrayanSteve_> Hi
[17:27] <BrayanSteve_> Could me a question?
[17:29] <popey> !ask | BrayanSteve_
[17:35] <BrayanSteve> Did you install Ubuntu system on my Smartphone.. He is a Razr D1..the possibility that this system be installed on my smartphone?
[17:38] <BrayanSteve> i'm no speaking english very well...
[17:38] <BrayanSteve> I'm still learning
[17:42] <BrayanSteve> Did you install Ubuntu system on my Smartphone.. He is a Razr D1..the possibility that this system be installed on my smartphone?
[17:46] <zyga> BrayanSteve: I don't think that razr d1 is supported
[17:48] <BrayanSteve> got it.. but there is a possibility?
[17:49] <amin_> hi
[17:49] <zyga> BrayanSteve: if you or someone else works on it, yeah, have a look at https://wiki.ubuntu.com/Touch/Porting
[17:50] <zyga> BrayanSteve: also look at https://wiki.ubuntu.com/Touch/Devices
[17:50] <BrayanSteve> ok..
[17:52] <amin_> my device is: 512mb ram 650MHz powervr 543 can i setup ubuntu touch??
[17:55] <amin_> my device is: 512mb ram 650MHz cpu powervr 543 gpu can i setup ubuntu touch??
[17:55] <zyga> amin_: see the two links I gave to BrayanSteve_
[17:56] <amin_> Ok tanx
[17:57] <BrayanSteve_> but if I install the razr family are mentioned in the list, you can go right?
[18:01] <BrayanSteve_> configuration of my Smartphone: 1ghz, 1gb ram, 4gb intenal + 2gb external
[18:06] <pmcgowan> davmor2, Saviq apps scope scrolling is much jumpier in 270 it seems
[18:10] <davmor2> pmcgowan: no different for me than it has been with the new scopes, only added issue has been that all of a sudden the listing only display on the top half of the screen.  The app scrolling is technically smooth the issue is there are no stored icons so it has to pull them everytime
[18:10] <davmor2> pmcgowan: I think that is being worked on though as I understand it
[18:11] <pmcgowan> davmor2, ok but seems different to me, scrolling to the top it freezes then shows the open apps all at once
[18:11] <pmcgowan> either way not so nice
[18:13] <davmor2> pmcgowan: oh yes does seem to judder more on the installed apps if you scroll it quickly
[18:13] <pmcgowan> yep
[18:20] <janimo> ogra_, which upstart signal to start on if I want to do something after the container is fully initialized?
[18:20] <janimo> ogra_, android-container ? android ?
[18:21] <ogra_> amdroid
[18:21] <ogra_> android-container is for properties
[18:22] <janimo> ogasawara, thanks
[18:22] <janimo> sigh
[18:22] <ogra_> http://paste.ubuntu.com/7186133/
[18:22] <ogra_> see here ... on how to use the property stuff
[18:23] <janimo> ogra_, I saw the adbd script starts on android-container so I thought that is the signal
[18:24] <bzoltan> mhall119:  tomorrow morning I will do help. I suggest to remove the old chroot and create a new one as start
[18:24] <janimo> knowing that adbd is started 'after the container is initialized'
[18:24] <ogra_> janimo, it doesnt start on android-container, it starts on "android-container persist.sys.usb.config=*adb"
[18:24] <ogra_> which means it starts as soon as someone adds "adb" to that property
[18:25] <janimo> ogra_, hmmmm I just discarded that as some unimportant details I guess :)
[18:25] <ogra_> heh
[18:25] <janimo> ogra_, so if I wanted to write into a device node created by android and wanted to make sure it exists, is the best way to just poll for it ?
[18:26] <ogra_> no, then android is the right event
[18:26] <ogra_> it only gets emitted once ueventd is fully done and the init.rc scripts are run
[18:26] <janimo> ogra_, ack
[18:28] <mhall119> bzoltan: thanks, I appreciate it
[18:31] <AskUbuntu> does ubuntu-sdk all programming language supports all mobile devices? | http://askubuntu.com/q/441616
[19:05] <omac> is there a plugin for ubuntu-sdk to transparently integrate ubuntu-touch projects to github and launchpad?
[19:12] <omac> does the git->gerrit tool within the ubuntu-sdk work with github and launchpad?
[19:15] <robotfuel> who can review and approve my simple MP for the platform-api project? https://code.launchpad.net/~chris.gagnon/platform-api/get_coverage_in_ci/+merge/213533
[19:47] <dansuf> Can someone help me? I'm porting touch to my phone and with surfaceflinger chosen I've got EGL_BAD_CONTEXT and in dmesg binder: 644:644 transaction failed 29189, size 56-0 or binder: 644:791 transaction failed 29189, size 56-0 evgery time there's this egl warning
[19:47] <dansuf> every*
[19:49] <nhaines> dansuf: I think they just completely removed surfaceflinger support from Ubuntu in the last couple of days.
[19:50] <greyback> nhaines: dansuf: hasn't happened yet, but will be today/tomorrow
[19:51] <greyback> robotfuel: I approved it. I don't have landing powers tho
[19:51] <dansuf> nhaines, greyback, thank you for this information, mir also doesnt work for me, maybe even for the same reason
[19:52] <dansuf> which is still a mystery for me
[19:52] <robotfuel> greyback: thanks, do you know who I talk to so it can land?
[19:52] <greyback> robotfuel: kgunn
[19:52] <greyback> he should be able to help
[19:52] <robotfuel> greyback: thanks
[19:53] <greyback> dansuf: sadly I don't know how to help you, but  mail to ubuntu-phone@lists.launchpad.net would get the right people looking at it
[19:55] <dansuf> greyback: Thanks, I will mail to them if I don't get any help here.
[19:56] <greyback> dansuf: it's worth lurking here for a while more. There are people in europe who might be able to help too, so pop by tomorrow?
[19:58] <dansuf> greyback: You mean that there are more helpful people at working time in europe timezone?
[19:58] <nhaines> dansuf: yes, that's when most of the core developers work.
[19:59] <greyback> dansuf: likely, but there are some in the US who could also help. So all I can say is be patient and hope the right person swings by
[20:00] <dansuf> nhaines: greyback: ok, thank you, I live in europe and I attend to school during working hours so it will be better for me to use mailing lists, I think
[20:01] <greyback> welcome
[20:01] <kgunn> robotfuel: so you just need someone to land it for you ?
[20:01] <robotfuel> kgunn: yes
[20:02] <kgunn> robotfuel: lemme check something real quick
[20:03] <kgunn> dansuf: if you'd be willing, you might hang out in #ubuntu-mir...and see if you can get your port working with mir (since that's what they do...you'll get better response vs surfaceflinger)
[20:05] <dansuf> kgunn: I've been there and the person who helped me didn't know what's the problem
[20:06] <kgunn> dansuf: what's your device? and what stage are you at ? e.g. can you boot the ubuntu kernel ?
[20:06] <kgunn> sergiusens: so...i see you have platform-api updates going in, would you be able to add in some new testing coverage supplied by robotfuel ?
[20:07] <dansuf> kgunn: it's se live with walkman, a'ka coconut and my kernel boots, container boots and I can get some tests working
[20:07] <kgunn> sergiusens: https://code.launchpad.net/~chris.gagnon/platform-api/get_coverage_in_ci/+merge/213533
[20:07] <sergiusens> kgunn: hmmm, no I shouldn't have any silo assigned :-)
[20:07] <kgunn> sergiusens: line 8 ?
[20:07] <sergiusens> kgunn: might be a missed thing by Mirv; that silo needs fixing from riccm first
[20:08]  * sergiusens sorts it
[20:08]  * sergiusens hasn't dealt with ci train in a week and feels the joy
[20:09] <kgunn> hehe
[20:09] <sergiusens> robru: cyphermox can you free up silo 5? as in cancel?
[20:09] <dansuf> kgunn: test_glesv2 works but mir tests show errors with binding buffer to texture
[20:10]  * sergiusens goes to the correct channel
[20:12] <kgunn> dansuf: checking something...
[20:14] <kgunn> dansuf: so you already install mir-test-tools on your device ?
[20:14] <dansuf> kgunn: I installed mir-demos or something like that
[20:14] <kgunn> dansuf: if you could install mir-test-tools, and run mir_integration_tests
[20:15] <dansuf> kgunn: it's preinstalled fortunately
[20:16] <kgunn> i believe if it fails to run properly, it might provide more hints
[20:16] <dansuf> kgunn: So I run it and got an image on the screen for less than a second
[20:16] <dansuf> and it passed
[20:16] <kgunn> hmmm, that's good, that means at the mir driver level things are "all good"
[20:17] <kgunn> dansuf: so just curious...if you just try to start unity8 from the command line what does it do ?
[20:17] <dansuf> QXcbConnection: Could not connect to display
[20:19] <dansuf> kgunn: I should mabe give the whole log  generated by logcat when running lightdm
[20:19] <dansuf> with mir it gives more egl-related errors
[20:19] <kgunn> dansuf: hmmm, that sounds like the Qt plugin might be wrong ? xcb instead of mir ?
[20:19] <kgunn> greyback: ^
[20:20] <rickspencer3> kyleN, thanks for the scopes docs, I'll check them out tomorrow
[20:20] <rickspencer3> kyleN, I finally got my head around QXmlStreamReader, I htink I may do a blog post on it, I bet a lot of scope authors will want to use it
[20:20] <greyback> kgunn: dansuf: check the value of QT_QPA_PLATFORM - it should contain "ubuntumirclient" - if not, change it so it does
[20:20] <greyback> dansuf: that is an environment variable
[20:21] <dansuf> greyback: If I do it right (echo $QT_QPA_PLATFORM) it's empty
[20:22] <greyback> dansuf: ok, then "export QT_QPA_PLATFORM=ubuntumirclient"
[20:22] <dansuf> greyback: done it already
[20:22] <kgunn> dansuf: ok now try and launch  unity8
[20:23] <dansuf> greyback: kgunn:  WARNING: QApplication was not created in the main() thread.
[20:23] <dansuf> Service name already taken.
[20:23] <dansuf> Could not register to DBus session.
[20:23] <dansuf> terminate called after throwing an instance of 'std::logic_error'
[20:23] <dansuf>   what():  basic_string::_S_construct null not valid
[20:23] <dansuf> Aborted (core dumped)
[20:23] <kgunn> mmm... how about stop unity8, then start unity8 ;)
[20:24] <dansuf> unknown job :)
[20:24] <dansuf> aa
[20:24] <dansuf> i see
[20:24] <kgunn> are you root? or phablet ?
[20:24] <kyleN> rickspencer3, 'welcome
[20:24] <dansuf> root
[20:24] <kgunn> dansuf: yeah gotta be phablet....
[20:24] <dansuf> ok
[20:25] <kgunn> one moment
[20:25] <dansuf> so
[20:25] <dansuf> lots of errors and at the end what():  error binding buffer to texture
[20:25] <dansuf> so generally the one I had before
[20:26] <dansuf> I think it is hardware-related issue
[20:26] <greyback> dansuf: could you please use a pastebin tool like pastebin.ubuntu.com to show us all the output?
[20:26] <dansuf> greyback: yeah
[20:27] <popey> ahayzen: seen http://paste.ubuntu.com/7186673/ on music-app? balloons suggests you have?
[20:27] <greyback> dansuf: let's try something simpler first, before trying unity8. Please install the "mir-demos" package and let me know when you're ready
[20:27] <dansuf> greyback: I've already tried mir-demos
[20:27] <kgunn> greyback: he did run mir_integration_tests
[20:28] <greyback> ah ok
[20:28] <dansuf> greyback: kgunn: I run the long one with fb at the end and it run successfully annd the rest threw error binding buffer to texture
[20:28] <kgunn> dansuf: did you start mir_demo_server before trying some other demo_client ?
[20:28] <dansuf> kgunn: yup
[20:28] <kgunn> ah...ok, so mixed success/failure
[20:28] <dansuf> greyback: kgunn: pastebin.ubuntu.com/7186701/
[20:31] <greyback> dansuf: yeah seems the eglCreateImageKHR call in Mir is failing for some reason. I haven't the first idea why
[20:32] <dansuf> kgunn: greyback: I checked the standalone test and input also works and render_surfaces doesn't show any error but the screen is balck and i can't stop it
[20:32] <dansuf> greyback: Yes I've seen this error before in my logs
[20:37] <kdub> dansuf, did you get surfaceflinger working without that error?
[20:37] <dansuf> kdub: my surfaceflinger didnt work and didn't throw that error as far as I remember
[20:38] <dansuf> kgunn: greyback: kdub: thank you for your help but it's really late and I have to go to sleep sonn.
[20:39] <kgunn> later
[20:39] <greyback> no worries, I wish you luck
[20:39] <kgunn> hope it starts working for you
[20:39] <dansuf> thanks
[20:53] <tedg> bfiller, popey, Do you guys know why some apps are shipping blank url-dispatcher files?
[20:55] <popey> tedg: probably generated by the sdk
[20:56] <tedg> popey, Who can stop that craziness! :-)
[20:57] <mterry> saviq, btw, I updated my USC branches to compile against latest Mir.  You may also want to pick up lp:~alan-griffiths/unity-mir/compatibility-with-mir-changes for unity-mir compatibility
[20:57] <mterry> (for silo 002)
[21:08] <ahayzen> popey, seen something similar i'll have a look later, just going shops :)
[21:08] <ahayzen> popey, is there a bug report?
[21:09] <popey> I'll file one..
[21:09] <ahayzen> popey, thanks
[21:12] <popey> ahayzen: bug 1300450
[21:15] <zte_kis_plus> hello
[21:15] <zte_kis_plus> i want to install ubuntu in my zte kis plus
[21:15] <zte_kis_plus> how can i do this?
[21:16] <zte_kis_plus> any one here?
[21:17] <zte_kis_plus> hellooooooooooooooooooooooooo
[21:17] <zte_kis_plus> please people need help
[21:19] <fps> hi, is there anything one can do about the device appearing and disappearing constantly on the usb port?
[21:19] <fps> this kde notification is so annoying that i almost can't charge the phone
[21:20] <zte_kis_plus> yes
[21:20] <zte_kis_plus> is bicouse usb version
[21:20] <fps> zte_kis_plus: do you have more details?
[21:21] <zte_kis_plus> you may need to use usb 2.0 or higher
[21:21] <fps> hmm
[21:21] <fps> why would that be an issue?
[21:22] <zte_kis_plus> i know from windows
[21:22] <fps> and i think a] my port is an usb 2.0 port and my hub, too
[21:22] <zte_kis_plus> the same
[21:22] <fps> it works great for android devices
[21:22] <fps> it's just ubuntu touch. it's like the service is constantly restarting
[21:22] <fps> that kinda coincides with the UI crashing pretty often, too
[21:22] <zte_kis_plus> but in windows is show message that yous hould conect into a high hub like 3.0
[21:23] <zte_kis_plus> or any other hub that have extenral power
[21:23] <pmcgowan> fps, are you using the latest image? and on which device?
[21:23] <zte_kis_plus> well then my be a bad instalation
[21:23] <zte_kis_plus> or configuration into your phone
[21:23] <zte_kis_plus> any way
[21:23] <zte_kis_plus> i want to install ubuntu into my  zte kiss plus
[21:23] <zte_kis_plus> but how can i do that?
[21:23] <fps> pmcgowan: it's a nexus 4 and i updated a few days ago.. r250. interestingly enough my buffy got 263 or so ;D
[21:23] <pmcgowan> zte_kis_plus, did you check the ports page?
[21:24] <zte_kis_plus> no
[21:24] <zte_kis_plus> what is that?
[21:24] <fps> pmcgowan: i had to use the OTA updater, since ubuntu-flash-device failed to push the image
[21:24] <pmcgowan> !devices
[21:24] <fps> s/buffy/buddy
[21:25] <zte_kis_plus> cant find zte
[21:25] <zte_kis_plus> :(
[21:25] <pmcgowan> fps, 250 was the last image promoted to the devel channel I suspect, and the prorposed channel is up to 270 now, but neither should ahev the issue you see
[21:25] <fps> pmcgowan: ok, i rechecked it's r250 on this device.. and yeah, i initially pushed the image from the devel channel. might be that my buddy used devel-proposed, true..
[21:26] <zte_kis_plus> so bad is no image from the actuals that may work with my zte? i mean i dont know about this compatibility
[21:26] <zte_kis_plus> but i love to have ubuntu in my zte
[21:26] <pmcgowan> zte_kis_plus, seems no one has ported it
[21:26] <pmcgowan> zte_kis_plus, there are instructions in the porting guide but it takes some work
[21:27] <fps> pmcgowan: ah, using the UI actually made it stop disappearning and reappearing on the bus
[21:27] <t1mp> fps: did you try a different USB cable and other USB port?
[21:27] <zte_kis_plus> well how much will cost me for some one to make it for me?
[21:27] <pmcgowan> fps, could be a bug in that revision then
[21:28] <fps> pmcgowan: or like t1mp said it coul dbe that my cable or port are bad..
[21:28] <pmcgowan> yep
[21:28] <fps> t1mp: i used this cable on a different port, yes, same behaviour..
[21:28] <fps> t1mp: i'll see if i can find another cable.. though this one works just fine with the android devices i connect with it
[21:30] <zte_kis_plus> pmcgowan, do you know how to make it?
[21:30] <pmcgowan> zte_kis_plus, no sorry, there may be folks willing to help you could ask on the mailing list
[21:32] <zte_kis_plus> here is my email tuningteam@yahoo.com if you know some one that can make please send me email or the respective person contact me
[21:33] <pmcgowan> zte_kis_plus, join this team and mailing list https://launchpad.net/~ubuntu-phone
[21:35] <zte_kis_plus> ok i have registred
[21:35] <zte_kis_plus> now?
[21:37] <zte_kis_plus> sorry but i'm new to this one i mean i use linkus etc.. but not using so much forums website etc..
[21:37] <zte_kis_plus> i will be back later need to reboot pc
[21:39] <fps> t1mp: oh wow, the power cable of the usb hub got detached ;D
[21:39] <fps> t1mp: so power was just lacking...
[21:44] <t1mp> fps: ok, so it is solved now :)
[22:01] <robotfuel> kgunn: do you know who else I can ask about landing my MP for platform-api? https://code.launchpad.net/~chris.gagnon/platform-api/get_coverage_in_ci/+merge/213533
[22:04] <slangasek> sergiusens: is this something I could ask you to review? https://code.launchpad.net/~vorlon/phablet-tools/checkbashisms/+merge/213556
[22:04]  * sergiusens looks
[22:05]  * Saviq considers slangasek's LP handle quite badass everytime he sees it
[22:06] <sergiusens> slangasek: I'm not sure how it got in; it's checked on package build... that said, I think barry already fixed this
[22:06] <Saviq> OTOH /me imagines Vogons every time, too
[22:06] <sergiusens> but your solution is an improvement it seems
[22:07] <barry> sergiusens, slangasek: well, kind of.  the branch is approved and passes ci, but not merged afaict: https://code.launchpad.net/~barry/phablet-tools/lp1298550/+merge/213131
[22:08] <barry> sergiusens: why not try to land it? :)
[22:09] <sergiusens> barry: yeah, I might want to land both of slangasek's MRs as well; mind if we just use his bashism fix and you revert yours?
[22:10] <barry> sergiusens: as long as it gets fixes, that's cool with me
[22:30] <sergiusens> barry: just revert the bashisms; and I'll request the silo right after ;-)
[23:24] <kgunn> robotfuel: just to let you know i added a landing line...
[23:26] <kgunn> robotfuel: ah...kept forgeting which channel we were in...so i gotta talk someone into a silo, but i think i can land it
[23:27] <kgunn> robotfuel: i assume its a "make sure it doesn't break" test...since there's no real way to test it, other than ci