[01:14] <mterry> robert_ancell, I have another patch I'd like to squeeze into lightdm.  This time having it search XDG_DATA_DIRS for config info (to let OEM team customize image)
[01:14] <mterry> whoops, not here
[01:25] <SparkyFlary> is it possible to put ubuntu touch on my samsung galaxy temporarily?
[01:25] <SparkyFlary> like a live cd sort of way?
[07:43] <anil> Hii .. I have compiled phablet kernel with Framebuffer console ..
[07:43] <anil> the nexus 10 is not coming up with new kernel
[07:43] <anil> to enable framebufffer console what it require apart from enabling framebuffer console in .config
[08:04] <asac> stgraber: there?
[08:04] <asac> stgraber: seems our iamges dont work in infra anyumore (e.g. dont install()
[08:04] <asac> stgraber: have you pipecleaned the system-image  update as i suggested yestetrday?
[08:06] <asac> ogra_: ^^
[08:06] <asac> help :)
[09:16] <tsdgeos> so is phablet-flash finally unsupported?
[09:17] <asac> tsdgeos: no updates are distributed for a while already
[09:17] <asac> tsdgeos: dont ask me why we didnt provide a compatibilty link :)
[09:17] <tsdgeos> asac: ?¿ i used it yesterday and got me two different images at least
[09:17] <asac> tsdgeos: yeah, the new one is ubuntu-device-flash :)
[09:18] <asac> hwoveer, i would have preferred to just keep shipping the phablet-flash command
[09:18] <asac> as well
[09:18] <tsdgeos> the command is here
[09:18] <tsdgeos> it just doesn't work
[09:19] <ogra_> asac, stgraber discussed it with plars and doanac` last night, they even shared code for a fix
[09:19] <ogra_> not sure why that didnt lnad
[09:19] <ogra_> *land
[09:22] <asac> ogra_: i think something landed
[09:22] <asac> ogra_: but noone reran the jobs?
[09:22] <asac> e.g. we offlined the device
[09:22] <asac> and now its working
[09:22] <ogra_> ah, k
[09:22] <asac> anyway, discussed was that if there is an issue we revert
[09:22] <asac> because CI team is all into something customer
[09:22] <ogra_> we had three builds this night, intresting that nobody noticed it over three images :/
[09:23] <asac> ogra_: noone is there
[09:23] <asac> hence i wanted it to be reverted if something doesnt go well
[09:23] <ogra_> they wre ehere to discuss about it
[09:23] <asac> they are all on-site somewhere
[09:23] <asac> ogra_: yes, but they were in constant firedrill mode for something else
[09:23] <ogra_> reverting isnt done easily
[09:23] <asac> well, i asked if we could revert before doing it
[09:23] <asac> i didnt hear a NO
[09:24] <ogra_> right, but you need stgraber to do it
[09:24] <asac> right, hence i asked stgraber and you to pipeclean and if anything goes bad revert right away
[09:24] <asac> i am not asking these things for fun :)
[09:24] <asac> anyway
[09:24] <asac> </endcomplain
[09:24] <asac> >
[09:25] <asac> also not to you reall
[09:38] <JamesTait> Good morning all; happy Biodiesel Day! :-D
[09:52] <sil2100> alecu: ping
[09:59] <nerochiaro> hey everyone, i'm trying to get multitouch working on desktop via a magic touchpad. unity seems to get the 3- and 4-finger tap gestures to show dash and window switcher, but i can't do multifinger swipes or pinches. any idea where i should start looking ?
[10:13] <ogra_> nerochiaro, i think #ubuntu-x is the better place for this
[10:17] <nerochiaro> ogra_: ok, thanks
[10:17] <ogra_> popey, am i blind or is our topic gone ?
[10:17] <popey> i see it
[10:17] <ogra_> (is is my client messed up
[10:17] <ogra_> )
[10:18] <ogra_> aha, k
[10:18] <ogra_> silly focus issues on 12.04
[11:03] <davmor2> Morning all
[11:40] <bzoltan1> cjwatson: Hellor,  do you know when the 0.4.19 click will land?
[11:40] <cjwatson> bzoltan1: hopefully today - I want to sort out https://code.launchpad.net/~mardy/click/lp1245826/+merge/204674 first
[11:41] <cjwatson> if that looks like it's taking too long I'll try to land click first
[11:42] <bzoltan1> cjwatson: I wold be happy to see it as soon as possible... we have a fix for the click chroot cmake problem and that needs a healthy chroot.
[11:42] <cjwatson> bzoltan1: your comment on that MP implies that you are creating ubuntu-sdk-13.10 chroots using trusty, which is extremely worrying.  please stop
[11:42] <cjwatson> if you create them using saucy you shouldn't have this problem
[11:43] <cjwatson> (https://code.launchpad.net/~xnox/click/v8-is-gone/+merge/211485)
[11:43] <bzoltan1> cjwatson: one can not create saucy chroot either due to an other problem
[11:43] <cjwatson> what problem is that?
[11:43] <bzoltan1> cjwatson: it fails ... i do not have the logs in hand
[11:43] <cjwatson> we should fix that separately
[11:43] <bzoltan1> cjwatson: just try click chroot -a armhf -s saucy create
[11:43] <cjwatson> my internet is very slow
[11:44] <bzoltan1> cjwatson: let me produce the logs then
[11:44] <cjwatson> it would be most helpful if somebody with more than 2Mb/s could try it
[11:45] <cjwatson> [also, the correct invocation is click chroot -a armhf -f ubuntu-sdk-13.10.  the -s option is really only for debugging]
[11:46] <cjwatson> in particular if you leave out -f then you'll get different results once click chroot's default framework changes
[11:47] <cjwatson> which will have to happen at some point soonish
[11:47] <bzoltan1> cjwatson: OK, I will use only the arch and the fw
[11:49] <bzoltan1> cjwatson: http://pastebin.ubuntu.com/7113628/
[11:50] <cjwatson> hm, interesting
[11:50] <cjwatson> thanks, I'll see if I can disentangle that somehow
[11:52] <bzoltan1> cjwatson: that might ease some pain
[11:53] <cjwatson> the cross toolchains are a bit delicate
[11:55] <bzoltan1> :) that is a rather mild statement
[11:56] <cjwatson> I have been infected by the British habit of understatement
[11:57] <janimo`> ogra_, any idea why between the last two promoted images (Feb 20  and Mar 14) adbd would no longer start and the device seems offline? I see the mtp server config file had been added, you did some adbd/ssh work, but any other clues are helpful
[11:57] <janimo`> ogra_, this is not a nexus device
[11:57] <ogra_> janimo`, adb was moved to start after the container
[11:58] <ogra_> to prevent the numerous disconnect issues we had when it gets dynamically reconfigured all the time
[11:58] <janimo`> ogra_, but once unity8 is up and working, adbs should also be ready right? I have a GUI just device offline from adb
[11:59] <ogra_> (we leave the whole configuration to android now and only run the adbd on the ubuntu side, that saves from getting like 1000 popups on your desktop and about 4 reconnects, which breaks automation in various places)
[11:59] <bzoltan1> cjwatson: well, it is better than being born with the continuously exaggerative Hungarian habit
[11:59] <ogra_> janimo`, yeah, it should just come up
[12:00] <ogra_> mtp should not have any influence
[12:01] <ogra_> janimo`, could it be that your android container misses the forcing of the persistent property for adb/mtp in init.rc ?
[12:02] <ogra_> # adb force hack
[12:02] <ogra_>     setprop persist.sys.usb.config mtp,adb
[12:02] <ogra_> your init.rc should have this one
[12:04] <JamesTait> Regarding https://bugs.launchpad.net/touch-preview-images/+bug/1293797 can someone tell me what service the device contacts to check for updates?
[12:05] <JamesTait> Click package updates, that is.
[12:05]  * ogra_ sighs, why do poeople not file bugs against the packages
[12:06] <ogra_> JamesTait, i think beuno might know
[12:06] <ogra_> (they should query the store server)
[12:07] <beuno> JamesTait, click index, yes
[12:07] <beuno> JamesTait, it sends a list of packages it has, and the server replies with what's on the server, and the client compares
[12:07] <beuno> IIRC
[12:07] <beuno> alecu knows the details
[12:08] <JamesTait> Ah, it's querying click index?  Interesting.
[12:09] <JamesTait> Hm, I don't recall writing any code that accepts a list of packages. :-/
[12:15] <beuno> JamesTait, I forget who did, maybe it was pindonga?
[12:15] <davmor2> JamesTait: I can answer that bug, they are on the 14.04-dev version to make them work for the QT5.2.1 version so they shouldn't install on a system that isn't on QT5.2.1
[12:16] <JamesTait> beuno, I thought so, but he wasn't that sure - I think we've figured out what the problem is now though.
[12:16] <beuno> cool cool
[12:16] <JamesTait> davmor2, at a high level, yes. :)
[12:28] <cjwatson> bzoltan1: OK, I think I've fixed saucy chroot creation - testing that (sloooowly) and then I'll see about a landing
[12:29] <bzoltan1> cjwatson: is there anything I can test?
[12:29] <cjwatson> (it needed a dist-upgrade of the chroot before trying to install the cross-compiler etc.)
[12:29] <cjwatson> bzoltan1: you can grab lp:click, do debian/rules build, then sudo ./run-click chroot -a armhf -f ubuntu-sdk-13.10 create
[12:29] <bzoltan1> cjwatson: Ohh... that one. Super
[12:30] <cjwatson> also fixed an embarrassing bug where we weren't actually suppressing daemon startup in the chroot as was always intended
[12:31] <cjwatson> which I confidently asserted in some UDS session worked fine :)
[12:32] <cjwatson> bzoltan1: going out to do some admin, hopefully my test will have finished by the time I get back
[12:32] <janimo`> cjwatson, hi, is the click frontend going to be rewritten in Vala at one point too?
[12:33] <ogra_> ugh
[12:33] <ogra_> janimo`, i thought C all the way :)
[12:33] <bzoltan1> cjwatson:  Thanks a lot. I am testing...
[12:33] <janimo`> ogra_, well seeing the libclick is in Vala...
[12:33] <janimo`> ogra_, which is C after all
[12:46] <bzoltan1> cjwatson: I could create an armhf chroot with ubuntu-sdk-13.10 fw without any trouble. Thank you.
[12:53] <zbenjamin> cjwatson: how will the new splitted frameworks actually work. Will you need a own chroot for -html, -qml, -papi?
[12:53] <zbenjamin> cjwatson: or will a 14.04 framework just support all of them
[12:53] <zbenjamin> erm chroot i mean
[13:25] <Saviq> is anyone else's flo turning off after some idle time?
[13:25] <Saviq> it's the umpteenth time I thought it discharged, but it's fully charged... just turned off
[13:26] <rsalveti> Saviq: hm, a kernel crash would probably reboot it
[13:26] <Saviq> rsalveti, not reboot
[13:27] <Saviq> rsalveti, it powers off
[13:27] <rsalveti> Saviq: just noticed mine did the same
[13:27] <rsalveti> was completely off here
[13:27] <Saviq> unless my cats are having fun with me, this is crazy
[13:27] <ogra_> Saviq, i noticed it too, but it didnt happen for a while now
[13:27] <ogra_> Saviq, was your device wired up ?
[13:27] <Saviq> rsalveti, ogra_, sounds like a broken deep sleep mode or something
[13:27] <Saviq> ogra_, no
[13:27] <rsalveti> nothing changed in the kernel side
[13:28] <ogra_> rsalveti, i noticed it randomly since i run flo
[13:28] <sergiusens> Saviq, yes; rsalveti I thought I told you about that one
[13:28] <ogra_> but it only seemed to happen to me when the device was kept wired over night
[13:28] <ogra_> havent seen it in over a week now
[13:29] <ogra_> (and i didnt have to charge in over a week either !!!)
[13:29] <Saviq> ogra_, maybe it did power off, then ;)
[13:29] <ogra_> Saviq, because it was finished charging ?
[13:29] <ogra_> :P
[13:29] <Saviq> ogra_, no idea, something like that
[13:29]  * Saviq files a bug
[13:30] <cjwatson> janimo`: I'm thinking about it at some point, but (a) I want "click build" to remain pure-Python for portability, (b) the performance-sensitive paths should all be rewritten to use libclick rather than fork/exec anyway
[13:30] <cjwatson> bzoltan1: great, thanks
[13:30] <rsalveti> bq27541_get_psp temperature was quite high in my syslog
[13:30] <ogra_> it definitely drains significantly less power than all other devices i have
[13:30] <rsalveti> before it decided to shutdown
[13:30] <robotfuel> sergiusens: ping, ubuntu-device-flash reboots my maguro in to recovery mode, it doesn't flash my phone like phablet-flash did. is there a flag I am missing?
[13:30] <ogra_> rsalveti, add a fan then :P
[13:30] <rsalveti> ogra_: and it also finished charning
[13:30] <rsalveti> *charging
[13:30] <bzoltan1> cjwatson:  is there a simple way to ask from a click chroot what frameworks are available
[13:30] <bzoltan1> ?
[13:31] <cjwatson> zbenjamin: I'm open to feedback on that; I suspect it will generally be more convenient to have a single chroot, and have the ABIs enforced by other things like the review tools.  What do you think?
[13:31] <sergiusens> robotfuel, what are you trying to do?
[13:31] <rsalveti> bq27541_get_capacity = 0% ret= 0
[13:31] <rsalveti> bq27541_get_psp temperature= 349
[13:31] <ogra_> wow
[13:31] <cjwatson> bzoltan1: No, it's a bit light on query interfaces right now.  Suggest an interface, maybe?
[13:31] <robotfuel> sergiusens: flash the phone automatically like phablet-flash did. all of the phones in ci are broken, because they are still trying to use the phablet flash command.
[13:31] <ogra_> is that in farenheit ?
[13:32] <rsalveti> Saviq: check yours as well
[13:32] <rsalveti> ogra_: might not be in any scale we know
[13:32] <davmor2> robotfuel: maguro isn't supported passed the 4.4.2 android update
[13:32] <ogra_> yeah
[13:32] <mterry> tedg, what's the bug # for that FFe for indicator-sound?
[13:33] <sergiusens> robotfuel, ubuntu-device-flash --wipe channel trusty-proposed ... like that?
[13:33] <rsalveti> ogra_: actually, bq27541_get_capacity = 0 means it was completely out of battery
[13:33] <robotfuel> sergiusens: yes, I have a maguro which is probably the issue
[13:33] <tedg> mterry, bug 1293677
[13:33] <ogra_> rsalveti, yeah, but the 349 $whatever for the temp are weird
[13:34] <Saviq> rsalveti, 250...260, doesn't get much higher
[13:34] <sergiusens> robotfuel, I don't think the phablet-flash being broken is related to ubuntu-device-flash
[13:34] <sergiusens> robotfuel, I don't think there's devel-proposed avail for maguro anymore
[13:34] <robotfuel> sergiusens: phablet-flash looks for a json file that does not exist on the server anymore
[13:34] <bzoltan1> cjwatson: I will figure out something. For now I will rely on the name of the chroot
[13:34] <rsalveti> sergiusens: we should have it still
[13:35] <sergiusens> robotfuel, for that, do --channel ubuntu-touch/devel-proposed
[13:35] <sergiusens> rsalveti, it's just that robotfuel is mixing up two problems
[13:36] <ogra_> there are still both channels for maguro ... but devel/trusty only has 188 as the last promoted image
[13:36] <ogra_> (and we dont promote any for it anymore)
[13:36] <sergiusens> rsalveti, yeah maguro is there;
[13:36] <Saviq> ogra_, rsalveti bug #1294130
[13:37] <ogra_> Saviq, thx
[13:37] <rsalveti> Saviq: can you add your /var/log/syslog in there?
[13:37] <Saviq> rsalveti, sure, but I've rebooted twice since
[13:37] <Saviq> rsalveti, dmesg.?
[13:37] <rsalveti> Saviq: no worries
[13:37] <rsalveti> Saviq: want the messages before it went off
[13:38] <rsalveti> Saviq: you should have it unless you flashed your device
[13:38] <sergiusens> robotfuel, and the full descriptions for ubuntu-device-flash and installation should be in the wiki
[13:38] <Saviq> 47MBs syslog - sure, it'll be there...
[13:39] <rsalveti> ouch, but gzip should help quite a lot
[13:39] <sergiusens> robotfuel, https://wiki.ubuntu.com/Touch/Install#Step_4_-_Downloading_.26_Deploying_Image_to_Device
[13:40] <Saviq> rsalveti, https://bugs.launchpad.net/ubuntu/+source/android/+bug/1294130/comments/1
[13:40] <rsalveti> Saviq: thanks
[13:52] <stgraber> asac: hmm, so on my side everything went well including the end to end tests on devices here. As for QA, my understanding was that sergiusens figured out that they were using broken code ahead of time and provided a fix, I wasn't told of any problem...
[13:53]  * stgraber continues to read backscroll
[13:54] <hedz09> ogra_: hey ogra, thanks for the help yesterday. I followed the instructions to prepare the ubuntu touch filesystem and got the following when booting up:     4.258965] init: Failed to bind socket 'property_service': No such file or directory [    4.268258] init: init startup failure [    4.272900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 . Does anyone have thoughts on what's going on?
[13:54] <sergiusens> stgraber, so after a couple I recalled that ci used the device specific channel's json to figure out if there was a new build available; that spanned into a couple of branches that needed updates
[13:54] <ogra_> stgraber, all fine
[13:55] <stgraber> oh, ok, because they also used the hardcoded URLs instead of parsing channels.json...
[13:55] <sergiusens> stgraber, I'm going to see if I can provide an alternative for them; exactly
[13:55] <sergiusens> stgraber, seems they were confused as I was by the definition of 'links' where we thought they were at the file layout level :)
[13:56] <sergiusens> as in ln -s ubuntu-touch/saucy saucy
[13:56] <stgraber> well, at least with that change we managed to spot all the tools that aren't spec-compliant in one go ;)
[13:57] <zbenjamin> cjwatson: yes single chroot sounds way better
[13:57] <cjwatson> zbenjamin: yeah, I think otherwise we end up creating a combinatorial explosion of chroots, it sounds weird
[13:58] <sergiusens> stgraber, agreed;
[13:58] <zbenjamin> cjwatson: completely agree, thats exactly why i'm asking because each chroot will be a own target in creator, that would be totally confusing :)
[13:59] <janimo`> ogra_, found the adbd issue. The change in the init script to not poke sysfs much but use the functionfs mount broke it here
[13:59] <cjwatson> zbenjamin: feel free to play with lp:click r403, which is what I'm trying to get landed now
[13:59] <janimo`> apparently that other branch of code was not preserved at all. This device has functionfs but since I first heard of it today I'll need to see why it does not behave
[13:59] <zbenjamin> cjwatson: ok
[14:00] <ogra_> janimo`, oh ? do you have a device with functionfs ?
[14:00] <janimo`> ogra_, well, mount -t functionfs did mount something and that f_ffs entry is there in syslog so I guess
[14:01] <janimo`> as I said I do not know what fs this is or what exactly that init script change was meant to fix
[14:01] <ogra_> janimo`, and your android doesnt configure functionfs for the gadget ?=
[14:01] <janimo`> ogra_, I need to dig into that. I tested the functionfs mount in recovery mode. In ubuntu boot mode I cannot adb shell in
[14:01] <ogra_> janimo`, its like "a unionfs to make the gadget device have more than two functions"
[14:02] <ogra_> usually g_android can only handle two functions
[14:02] <janimo`> ogra_, I may be missing some kernel config options or it's just something not tested much in this kernel. Does android use this?
[14:02] <ogra_> the functionfs extends that
[14:02] <ogra_> you should see it being handled in init.$device.usb.rc
[14:03] <ogra_> *if* your device supports it
[14:03] <janimo`> ogra_, for now I'll override that script with the old version in our rootfs so we can test recent images, but I need to find the cause
[14:03] <sergiusens> robotfuel, just show me the code/script branch and I'll propose an MR
[14:03] <ogra_> worst case just drop it from the kernel
[14:03] <ogra_> we dont even support more functions than adb and mtp yet
[14:04] <janimo`> ogra_, do I need extra stuff in init scripts? I just diffed the two ubuntu image fss and this is how I found the change. If you have a pointer to a bug or changelog for this change which may touch other files that would be good :)
[14:04] <ogra_> no, we dont have a bug for it
[14:04] <ogra_> changelog entry should be in android-tools-adbd
[14:04] <ogra_> iirc
[14:05] <ogra_> janimo`, http://paste.ubuntu.com/7114228/
[14:06] <janimo`> ogra_, thanks. So on devices where there's no fgunctionfs is the old codepath not needed either?
[14:06] <ogra_> right
[14:06] <janimo`> those commands poking sysfs/andoird
[14:06] <robotfuel> sergiusens: they are using phablet-flash in a job, pinky is going on site to switch to ubuntu-device-flash, in case something goes wrong.
[14:07] <ogra_> janimo`, we wait for the container to have it configured before we start adbd so the sysfs hacks arent needed anymore ... what *is* needed is the line in init.rc that forces the persist property
[14:07] <robotfuel> sergiusens: ubuntu-device-flash reboots my phone to the recovery screen, but doesn't flash it. I am using a maguro.
[14:07] <sergiusens> robotfuel, you can still use phablet-flash for the time being
[14:07] <sergiusens> robotfuel, just change the channel to ubuntu-touch/devel-proposed
[14:07] <groggster> Hello! I am looking for the kernel sources for 3.0.0.3-maguro for building a kernel module. Where are they, and do I have to do something special to my Ubuntu touch phone in order to build and use kernel modules?
[14:07] <robotfuel> sergiusens: yes, we just tested your changing the channel and it works :)
[14:08] <sergiusens> robotfuel, afaik, your box is on raring; I would wait for the switch to saucy
[14:08] <robotfuel> cjohnston: ^^
[14:09] <sergiusens> robotfuel, that was what we discussed with plars and doanac` fwiw
[14:09] <cjohnston> yup
[14:09] <plars> sergiusens, robotfuel: that's happening this friday
[14:14] <robotfuel> sergiusens: I opened a ubuntu-device-flash bug  https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1293937 who do I ping to triage?
[14:15] <sergiusens> robotfuel, that already has an MR which I asked mandel to review
[14:16] <robotfuel> sergiusens: ok thanks
[14:25] <hedz09> ogra_:  Do you have any thoughts on the error? I haven't been able to find anything.
[14:26] <ogra_> hedz09, not really, thats just the last line ... the error is most likely somewhere before
[14:28] <barry> ogra_: is `ubuntu-device-flash --revision -1` broken?  (channel trusty-proposed)
[14:30] <hedz09> ogra_:hmm, ok. Thanks.
[14:30] <ogra_> barry, ask sergiusens  .... thats his baby :)
[14:30] <barry> ogra_: ack :)
[14:31] <barry> sergiusens: so, without --revision -1, image 243 gets installed.  but s-i.u.c seems to have image 242
[14:31] <barry> % ubuntu-device-flash --channel=trusty-proposed --revision -1 --bootstrap
[14:31] <barry> 2014/03/18 10:27:14 Expecting the device to be in the bootloader... waiting
[14:31] <barry> 2014/03/18 10:27:14 Device is |manta|
[14:31] <barry> 2014/03/18 10:27:16 Failed to locate image -1
[14:31] <barry>  
[14:32] <sergiusens> barry, yeah; there's an mr for that
[14:32] <popey> barry: command line help says "--revision=" not --revision<blank>
[14:32] <popey> ?
[14:32] <barry> popey: nope.  `--revision -1` also fails (but cli should accept both)
[14:32] <popey> ☹
[14:33] <sergiusens> barry, popey yeah, cli works with both; relative versions against latest need a merge
[14:33] <barry> sergiusens: ack.  thanks, i'll use an absolute number for now
[14:34] <sergiusens> barry, should land today; getting reviewers is what takes time :-)
[14:34] <sergiusens> popey, care to take a look https://code.launchpad.net/~sergiusens/goget-ubuntu-touch/relative/+merge/211523
[14:34] <popey> hah, saw that coming
[14:35] <popey> i can test at the moment, i dont want to flash my devices
[14:36] <sergiusens> popey, just see that it start downloading ;-)
[14:38] <popey> ack
[14:59] <om26er> sergiusens, hey! do you know why I am seeing this error when doing click setup ? http://paste.ubuntu.com/7114344/
[15:00] <sergiusens> om26er, you are not using unity8 from trunk is my guess
[15:00] <om26er> sergiusens, its the latest unity that comes on the image
[15:02] <sergiusens> om26er, which version; I'll flash and check
[15:03] <om26er> sergiusens, its the very latest image 243
[15:03] <sergiusens> om26er, need to look at the latest unity8, maybe something changed there
[15:03] <om26er> sergiusens, so the problem was I did not had ubuntu-dev-tools installed due to some reason
[15:03] <om26er> which provides pull-lp-source
[15:03] <om26er> I remember installing phablet-tools with --no-install-recommends that's probably the reason
[15:04] <sergiusens> oh
[15:04] <ogra_> wow, why ?
[15:05] <Tassadar> stgraber: hi, I'd want to add that ubuntu-touch "flavour" (is that what you call it?) to my server too - are all the code changes required on launchpad already?
[15:06] <stgraber> Tassadar: yep, the production server is running the branch as it is on Launchpad, I can copy/paste you the si-shell commands I did yesterday to do the change
[15:06] <Tassadar> yeah, that would be nice, thanks
[15:07] <hedz09> ogra_:  here's the full log: http://pastebin.com/ass2A2ws
[15:09] <ogra_> hedz09, that looks very much like you are booting into android
[15:09] <ogra_> instead of into ubuntu
[15:09] <Tassadar> stgraber: also, I suppose it should be fine to add flavor as option when selecting the image to my app (it currently has "channel" and "version", but the channel names are bit too long right now). That would require for the naming schema to be consistent, like there can only be just one slash in the channel name, dividing the flavor name and channel name. Is that what you plan to do?
[15:11] <stgraber> for channel in pub.list_channels().keys():
[15:11] <stgraber>     pub.rename_channel(channel, "ubuntu-touch/%s" % channel)
[15:11] <stgraber>     pub.create_channel_redirect(channel, "ubuntu-touch/%s" % channel)
[15:11] <stgraber>     if "alias" in pub.list_channels()["ubuntu-touch/%s" % channel]:
[15:11] <stgraber>         pub.change_channel_alias("ubuntu-touch/%s" % channel,
[15:11] <stgraber>                                  "ubuntu-touch/%s" % pub.list_channels()["ubuntu-touch/%s" % channel]['alias'])
[15:11] <stgraber> Tassadar: that should do the trick ^
[15:12] <stgraber> Tassadar: in theory we could add more sub-directories in the path but I can't think of a good reason to do that at the moment, so just splitting on / should be fine for now
[15:12] <hedz09> ogra_: I put the contents of out/target/product/root  on my root partition. Are these the wrong ramdisk files?
[15:12] <Tassadar> stgraber: okay, thanks. I'll make it work correctly even when there is more than one slash then
[15:12] <ogra_> hedz09, you want the contents of the tarball in your root partition
[15:13] <ogra_> hedz09, (the ubuntu rootfs)
[15:13] <ogra_> well, in fact you want a file called system.img in /userdata/ with the rootfs in it
[15:14] <ogra_> like rootstock creates
[15:14] <ogra_> (the initrd will find it and mount it as /)
[15:17] <hedz09> ogra_: my current setup is: root partition contains root, /userdata/ has the system.img with the ubuntu rootfs and android-ramdisk in it. From what you're saying it seems that my root partition is incorrect. Which initrd do I put on my root partiton (if the userdata partition contains the ubuntu rootfs in system.img)
[15:18] <Tassadar> how can I look at the last commit in bzr, like git show
[15:18] <ogra_> hedz09, you root partition should only contain /userdata
[15:19] <cjwatson> Tassadar: bzr log -p -rlast:
[15:19] <cjwatson> Tassadar: I use   bzr alias show="log -v -p -n1 --long"
[15:19] <Tassadar> thanks, I'll add that too
[15:19] <cjwatson> so that "bzr show -rlast:" works
[15:22] <hedz09> ogra_: ok. I'm using a prebuilt kernel so my build doesn't make a boot.img so I have to make it myself. What ramdisk should be packaged with it?
[15:25] <Tassadar> bzr is a bit...different from git which I'm used to. And now I have a merge conflict, guess I'll have to learn how to merge properly in bzr :x
[15:29] <ogra_> hedz09, ah, you should have an ubuntu-ramdisk file in your build dir that was downloaded during build
[15:29] <Tassadar> oh, when I merge with some other branch in bzr, I don't get history from that branch into my tree, that's unusual
[15:32] <hedz09> ogra_: I have android-ramdisk.img and ramdisk.img. The ramdisk.img has init as  a shell script -- is this right?
[15:33] <ogra_> yes
[15:34] <rsalveti> ogra_: file adbd
[15:34] <rsalveti> adbd: ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=dd06a054f09b70ae16fc2637a9ca78d22c0e9a20, stripped
[15:35] <ogra_> rsalveti, hmm
[15:35] <ogra_> then it should start for him as well
[15:36] <ogra_> rsalveti, could you give him a binary initrd ?
[15:36] <rsalveti> ubuntu/ubuntu-touch-generic-initrd/usr/lib/ubuntu-touch-generic-initrd/initrd.img-touch
[15:36] <rsalveti> just need to grab that one from the package itself
[15:36] <rsalveti> ubuntu-touch-generic-initrd
[15:37] <rsalveti> same as I do for the x86 emulator image
[15:37] <ogra_> oh, we build it for x86 ?
[15:37] <hedz09> ogra_: I tried using this before and the kernel couldn't find /init :  [ 2.903520] Failed to execute /init.  Attempting defaults... [ 2.913137] Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
[15:37] <ogra_> i thought we didnt
[15:37] <rsalveti> ogra_: we build it now ;-)
[15:37] <rsalveti> had to change to support x86
[15:37] <ogra_> hedz09, then your initrd is broken ... it does all the mounting of the rootfs before swtiching to init
[15:37] <ogra_> rsalveti, ah, that was the missing bit :)
[15:37] <rsalveti> yeah, I'd guess that the data partition is not mounted
[15:38] <ogra_> hedz09, you do *not* unpack the ramdisk anywhere
[15:39] <ogra_> it needs to come from the boot.img (or your u-boot setup needs to load it from somewhere)
[15:41] <ogra_> hedz09, looking at http://pastebin.com/ass2A2ws you never load the initrd
[15:42] <ogra_> find out how to configure your u-boot in a way that it loads it
[15:42] <ogra_> and put the img file next to your zImage
[15:43] <ogra_> i guess the guys in #beagle can help pointing you to docs worst case
[15:43] <popey> davmor2: I fiddled with the nexus sheet formatting because a user showed me a screenshot showing it to be hard to read on windows ⍨
[15:44] <ogra_> just ask him to install ubuntu in a VM :P
[15:44] <popey> :D
[15:45] <ogra_> or add: "windows is deprecated, please use a modern OS like Ubuntu" at the top of the sheet ;)
[15:45] <davmor2> haha
[15:45] <t1mp> is the "unlock sim" dialog kind of broken in image 244?
[15:45] <tester4711> Hi, quick question: how can i restart unity8 in the emulator manually?
[15:45] <t1mp> it reacts very slow.. so slow that I cannot properly enter the pin
[15:46] <t1mp> and then it just dies before I click done
[15:46] <ogra_> t1mp, 243 had some bad Mir issues, not sure that already got reverted properly in 244
[15:46] <cwayne> tester4711: adb shell; sudo -iu phablet initctl restart unity8
[15:47] <t1mp> ogra_: okay. could be mir also, I haven't tried much else besides the unlock sim yet
[15:47] <ogra_> t1mp, start the system-settings ... if it stays white until you touch the screen, thats the issue
[15:47] <cwayne> rsalveti: when will the x86 emulator be released?
[15:47] <hedz09> ogra_: I've been following TI's Android image for the structure. In hindsight this was a bad route. For their Android image, they make a boot, rootfs and userdata partition. Boot has u-boot.img, MLO, zImage, uEnv.txt unpacked. Rootfs has the ramdisk unpacked as well as the contents of system (uEnv.txt passes an argument to the kernel to indicate this as the root partition). I was able to build CM and construct a similar struct
[15:47] <cjwatson> Tassadar: yeah you do, at least after you commit
[15:48] <cjwatson> Tassadar: you might want to use bzr log -n0 to see the merged history
[15:48] <rsalveti> cwayne: when it's done :P
[15:48] <tester4711> @cwayne: thx.
[15:48] <hedz09> ogra_: uEnv also passes to the kernel the location of the init binary
[15:48] <ogra_> hedz09, yeah, bad idea ... load the initrd from u-boot, have a system.img in /userdata on your root partition and you should boot into ubuntu
[15:49] <ogra_> you shouldnt need to pass the init= arg
[15:49] <cwayne> rsalveti: :D
[15:49] <rsalveti> cwayne: working on it, should have more news later this week
[15:49] <Tassadar> cjwatson: what happens to the revision numbers then? do they change?
[15:49] <ogra_> the kernel usually looks in known places anyway
[15:49] <ogra_> (/sbin/init and /init at least)
[15:49] <t1mp> ogra_: yes, system settings stays white
[15:49] <cjwatson> Tassadar: revision ids stay the same; revision numbers depend on the branch you're on
[15:49] <cjwatson> (--show-ids to see the ids)
[15:50] <ogra_> t1mp, then blame Mir for the PIN stuff too i guess ... see if it works on 241 or 242
[15:52] <hedz09> ogra_: ok, so on my boot partition I should put initrd (just ensuring I understand this correctly so I can move away from what TI did)
[15:53] <ogra_> you should put the initrd and change your u-boot configuration to load it
[15:55] <hedz09> ogra_:  put initrd where, sorry?
[15:55] <ogra_> next to the zImage file ... wherever that lives
[15:56] <ogra_> (most likely a vfat boot partition)
[15:56] <ogra_> (and no, i dont know what you need to change for u-boot to make it load it ... you will have to find out yourself)
[15:57] <hedz09> ogra_: ok, I'll look into it. Thanks for the help.
[16:03] <mterry> ogra_, what branches did you have on your machine when you made that boot animation video?
[16:03] <ogra_> mterry, only https://code.launchpad.net/~unity-team/unity-system-compositor/new-gl-screen/+merge/210466
[16:04] <mterry> ogra_, huh, OK.  I didn't see much of a black screen in between the animation and the greeter
[16:04] <ogra_> yeah
[16:04] <ogra_> it works pretty nice
[16:14] <bfiller> rsalveti, Mirv: I thought qtmultimedia in Qt5.2 depended on gstreamer1.0 and not 0.10. But seems libqt5multimedia5-plugins still depends on libgstreamer0.10-0
[16:14] <rsalveti> bfiller: just qtmultimedia-touch depends on gst1.0
[16:14] <rsalveti> bfiller: the original one is still depending on gst0.10
[16:15] <bfiller> rsalveti: even for 5.2?
[16:15] <rsalveti> yes
[16:15] <bfiller> rsalveti: so for touch apps on the desktop this poses a problem I guess
[16:16] <rsalveti> bfiller: it's a problem if you're using qtmultimedia and gst in the same app
[16:16] <bfiller> rsalveti: right
[16:17] <bfiller> rsalveti: I guess as long as we just use qtmultimedia and not gst directly we should be ok
[16:17] <rsalveti> bfiller: yes
[16:17] <bfiller> rsalveti: but gstreamer0.10 will get pulled into the desktop based on qtmultimedia which should be ok
[16:17] <rsalveti> yeah
[16:17] <bfiller> should be ok then
[16:18] <bfiller> rsalveti: as long as scene selector in media player can be done someway without directly using gstreamer
[16:18] <bfiller> as that's not part of qtmultimedia currently
[16:18] <rsalveti> bfiller: afaik that will be done with the mediahub
[16:19] <bfiller> rsalveti: will mediahub run on desktop?
[16:19] <rsalveti> bfiller: I belive so, that's part of our convergence plan anyway
[16:27] <timppa> latest image seems to be very slow opening apps
[16:27] <timppa> and many apps don't open at all
[16:31] <cjwatson> timppa: apparently being investigated, https://bugs.launchpad.net/mir/+bug/1294051 https://bugs.launchpad.net/mir/+bug/1294053
[16:32] <timppa> cjwatson: ok, great
[16:33] <timppa> geoclue-and-gypsy package was on the changelog, has it been implemented in what way? Can I use it from Qt app?
[16:40] <tyzeffffff> hi guys, i am french guy from maldive, nice no? lol! ok seriously i am linux lover from 2007 with festy fawn 7.04. then this days i used to on a gt-i9070uncle'sam change my android stock for cyano11 bug a bit then now went on cm10.2... then? then i saw that it may possible to install ubuntu touch on my device samsung s advance gt-i9070... and this can help ubuntu if i report bugs... then i like this way but don't know if i
[16:40] <tyzeffffff> big thank and sorry for this little roman
[16:43] <t1mp> !devices | tyzeffffff
[16:43] <tyzeffffff> any advice please cause i can't properly articles to explane if that's possible to install ubuntu touch on my samsung
[16:43] <tyzeffffff> oh thank t1mp
[16:45] <tyzeffffff> yes t1mp i went to this article but not so clear for me to understand what can i do for my phone...
[16:45] <t1mp> tyzeffffff: I don't see at-i9070 (I don't know what that is) listed on that page, so there is no port yet
[16:46] <t1mp> unless the device is one of those in the list, you would have to port it yourself
[16:47] <t1mp> I don't know how to do that. There is a guide here https://wiki.ubuntu.com/Touch/Porting but it won't be easy I think
[16:49] <tyzeffffff> t1mp well thank you i think just to wait for some times and see if later...
[16:50] <cjwatson> timppa: the geoclue-gypsy change was just me prodding at multiarch metadata
[16:50] <t1mp> tyzeffffff: yeah. It seems maldives is not the worst place to be waiting :)
[16:50] <cjwatson> timppa: in an attempt to simplify click chroot
[16:52] <tyzeffffff> t1mp lol, big joke i just got!!! yes that true nice to be patient here!
[16:53] <timppa> cjwatson: ok, I had high hopes on that :D
[16:59] <nerochiaro> bfiller: update: i managed to have the pages flip to the cover without closing the album, but the cover is scaled wrong for some reason. trying to fix that.
[16:59] <bfiller> nerochiaro: ack
[17:21] <Tassadar> stgraber: by the way, I suppose devices installed from s-i before the rename happened will be automatically set to the ubuntu-touch/* variant when they'll be updated?
[17:22] <stgraber> Tassadar: yep, they do.
[17:23] <stgraber> Tassadar: they'll grab an update as usual, the new version tarball will contain the new channel name in channel.ini and from that point on they'll use the new name directly
[17:23] <Tassadar> k
[17:26] <ogra_> mterry, i assume you only want to land https://code.launchpad.net/~mterry/session-manager-touch/split/+merge/211549 once kgunn has landed https://code.launchpad.net/~unity-team/unity-system-compositor/new-gl-screen/+merge/210466 ?
[17:26] <ogra_> (which i pinged him about yesterday)
[17:27] <ogra_> mterry, or does usc cope with getting options it doesnt know
[17:27] <mterry> ogra_, yeah really https://code.launchpad.net/~mterry/session-manager-touch/split/+merge/211549 needs to land in concert with ~mterry/unity8/split
[17:27] <mterry> ogra_, so I'd like to have the branch approved, but it needs proper silo treatment along with the unity8 branch
[17:27] <mterry> ogra_, USC does *not* cope well with that
[17:27] <mterry> :)
[17:27] <ogra_> right
[17:27] <ogra_> yeah, thats what i suspected :)
[17:32] <davmor2> popey: what refactoring did you do to the spreadsheet?
[17:32] <popey> i just moved stuff
[17:33] <davmor2> popey: ah fair enough ;)
[17:34] <Saviq> ogra_, how do I map image numbers between http://people.canonical.com/~ogra/touch-image-stats and the revisions?
[17:35] <davmor2> Saviq: Guess work like the rest of us ;)
[17:35] <Saviq> davmor2, I knew there must be some universal approach!
[17:35] <ogra_> Saviq, i'm working on the imagebot currently, in the future it should put links with the revisions in place ... until then http://ci.ubuntu.com/smokeng/trusty/touch/ is the easy way, or the harder way is to fish it out of http://system-image.ubuntu.com/ubuntu-touch/trusty-proposed/mako/index.json
[17:35] <davmor2> Saviq: it should be the same number in the ci train page
[17:36] <Saviq> davmor2, that's probably the best - the landing emails
[17:36] <ogra_> once my bot is done something like http://people.canonical.com/~ogra/touch-image-stats/243.changes will just work
[17:36] <ogra_> (though i have other work distracting me from finishing the bot atm)
[17:37] <Saviq> ETOOMANYCHANNELS too....
[17:39] <davmor2> Saviq:  Hey you open the can of worms don't start to panic now you can't handle them ;)
[17:40] <davmor2> Who's the best person to ask about the light sensor not working?
[17:40] <Saviq> davmor2, I'm past EOD, you're almost there, what do you care ;) someone else will have to deal
[17:41] <ogra_> davmor2, the powerd maintainer
[17:41] <Saviq> LOL
[17:41] <Saviq> davmor2, light as in backlight, or proximity? /me was pressing plenty of buttons today with my cheek...
[17:42] <davmor2> Saviq: light as in backlight, it doesn't do anything and I've been helpfully informed that it used to
[17:42] <Saviq> never really did the job for me...
[17:42] <Saviq> ok, /me moves to low power mode
[17:42] <ogra_> worked always fine for me
[17:43] <ogra_> (on mako that is)
[17:43] <davmor2> ogra_: and now? not right
[17:43] <ogra_> dunno, my usable mako is out of battery atm
[17:43] <ogra_> and the other one has no touchscreen
[17:43] <davmor2> ogra_: hahaha
[17:44] <ogra_> in flo there are known issues with backlight
[17:57] <rsalveti> davmor2: I'll check that bug later this week
[17:57] <nerochiaro> bfiller: i think i'm close to cracking it, but i need to go soon. i should be able to finish it tomorrow morning
[17:58] <bfiller> nerochiaro: anything I could try to at least see if the album doesn't close?
[17:59] <nerochiaro> bfiller:  yes, let me push a temp branch
[18:02] <nerochiaro> bfiller: i actually pushed directly to the MR
[18:02] <nerochiaro> bfiller: as it's a change that will need to go in there anyway
[18:02] <bfiller> nerochiaro: I'll try it
[18:03] <nerochiaro> bfiller: thanks, please update MR with your findings
[18:03] <bfiller> nerochiaro: will do
[18:09] <sergiusens> barry, mandel we good with silo 5 then?
[18:09] <sergiusens> just catching up with emails
[18:10] <barry> sergiusens: lgtm
[18:15] <sergiusens> great
[18:15] <mhall119> bzoltan1: is qt 5.2 going to be backported to Saucy in the SDK PPA?
[18:25] <barry> sergiusens, mandel: got disconnect, not sure if you saw my "good to go" message?
[18:25] <sergiusens> ogra_, rsalveti I added a comment to the vol up/down bug; don't think it's android
[18:25] <sergiusens> barry, yup; got the lgtm one; assumed it's what I wanted to hear :-)
[18:25] <sergiusens> thanks
[18:26] <barry> sergiusens: :)
[18:26] <ogra_> sergiusens, thx
[18:27] <sergiusens> ogra_, should I also reply to the email? my guess is something is filtering it now
[18:27] <ogra_> which email ?
[18:28] <rsalveti> sergiusens: it's not android
[18:29] <sergiusens> ogra_, the landing team meeting email
[18:29] <sergiusens> rsalveti, yeah, but the bug is assigned to android :-P
[18:29] <ogra_> ah, yeah, i think that might make sense
[18:29] <rsalveti> sergiusens: right, but that is fine
[18:29] <rsalveti> it's just a placeholder
[18:29] <sergiusens> rsalveti, have you already figured it out?
[18:29] <rsalveti> I'm currently investigating that bug
[18:29] <ogra_> blame Mir :P
[18:30] <ogra_> its the top one to blame today
[18:30] <rsalveti> right
[18:33] <sergiusens> rsalveti, ogra_ well it's not unfeasible for mir to be it as it grabs the input devices
[18:33] <ogra_> yep
[18:33] <rsalveti> it was also happening before the new mir landed
[18:33] <ogra_> despite the :P i wasnt joking :)
[18:33] <rsalveti> but anyway, checking
[18:34] <ogra_> right, it was broken in 241 already
[18:34] <sergiusens> rsalveti, could also be qt/qtubuntu; had some issues before there
[18:45] <davmor2> rsalveti: ah thanks dude
[19:08] <jkt> hi there
[19:08] <jkt> running patched ubuntu-ui-components (removed all references to the thumbnailer because that's something I have no idea where to get and how to build)
[19:08] <mhall119> bzoltan1: Kaleo: jkt is trying to build the ubuntu-ui-toolkit on gentoo (for testing the Trojita port)
[19:08] <jkt> file:///opt/qt5.2/qml/Ubuntu/Components/MainView.qml:18:1: module "Ubuntu.Unity.Action" is not installed  import Ubuntu.Unity.Action 1.1 as UnityActions
[19:08] <mhall119> can you help him?
[19:09] <jkt> the ubuntu-ui-components built and installed (after patching out the thumbnmailer) just fine, but apparently it requires some Unity-specific bits
[19:09] <jkt> I'm on KDE4 if it's relevant
[19:11] <mhall119> jkt: https://launchpad.net/unity-action-api looks to be the project that provides it
[19:12] <mhall119> which looks like it needs HUD stuff
[19:12] <mhall119> so really MainView should be runable without Unity.Actions being available to it
[19:13] <jkt> mhall119: ack, needs hud-2 -> no joy
[19:13] <mhall119> bzoltan1: ^^ if you agree, I'll file a bug about that
[19:14] <alecu> beuno, JamesTait: did you guys got enough details on the update process?
[19:16] <mhall119> jkt: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1294298 if you want to subscribe to it
[19:17] <jkt> mhall119: you might want to add Ubuntu/Components/Page.qml to the list
[19:18] <jkt> mhall119: and grep shows that TextField.qml and Action.qml are the other two culprits
[19:20] <mhall119> done
[19:35] <bzoltan1> mhall119:  thanks for filing the bug. We will check it out in the morning
[19:36] <timppa> evening! I just typed my longest note with the notes app and noticed that it does not scroll. So when the note is long enough the text hides under the keyboard
[19:36] <timppa> I think that's not the way it should be?!
[19:38] <mhall119> thanks bzoltan1
[19:39] <t1mp> mhall119: what's the use case for that bug?
[19:39] <mhall119> t1mp: running an app outside of Unity
[19:40] <t1mp> mhall119: that dependency is there because actions of the app are also made available to the HUD
[19:40] <mhall119> t1mp: then they should be exposed in a way that allows the app to run when the HUD isn't there
[19:40] <bzoltan1> mhall119: what is the use case to use an app without Unity?
[19:40] <mhall119> bzoltan1: in this case, the upstream developer doesn't run Unity (or even Ubuntu) but wants to run the Ubuntu UI port of his project
[19:40] <t1mp> mhall119: you mean for porting it to other operating systems?
[19:40] <bzoltan1> mhall119:  I am not against it :) justtry to understand the issue
[19:41] <mhall119> t1mp: if I run Xubuntu I should still be able to run Ubuntu UI toolkit apps
[19:41] <bzoltan1> mhall119: is that written somewhere?
[19:41] <mhall119> I didn't think it would need to be
[19:42] <t1mp> mhall119: the plan was that more advanced functions of an app such changing the saturation of a photo in gallery-app, are only exposed via the hud
[19:42] <bzoltan1> mhall119:  kind of
[19:42] <t1mp> mhall119: those apps would break if there is no HUD
[19:42] <mhall119> I can run Gtk apps in KDE, and Qt apps in Gnome, I should be able to run UITK apps in either
[19:42] <t1mp> mhall119: to run gtk apps in kde you still need the gtk libs
[19:42] <mhall119> t1mp: that's fine, in that case the UnityActions shouldn't be a part of MainView, but something added on optionally
[19:42] <t1mp> < bzoltan1> mhall119:  I am not against it :) justtry to understand the issue <-- same for me :)
[19:43] <bzoltan1> mhall119:  It is a nice idea and I do not say I do not like it, but it is significant enough to get some real mandate to work on it
[19:43] <t1mp> mhall119: why? unityactions comes from a lib that you can install
[19:43] <mhall119> t1mp: which pulls in libhud
[19:44] <t1mp> mhall119: yes, just like running any qt app on gnome will pull in libqt
[19:45] <t1mp> mhall119: I agree that it is nice to keep the dependencies as small as possible. Just trying to find a use case to make the importance more than "Wishlist" :)
[19:45] <mhall119> t1mp: libqt is on the same level as ubuntu-ui-toolkit, libhud is not
[19:47] <mhall119> t1mp: the user case is that app developers can't port their app to our awesome convergence toolkit without running Ubuntu and Unity on their development machine
[19:48] <mhall119> in this case, an upstream email client is giving us an Ubuntu UI port, we should let them develop and run it on the same environment they currently develop on
[19:48] <t1mp> mhall119: yes, that makes sense
[19:48] <bzoltan1> mhall119:  according to my prsent understanding the target platform for the SDK and so UITK is the Ubuntu 14.04
[19:48] <mhall119> bzoltan1: Ubuntu 14.04 does not require Unity though
[19:49] <mhall119> jkt is happy compiling from source to run it on Gentoo, but the more dependencies there are to use MainView, the bigger roadblock that becomes
[19:49] <bzoltan1> mhall119: I might not be competent enough to say much about that
[19:50] <mhall119> bzoltan1: is there any technical reason other than convenience to keep such a narrow target for UITK?
[19:51] <bzoltan1> mhall119:  my understanding is the Unity is a centerpiece in 14.04
[19:51] <t1mp> mhall119: support takes a lot of time, and we have very limited time
[19:51] <bzoltan1> mhall119:  resources, schedule, requirements
[19:51] <mhall119> t1mp: I understand, and that's a valid reason for "not right now", but not for "not ever"
[19:51] <t1mp> mhall119: technically I see no problems in making it work the way you like :)
[19:51] <mhall119> I'm okay with "not right now" if that's the answer
[19:52] <bzoltan1> mhall119:  again :) I am not against it... just wish to see a written, documented, discussed and signed requirement
[19:52] <bzoltan1> mhall119:  "not right now" means not in the next 3-4 months
[19:52] <bzoltan1> mhall119:  zsombi has commented on the bug
[19:53] <bzoltan1> mhall119:  he has a good point
[19:54] <mhall119> bzoltan1: sounds reasonable to me, though I hope "HUD going away" is a temporary condition of the bottom edge/header changes, not a permanent situation
[19:54] <mhall119> but it sounds like a good opportunity to make it a clean separation between UITK and Unity
[19:55] <t1mp> mhall119: if the hud would go away, yes. If it comes back with a different way to invoke it it would be a pity to break/remove the APIs for adding actions to the HUD now
[19:55] <t1mp> more than a pity. We promised not to break APIs
[19:56] <bzoltan1> mhall119:  me too, but keep in mind that right now I have no mandate, neither time or resources to consider other targets than Ubuntu 14.04 with Unity ... in case you need something else :) you know  who to go.
[19:58] <t1mp> I wonder whether QtQuick can do conditional imports
[19:59] <mhall119> t1mp: the APIs exposed to developers aren't dependent on Ubuntu.Unity.Actions, that's an implementation detail in the UITK
[19:59] <t1mp> in a way, yes - https://bugreports.qt-project.org/browse/QTBUG-16854
[19:59] <mhall119> t1mp: developers just use Ubuntu.Components.Action
[19:59] <t1mp> mhall119: true. I was thinking of import Ubuntu.Unity.Action 1.1 as UnityActions
[19:59] <t1mp> in our Action.qml
[20:00] <t1mp> I think we can hide that with a Loader inside Action.qml
[20:00] <mhall119> which could be be replaced by something else that doesn't have a hard dependency on other libs, and we wouldn't break the API we give developers
[20:00] <t1mp> mhall119: do you know of any apps that use the UITK APIs to offer functionality in the HUD?
[20:01] <nhaines> Not to be unconstructive, but I would hate to think that the current situation of Unity 8 is that "no one knows what's happening with HUD."
[20:04] <t1mp> nhaines: the new bottom-edge for apps (which I like) conflicts with the current way of invoking the HUD. That's what I know
[20:05] <mhall119> t1mp: I know the webbrowser-app does, my uReadIt app does, probably others (though we didn't push this API much)
[20:06] <nhaines> t1mp: That's where I'm at.
[20:07] <mhall119> nhaines: it's in the hands of the designers now to figure out how to expose the HUD in a way that doesn't conflict with the bottom edge changes
[20:07]  * mhall119 personally hopes it's exposed the same way indicators are, from the top
[20:08] <t1mp> nhaines: the designers presented the new bottom edge and a new header design in one week, so I don't expect they will also present a solution for that this week
[20:08] <nhaines> mhall119, t1mp: this kind of thing should have been hand-in-hand with the bottom edge design (if not the header design).
[20:09] <nhaines> I've given thought to overloading the search panel for HUD but I don't think I like that idea.
[20:09] <t1mp> hmm
[20:09] <t1mp> apps can have a search button in the header which changes the header title to a search field
[20:09] <t1mp> maybe the search panel in the status bar will not be needed anymore then?
[20:09] <nhaines> There's already no search panel in the status bar.
[20:10] <nhaines> Basically, all the vague mockups with no API or implementation means that once again I have to throw away all my app designs and start over... whenever code decides to land.
[20:11] <t1mp> nhaines: you are right. the search panel is not there in apps, only in the scopes
[20:11] <t1mp> nhaines: which app designs do you have?
[20:11] <t1mp> nhaines: many of the new header APIs and implementation are my tasks. So if you have suggestions feel free to tell me
[20:12] <t1mp> nhaines: we try not to break existing APIs, and so far we managed not to do that
[20:21] <nhaines> t1mp: I'm working on a document editor for writers.
[20:22] <nhaines> But I'm not going to waste my time designing toolbars and HUD actions when both of those designs are going to be invalidated.
[20:23] <nhaines> t1mp: I'm a little skeptical about the header design (same icon for tabs and for actions seems *really* sketchy to me) but I can't wait to see them in action because there's a potential to be really interesting.
[20:23] <nhaines> t1mp: any idea when they're planned to land?
[20:23] <t1mp> nhaines: I don't know what will happen to the HUD
[20:24] <t1mp> nhaines: for the toolbar, the plan is that you only have to flip one boolean switch in MainView, and the tools you had in the toolbar will move to the header
[20:25] <t1mp> nhaines: it won't land all at once, but in steps. The first steps (bottom edge available for apps, tabs in drawer in the header) in the coming two weeks
[20:25] <t1mp> nhaines: we got a bit slowed down because of the transition to qt 5.2. I cannot land new things until we have a stable image with qt 5.2
[20:26] <t1mp> nhaines: you can track the work in progress here https://blueprints.launchpad.net/ubuntu-ui-toolkit/+spec/new-header
[20:26] <jkt> bzoltan1, t1mp: hi there
[20:26] <t1mp> jkt: hello
[20:27] <jkt> re the unity dep in your QML bits
[20:27] <bzoltan1> hello jkt
[20:27] <jkt> you realize that this is going to make testing apps for Ubuntu rather hard, if not impossible, when one does not run Ubuntu, right?
[20:27] <bzoltan1> jkt:  yes
[20:28] <jkt> well
[20:28] <jkt> that's something unexpected
[20:28] <bzoltan1> jkt:   why is that?
[20:28] <jkt> do you plan to require just a couple of installed libs, or do you plan to impose runtime bits (i.e. running Unity) as well?
[20:29] <bzoltan1> jkt: to put it very simple. The primary target for the Ubuntu SDK is Ubuntu.
[20:30] <t1mp> jkt: you don't need to run unity, but we do need the unity libs as they define the Action component that is now in UITK
[20:30] <bzoltan1> jkt: we do not test our SDK (neither the tools or the APIs) on other platform than on Ubuntu
[20:30] <jkt> I'm not talking about using a SDK, but about running applications
[20:30] <jkt> I'm fine with hitting bugs
[20:31] <jkt> and reporting them, of course
[20:31] <t1mp> jkt: you want to port your email app to our UITK, but you want it to stay cross-platform and not depend on unity libs?
[20:31] <jkt> this is something which is under development, sure
[20:31] <bzoltan1> jkt: As far as I understand now, the objective of the Ubuntu SDK is to create applications for Ubuntu.
[20:31] <jkt> I do not want to port anything anywhere, "you" want a Unity frontend for that
[20:31] <jkt> I'm reviewing the patches
[20:31] <t1mp> ok, I didn't know that
[20:32] <jkt> anyway, it's your choice to make by all means -- it's just something which surprised me a bit
[20:33] <bzoltan1> jkt:  I would love to see the ubuntu SDK and the APIs portable to other platforms. That would be super cool and exciting.
[20:33] <t1mp> I agree with bzoltan1.
[20:33] <bzoltan1> jkt: I wonder what surprised you. Could you please elaborate?
[20:33] <jkt> the way things have worked for past X years was that you were able to run any app on any desktop, you just needed to install a couple of libraries
[20:34] <jkt> what surprised me was that you were surprised that one would want to run a "built for Ubuntu" app on another desktop
[20:34] <jkt> perhaps I considered that more of an interoperable desktop platform than e.g. a mobile UI
[20:34] <ajalkane> Ubuntu SDK is open source, why should it be a problem to have it on other platforms? It becomes only an issue of politics
[20:34] <bzoltan1> jkt: it did not surprise me at all. That is a very natural thing.
[20:35] <jkt> I do understand that one needs to "port" an app (i.e. rewrite an UI) between, say, MeeGo Harmattan and Sailfish
[20:35] <jkt> these are completely different beasts, and that's how stuff works on mobile, sadly
[20:35] <bzoltan1> ajalkane: it is not forbidden to port the SDK to any platform.
[20:35] <jkt> but on desktop Linux, there were historically no such barriers, and one could run, say, a Gnome app on KDE without any hassle
[20:36] <ajalkane> bzoltan1: that's exactly what I mean. It's just a question of politics if other distros want to include it.
[20:36] <jkt> there were no nasty surprises like menubar disappearing only because platform XYZ has it outside of the window or whatever
[20:36] <ajalkane> I for one applaud Canonical in keeping it open source
[20:36] <bzoltan1> ajalkane: I do not do politics... ever
[20:37] <jkt> I've been told that the QML components for Ubuntu are supposed to power both desktop and mobile apps
[20:37] <bzoltan1> jkt: that is correct
[20:37] <jkt> and therefore I'm surprised that it will be hard to run the desktop ones on a non-Unity desktop, that's all
[20:38] <jkt> of course "you" are free to spend your resources in a way which fits you best
[20:38] <t1mp> jkt: there is still a bunch of stuff missing for desktop in our uitk. We don't intend to make it hard to run on a non-unity desktop
[20:38] <bzoltan1> jkt: As far as I know it has never been a secret that the primary platform as development environment and target is Ubuntu
[20:38] <t1mp> but it is not done yet, especially not for desktop
[20:39] <ajalkane> bzoltan1: I meant politics on part of the other distros if they choose to include this stuff, not on Ubuntus part
[20:39] <bzoltan1> jkt: ajalkane: we do not build anything with a purpose to make porting hard or impossible. Portable code is a fundamental value and we all respect this value.
[20:39] <dobey> jkt: it's no different from any other app, whether it's in qml, c++, or python. as long as you have the necessary dependencies installed and working, the app should work
[20:40] <bzoltan1> ajalkane: I do not do any politics, ever... in any meaning.
[20:40] <dobey> bzoltan1: are you dead? :)
[20:41] <bzoltan1> dobey: :) I have pulse
[20:41] <dobey> bzoltan1: whether you see something you do as political or not doesn't much matter. anything you do can be seen as a political thing by someone else. that's how politics works :)
[20:41] <ajalkane> Well me neither. But it's obvious there's lots of politics between the distros. One example is the whole holabaloo between Wayland and Mir, Upstart and systemd etc
[20:42] <nhaines> t1mp: Thanks for the blueprint!  Sorry, I'm in and out a bit today.  But I appreciate your explanations and the extra info!  :)
[20:43] <t1mp> nhaines: you're welcome. I also want to get the stuff in UITK so developers can use it ASAP.
[20:43] <bzoltan1> jkt: actually our idea for application developmen is that the SDK will have 3 major components. (1) The SDK Tools, that is QtCreator with special plugins (2) an emulator with the full blown Ubuntu and (3) a click chroot builder. One can create apps for Ubuntu on any platform where these components can work. Even on OSX or Windows ...
[20:44] <t1mp> I've seen a port of Ubuntu.Components to OSX... (can't find the website right now)
[20:44] <bzoltan1> dobey: I know :) But that is not my problem. I do no do politics and I am happy like this.
[20:45] <bzoltan1> t1mp:  and the QtC is perfectly portable too... same as the emulator. The click tools might need some love, but I think they are portable too
[20:45] <dobey> lp:click on osx or win would be a bit of a problem right now
[20:46] <bzoltan1> jkt: so even on Ubuntu we will go away from the classic model that the runtime is the development environment. It is not sustainable.
[20:46] <dobey> as it uses python-gi and has some code written in vala
[20:46] <t1mp> bzoltan1: click tools you only need if your target is ubuntu. I would be happy if people would like to develop cross-platform apps (for osx/windows) using our toolkit :)
[20:46] <bzoltan1> dobey:  not on the emulator ;)
[20:46] <t1mp> that would mean we have a really good toolkit :)
[20:46] <dobey> well, sure
[20:47] <bzoltan1> dobey:  XCode does the same the Maemo SDKs did the same ... neither of these used any local service or runtime dependency
[20:47] <t1mp> ^android sdk does the same
[20:48] <jkt> well, it just feels backwards when one needs an emulator or chroot or a virtual machine just for running a "desktop application" on a pretty common desktop Linux :)
[20:48] <dobey> bzoltan1: sure. but in that case "portability" isn't a concern for those tools, because they'll only ever be run in the VM
[20:48] <t1mp> jkt: yes, I agree.
[20:48] <dobey> jkt: you don't need an emulator to run the stuff on linux
[20:48] <t1mp> jkt: the bug was confirmed. It is just a matter of time (I'm not saying how much). Any help is welcome :)
[20:49] <dobey> the emulator is to run apps in an environment they would be run in on the phone/tablet/ubuntu
[20:50] <bzoltan1> jkt: we have seen that the model you talk about is hardly sustainable even on Ubuntu
[20:51] <bzoltan1> jkt:  even as we speak we provide and support the SDK for three different Ubuntu series ... it is not easy and it holds us back
[20:51] <t1mp> ^just to clarify, it is technically possible to get it all to work on 10 versions of ubuntu and also osx and windows and android, but it takes a *lot* of work to implement it and then even more to support it
[20:51] <bzoltan1> t1mp: +1k
[20:53] <JamesTait> alecu, I'm not here, but I think we did: https://bugs.launchpad.net/software-center-agent/+bug/1293797 - feel free to make any necessary corrections. :)
[20:53] <bzoltan1> not to mention that we do care about how things look and how good quality they are... and I think it is just plain honesty that we do not say that we provide the same experience and quality on distros we can not test and dogfood. But contributions are welcome. We do not block the porting.
[20:54] <bzoltan1> jkt: ajalkane: dobey ^
[20:54] <jkt> well, at this time I should probably point out that the application which made me come here builds and runs on OS/2
[20:54] <jkt> but sure, portability and packaging costs real time
[20:54] <t1mp> I'd be happy if people port uitk, and do my best to make it easy for them
[20:55] <jkt> "uitk" is what in this context?
[20:55] <ajalkane> Exactly as I would expect
[20:55] <t1mp> uitk = Ubuntu UI Toolkit, also known as Ubuntu.Components
[20:56] <t1mp> I'd support porting the full SDK also, but I happen to work more on UITK myself
[20:56] <jkt> right
[20:57] <bzoltan1> I totally  +1 what t1mp said
[20:57] <jkt> so as a feedback from another dev, it appears to build fine on Gentoo when one nukes the dep on "thumbnailer"
[20:57] <dobey> unless upstream qt has stopped supporting os/2, i don't see any reason why the uitk and apps couldn't be ported to os/2
[20:57] <bzoltan1> jkt:  I know .. that was one thing what caused problem for us too on 12.04
[20:57] <t1mp> jkt: oh cool. So there is no problem with the unity/hud dependency?
[20:58] <jkt> that's a runtime dep in the qml files
[20:58] <jkt> ...or I need more coffee
[20:58] <jkt> nope, I don't
[20:59] <jkt> ubuntu-ui-toolkit doesn't require these libs at build time, but its .qml files cannot load because they reference the unity-action-api
[20:59] <jkt> but that's what the bug report says already
[20:59] <dansuf> Is it possible to check which version of mir is ubuntu touch using?
[21:00] <dansuf> Or which the current daily build is using?
[21:01] <dobey> dpkg -l mir?
[21:01] <dobey> or https://launchpad.net/ubuntu/+source/mir
[21:01] <dansuf> there is no such package
[21:02] <dobey> press tab?
[21:02] <dansuf> I'm not too experienced in it but if daily contains the newset version that's not good
[21:02] <dansuf> for me
[21:02] <cwayne_> dpkg -l | grep mir
[21:02] <dansuf> as I've got a little problem
[21:02] <dobey> then don't run the daily builds?
[21:02] <dobey> or file a bug, because that's what the daily builds are for… testing
[21:03] <dansuf> the fact is I'm trying to port touch to my phone and it can be my fault, not the ubuntu itself
[21:04] <dansuf> thanks for the suggestion, I will file a bug when I'm sure it's software problem
[21:06] <mandel> sergiusens, sorry, I was out, yes, but I notice you already landed it :)
[21:07] <t1mp> dansuf:  apt-cache policy libmirplatform
[21:08] <dansuf> t1mp, thank you
[21:09] <dansuf> This is what happens in my logcat after starting lightdm service: http://pastebin.com/KMaQKNEL
[21:11] <dansuf> and in unity-system-compositor-log I've got this error:
[21:11] <dansuf> terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
[21:11] <dansuf>   what():  error during hwc set()
[21:16] <Saviq> dobey, fwiw, there's no bash completion on the devices...
[21:17] <dobey> Saviq: oh. well, install bash-completion then hit tab? :)
[21:17] <Saviq> dansuf, this error shows up sometimes when different mir servers fight for the hardware, as far as I can tell, it usually goes away after a reboot when everything settles again
[21:18] <Saviq> dansuf, not that this should be needed - still a bug
[21:18] <dansuf> Saviq, the problem is this happens always
[21:18] <dansuf> and I can't get any grphics at all
[21:19] <Saviq> dansuf, what device? which image number?
[21:19] <Saviq> dansuf, also, there's #ubuntu-mir that some mir folk hang out on, probably easier to get them there
[21:20] <dansuf> I am porting it to sony ericson  live with walkman, codename coconut
[21:21] <dansuf> If you mean ready device images there are none
[21:21] <dansuf> except for old unflipped saucy
[21:22] <dansuf> Thank you for giving me the channel name, I will definitely go there.
[21:22] <Saviq> dansuf, right, that might mean it's a device-specific thing, definitely talk to mir folk
[21:38] <rsalveti> jezz, apparmor takes a huge time to run during first boot on the emulator
[21:38] <rsalveti> running for more than 5 minutes already
[21:38] <jdstrand> rsalveti: speaking of which, what's up with the x86 emulator? I saw a blog post and am itching to try
[21:40] <jdstrand> rsalveti: also, note, we did get about a 40% improvement on compile times this cycle, but the emulator is a rough environment to make fast
[21:40] <jdstrand> rsalveti: we also devised a method to precompile policy which the image generation process could use for preinstalled apps, which would help quite a bit
[21:41] <jdstrand> rsalveti: but that most likely won't land this cycle
[21:44] <rsalveti> jdstrand: just missing a qt5 stack compatible with gles, which is what I'm currently working on
[21:44] <rsalveti> jdstrand: hopefully should have something for later this week
[21:44] <rsalveti> jdstrand: oh, ok
[21:45] <jdstrand> rsalveti: nice! :)
[21:48] <rsalveti> Saviq: wonder if we have a leak with the emulator as well, unity8 keeps eating more and more if you let the first boot navigation guide running
[21:48] <rsalveti> already eating 80%
[21:49] <rsalveti> 84%
[21:49] <rsalveti> oom will probably kill it in a few
[21:49] <Saviq> rsalveti, interesting... but only when the welcome thing is running?
[21:50] <Saviq> rsalveti, bug, please, we'll look into it
[21:54] <rsalveti> Saviq: when rendering it seems
[21:54] <Saviq> rsalveti, rendering anything?
[21:54] <Saviq> rsalveti, /me thinks mir/u-s-c
[21:55] <rsalveti> yeah, moving to a different lens is already enough
[21:55] <rsalveti> system-compositor seems fine, unity8 is the one eating more memory
[21:55] <rsalveti> let me open a bug
[21:58] <rsalveti> bug 1294373
[21:59] <rsalveti> I'd guess something with qt5.2
[22:17] <Tassadar> stgraber: btw, ubuntu-touch/devel-proposed* aliases are no longer hidden after the rename (but trusty-proposed still is)
[22:33] <stgraber> Tassadar: should be better now
[22:34] <stgraber> not sure if that matches what we had before as I've just redone it from scratch but I think what's visible now makes sense
[22:34] <Tassadar> yeah
[23:22] <sin18> even though i have unlocked my nexus 4 (fastboot oem unlock), at the time of flashing it bombs with 'can't boot recovery image' as im flashing the device with ubuntu-device-flash command
[23:25] <sergiusens> sin18, how are you running it?
[23:26] <sin18> sudo ubuntu-device-flash --channel=devel --bootstrap
[23:27] <sergiusens> sin18, can you pastebin the output?
[23:30] <sin18> sergiusens : pastebin.com/GmX8ShRb
[23:39] <shiggitay> rsalveti, hello :)
[23:39] <shiggitay> any N5 progress?
[23:40] <sergiusens> sin18, do you have xz-utils installed? (apt get it if not)
[23:40] <sergiusens> sin18, oh, and why the sudo to ubuntu-device-flash
[23:40] <sergiusens> ?
[23:41] <sin18> sergiusens : already have xz-utils .... as for sudo (no god reason now that you pose the ques).. let me run it with regular userid
[23:42] <sin18> no good*
[23:51] <sin18> sergiusens : i know why i was using sudo as i run into error -> mkdir /home/ubuntu/.cache/ubuntu-images/pool: permission denied
[23:52] <sergiusens> sin18, that can only happen if the first run was done as sudo
[23:52] <sergiusens> sin18, /home/ubuntu, is this a VM?
[23:54] <sin18> sergiusens : yes it is VM (virtualbox) hosted on fedora
[23:54] <sergiusens> sin18, that's going to be a problem with usb devices appearing and dissappearing; that's the reason it fails
[23:55] <sin18> sergiusens : that is true where i have to check 'usb' under devices during the process. However, i remember using same setup to install ubuntu touch on nexus 7 several months back
[23:56] <sergiusens> sin18, if you want to flash from fedora install go from yum, hope it has 1.2 and then "go get launchpad.net/goget-ubuntu-touch/ubuntu-device-flash" and make sure adb ad fastboot are avail
[23:57] <sergiusens> sin18, well; if from the VM you can run: adb device; adb reboot bootloader; fastboot devices; fastboot reboot; adb devices and it never fails I will look into it a bit more
[23:58] <sin18> sergiusens : i can confirm that adb device; adb reboot bootloader; fastboot devices; work for me on VM