[00:35] <cxa> Question, does anyone know if I can flash Ubuntu Touch to my Samsung Victory?  Or is it only Nexus devices?
[00:36] <cxa> Question, does anyone know if I can flash Ubuntu Touch to my Samsung Victory?  Or is it only Nexus devices?
[01:02] <AskUbuntu> Ayuda ubuntu para moviles | http://askubuntu.com/q/367018
[01:56] <bray90820> I am trying to install ubuntu touch but i keep getting status 7
[01:57] <bray90820> HTC G2
[02:39] <nmh> is it possible to load ubuntu onto a galaxy s3
[02:40] <RobbyF> kinda
[02:40] <genii> According to https://wiki.ubuntu.com/Touch/Devices , yes
[02:40] <nmh> ive seen some notes on the wiki for it but unsure of how to just learning the os and have an old android s3 to mess with
[02:40] <nmh> yeah thats where I am atm
[02:41] <nmh> gnna try it a few times
[02:42] <melvster> is it possible to run a different browser on ubuntu touch?
[02:42] <melvster> different than the default i mean
[02:50] <nmh> cant seem to find proper instructions for d2vzw
[02:50] <nmh> says unsuported :-(
[02:50] <nmh> noooooooo
[03:04] <AskUbuntu> having trouble with ubuntu installing on galaxy s3 d2vzw | http://askubuntu.com/q/367048
[03:25] <bray90820> So i am trying to install ubuntu on an HTC Desire Z but i keep getting status 7 error
[03:37] <ramdiks> hello
[05:16] <bray90820> So i am trying to install ubuntu on an HTC Desire Z but i keep getting status 7 error
[05:36] <duflu> bray90820: I don't think the Desire is working yet. There is at least one community member actively working on it though
[05:37] <bray90820> It says it is on the iki
[05:37] <bray90820> wiki
[05:39] <bray90820> duflu: https://wiki.ubuntu.com/Touch/Devices/flipped_vision
[05:40] <duflu> bray90820: No, that's a community page. Not official support. Official support is listed here: https://wiki.ubuntu.com/Touch/Devices#Working_with_phablet-flash
[05:42] <bray90820> my device is listed under
[05:42] <bray90820> Working, but not available from cdimage.ubuntu.com
[05:42] <bray90820> desire z
[05:43] <duflu> bray90820: "Working" is only the opinion of someone outside of Canonical. We can't confirm it
[05:43] <bray90820> Alright
[05:43] <bray90820> but why would i get status 7
[05:52] <Shashank> I have a question ..what if my nexus does't boot ? how to phablet-flash will work in that case ?
[08:16] <NewUTouchUser> Does Ubuntu Touch have a command to check the battery status by using command line?
[08:33] <wayting> hi, how long should please do not unplug device until phablet-flash finishes"
[08:33] <wayting> take to finish? My nexus 4 is blank
[08:54] <NewUTouchUser> Seemingly "sudo upower --dump" gives the info that I was looking for
[08:59] <pitti> NewUTouchUser: no need for sudo
[09:02] <NewUTouchUser> pitti: True
[09:39] <JamesTait> Good morning all; happy Animation Day! :-D
[09:51] <PAmako> Hi, I've tried installing ubuntu touch, now my nexus 4 is stuck on the google launch screen. what's the next step?
[09:57] <nerochiaro> tmoenicke: zsombi: any progress on https://bugs.launchpad.net/ubuntu-keyboard/+bug/1243164 ?
[09:57] <zsombi> nerochiaro: none on my side
[10:01] <zsombi> nerochiaro: have you checked that substing TextArea with TextEdit will do the same?
[10:07] <nerochiaro> zsombi: IIRC yes
[10:07] <nerochiaro> zsombi: which makes it an OSK problem i guess
[10:07] <zsombi> nerochiaro: ok, then I'll just follow that. pls update the bug with this fact
[10:08] <nerochiaro> zsombi: ok. let me double check and I'll update it
[10:08] <zsombi> nerochiaro: thx!!!
[10:09] <zsombi> nerochiaro: I will have a bug fix for IMA that I will ask you to check later today. It affects MAs overlapping IMAs (oSoMoN reported once a bug for that)
[10:10] <nerochiaro> zsombi: ok, i will check that when you have it read. i'm also noticing another strange behavior while trying to work with cursorPosition. it seems that when the height of the TextArea changes the cursorPosition becomes zero, then goes back to the position it should have
[10:10] <nerochiaro> zsombi: i'll make a test case for it as well
[10:10] <zsombi> nerochiaro: hmm, that's weird!
[10:18] <tsdgeos> t1mp: any eta for the review on https://code.launchpad.net/~aacid/ubuntu-ui-toolkit/tabbar_external_use/+merge/192307 ?
[10:21] <t1mp> tsdgeos: I got some other related stuff merged in last Friday.. Now I have one more tabs-related MR upcoming, but also some bugs to fix, so it depends on what I give priorities these days
[10:21] <t1mp> tsdgeos: how urgent is your mr?
[10:22] <tsdgeos> t1mp: as urgent as any other development :D
[10:22] <tsdgeos> it's blocking a feature in the shell
[10:22] <t1mp> which feature?
[10:22] <tsdgeos> but we don't have any immediate need other than the "should be done when it's done" :D
[10:22] <tsdgeos> t1mp: the hability to have tabs :D
[10:23] <tsdgeos> dash navigation bar at the bottom is gone and is replaced by tabs in the dash header
[10:24] <t1mp> oh, okay.
[10:24] <t1mp> tsdgeos: is "this week" good enough? I'm quite sure we'll be able to do that. Perhaps beginning of this week.
[10:25] <tsdgeos> t1mp: yes, this week is good enough :-)
[10:25] <t1mp> tsdgeos: ok, great. let's do that then. :) probably I will ask you one of these days to sync with trunk before we merge it.
[10:27] <tsdgeos> sure
[10:37] <Shashank> I have a question .. what if my nexus does't boot after copying image? how to phablet-flash will work again in that case ?
[10:38] <Shashank> anyone please answer to my question ...
[10:40] <Shashank> or tell me where I can found answer of my question ...
[10:57] <davmor2> Morning all
[10:59] <Jwtc2000> Mornin
[10:59] <davmor2> ogra_: maguro on the image 5 isn't always switching back on.  I've checked it has power but it's like it isn't waking from a long suspend.  I.E. Let it switch itself off on a night put it down first thing in the morning try turning it on nothing.  You have to remove the battery to get it back up.  If it happens again whats the best info to grab?
[11:00] <davmor2> ogra_: is it just syslog?
[11:28] <nerochiaro> zsombi: updated the bug to confirm TextEdit does the same
[11:39] <ogra_> davmor2, syslog and kern.log i think ...
[11:40] <davmor2> ogra_: thank, only every seems to be after a really long sleep, one or two hours makes no odds to it.
[11:42] <davmor2> ogra_: also have there been any images after 5?  It's no otaing here if there have
[11:44] <mardy> cjwatson: ping (question about click hooks)
[11:44] <nerochiaro> zsombi: this is the other problem I noticed, and you said "weird" this morning. can you please have a look and at least confirm it ? https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1245450 thanks
[11:51] <sil2100> Hi guys! I would need someone with notes-app and gallery-app AP experience to take a look at these two merges:
[11:51] <sil2100> https://code.launchpad.net/~osomon/notes-app/hide-toolbar/+merge/192727
[11:51] <sil2100> https://code.launchpad.net/~osomon/gallery-app/hide-toolbar/+merge/192746
[12:13] <Marquez> Hey
[12:30] <Predu> hello
[13:05] <cjwatson> mardy: just ask
[13:05] <mardy> cjwatson: hi! Do I understand correctly, that each hook can serve only one file?
[13:07] <mardy> cjwatson: if a click package has two files, like "calendar.service" and "contacts.service", is it possible to have a hook to symlink both of them under ~/.local/share/accounts7services/?
[13:07] <mardy> s,7,/,
[13:07] <cjwatson> mardy: There's one symlink per app in a package.  Wouldn't that situation amount to a multi-app package?
[13:08] <cjwatson> e.g. "hooks": { "calendar": { "accounts": "calendar.service" }, "contacts": { "accounts": "contacts.service" } } or whatever
[13:09] <cjwatson> We don't have any multi-app packages in place right now AFAIK and you'd probably be breaking new ground to some extent by attempting to use them, but the design is supposed to allow for them
[13:10] <mardy> cjwatson: it's not really multi app (it could be an app shipping an account plugin which supports multiple services), but whatever works will do
[13:12] <pete-woods> sil2100: I'll have a look at that bug
[13:12] <mardy> cjwatson: have you thought about providing the hook with a variable ${original-filename} which could be used in the file Pattern rule?
[13:13] <popey> anyone fancy confirming bug 1245482
[13:13] <sil2100> pete-woods: the HUD/Unity one? Thanks :)
[13:13] <pete-woods> sil2100: can't guarantee I can fix it
[13:13] <mardy> cjwatson: so something like this could work: "hooks": { "account-services": [ "calendar.service", "contacts.service" ] }
[13:13] <pete-woods> but I'll at least have a good look
[13:14] <sil2100> pete-woods: it would be at least enough if we knew who exactly to assign it to - as if it's an AP issue, I guess we can get some QA AP guys looking into this
[13:14] <mardy> cjwatson: and the Pattern rule could then be "Pattern: ${home}/.local/share/services/${id}_${original-filename}
[13:15] <cjwatson> mardy: If this is going to be a common case, have you considered having account-service-supporting apps put their .service files in a directory instead and symlinking to that?
[13:15] <pete-woods> sil2100: do we know if the tests fail / are unrelaible on saucy?
[13:15] <cjwatson> mardy: But feel free to file a bug for that; I'll have to think about the corner cases though (e.g. what if the "original filename" contains "/")
[13:16] <cjwatson> mardy: Also, I have a different thought
[13:16] <zsombi> nerochiaro: the sample code in the bug #1245450 uses TextEdit. Do you have any special setup of the  TextArea, or you use the default property settings?
[13:16] <cjwatson> mardy: If these are really ways to attach to different targets (i.e. calendar, contacts, etc. are system-defined things), then you should surely have multiple system-defined hooks instead
[13:17] <cjwatson> mardy: so it would be "hooks": { "app": { "account-service-calendar": "calendar.service", "account-service-contact": "contact.service" } }
[13:18] <zsombi> nerochiaro: also, using simple TextEdit does not really mirror the TextArea, because in the TextArea the cursor window is not the entire TextEdit, but only a section of it (due to the Flickable used to scroll teh content)
[13:18] <sil2100> pete-woods: from what I know, these were passing all the time on saucy
[13:18] <sil2100> pete-woods: I'll double-check though as we most probably had a period of 'no-tests' in saucy recently
[13:18] <mardy> cjwatson: not really, because all these service files end up being installed in the same directory
[13:20] <cjwatson> mardy: That's not relevant
[13:21] <cjwatson> Are "calendar" and "contacts" system-defined concepts?
[13:22] <mardy> cjwatson: no, they are defined by apps
[13:23] <cjwatson> ah, ok
[13:23] <cjwatson> well, feel free to file that bug and I'll see if I can work out what might make sense
[13:24] <mardy> cjwatson: OK, thanks
[13:24] <mardy> cjwatson: I'll give it some other thoughts first
[14:20] <nerochiaro> zsombi: sorry, was at lunch. i uploaded the wrong sample, if you put a textArea there it does the same thing (both with default props and with autoexpand)
[14:37] <zsombi> nerochiaro: ok, thx
[14:46] <nerochiaro> zsombi: can you confirm the bug ?
[14:47] <zsombi> nerochiaro: not yet, but will take it as next
[15:26] <nerochiaro> zsombi: i might have asked you already, but do you know if there's a way to know at what Y coordinate a delegate is inside a listview ?
[15:27] <zsombi> nerochiaro: the list items are placed onto the contentItem, so you need to map that coordinate to the ListView itself
[15:28] <nerochiaro> yeah, but how do i know where a delegate is inside the contentItem ?
[15:28] <janimo`> xnox, hi, is ro.debuggable=1 equivalent with running on emulator? I am looking at the latest change in system/core
[15:38] <xnox> janimo`: hm? no, that's not equivalent. It's just temporarily. I'll revert that soon.
[15:39] <xnox> janimo`: basically we had "console" to the ubuntu, and adbd to android. And android was launching it's own console over the top of ubuntu's when ro.debuggable=1 is set.
[15:39] <xnox> janimo`: i have now fixed "adbd into ubuntu", and we can go back to having a console for android.
[15:39] <xnox> janimo`: emulator is detected as "ro.qemu=1"
[15:40]  * xnox is just testing my adbd changes before uploading.
[15:41] <janimo`> xnox, thanks, the changelog comment and the code did not seem equivalent hence my question
[15:42] <xnox> janimo`: I see. gotcha, will try to make my changelog entries clearer. It made sense in the context I was in at the time =))))
[15:44] <janimo`> xnox, hi, is ro.debuggable=1 equivalent with running on emulator? I am looking at the latest change in system/core
[15:44] <janimo`> xnox, sorry, wrong window for up-arrow
[15:47] <cwayne_> is it known that launching a webapp can't scroll horizontally?
[15:49] <davmor2> cwayne: how are you trying to horizontally scroll?
[15:51] <nerochiaro> zsombi: ping
[15:52] <zsombi> nerochiaro: pong
[15:52] <nerochiaro> zsombi: i think you missed my previous question
[15:52] <nerochiaro> zsombi:  but how do i know where a delegate is inside the contentItem ?
[15:53] <cwayne_> davmor2, same way i do vertically, but horiztonally?
[15:54] <popey> cwayne_: hmm, i noticed that the other day with my kindle webapp but thought it was a problem their end, got an example?
[15:54] <zsombi> nerochiaro: when the ListItem's delegate gets control, it means that it is already an instantiated Component, so the component is on the contentItem
[15:54] <davmor2> cwayne: ignore me I was using maps in the browser sorry mate
[15:55] <cwayne_> popey, i was trying to make a webapp for kiwiirc and it was too wide (the network selection was off the screen to the right)
[15:55] <cwayne_> what does passing --webapp to webrowser-app actually do?
[15:56] <zsombi> nerochiaro: any other ListView delegate instance that is not on contentItem will be deleted
[15:56] <nerochiaro> zsombi: so delegate.y will give me the Y position of the delegate inside list.contentItem
[15:56] <zsombi> nerochiaro: yep, and that one you map to the ListView
[16:19] <xnox> ogra_: hm, I flash trusty-proposed onto grouper and by default there is no adbd, is that correct?
[16:19] <ogra_> no
[16:19] <ogra_> should be there
[16:20] <ogra_> ogra@chromebook:~$ adb devices
[16:20] <ogra_> List of devices attached
[16:20] <ogra_> 0046ceedca13b976	device
[16:20] <ogra_> works on mako
[16:20] <ogra_> (dont have my maguro near me atm, but i would guess there too)
[16:20] <xnox> ogra_: hm it appears only on second reboot.
[16:20] <xnox> ogra_: i wonder if it's a "getprop" race.
[16:21] <ogra_> xnox, very likely
[16:21] <ogra_> xnox, usually between mtp and adb
[16:30] <xnox> ogra_: can you test a package on mako for me?
[16:31] <ogra_> hmm
[16:31] <ogra_> xnox, what is it ?
[16:31] <ogra_> (mako is my day to day phone now ... )
[16:31] <xnox> ogra_: android-tools-adbd_4.2.2+git20130218-3ubuntu17_armhf.deb reboot and check that adbd still comes up. Maybe not =)
[16:31] <xnox> ogra_: i did test in the emulator & grouper.
[16:32] <ogra_> popey, do you have a writable mako by chance ?
[16:32] <xnox> ogra_: .... and i want saucy-proposed.
[16:32] <popey> ogra_: no, but I can do
[16:32] <xnox> ogra_: sorry, trusty-proposed.
[16:32] <xnox> popey: ah, let me get it over to you.
[16:32] <popey> my mako is on trusty-proposed
[16:32] <ogra_> popey, that would be great and save me to reinstall and re-set-up
[16:32] <popey> no problemo
[16:33] <daker> hey Kyle
[16:33] <ogra_> xnox, i am on trusty-proposed on both devices ;)
[16:33] <xnox> popey: download and install http://people.canonical.com/~xnox/repo/android-tools-adbd_4.2.2+git20130218-3ubuntu17_armhf.deb and reboot. Check that "adb shell" from a computer still works.
[16:33] <popey> kk
[16:33] <ogra_> i just dont want to have to set up and install all the click packages ahain
[16:33] <ogra_> *again
[16:33] <xnox> ogra_: =)
[16:33] <popey> i push click packages to my phone via a script
[16:34] <popey> I manually downloaded them all and just shove them en-masse to my phone ☻
[16:34]  * ogra_ looks forward to vUDS to define a proper backup tool
[16:34] <popey> +1
[16:35] <popey> ogra_: if i phablet-flash ubuntu-system -d mako, will that wipe my data then?
[16:35] <popey> (after going rw)
[16:36] <ogra_> popey, i think so
[16:36]  * popey will test and file a bug if it does
[16:36] <ogra_> there is a bug open iirc
[16:36] <popey> ooh?
[16:36] <ogra_> but i forgot the subject or number :(
[16:36] <popey> heh, nvm, I'll find it ☻
[16:36] <popey> hows the cat?
[16:36] <ogra_> sergiusens, do you remember ? ^^^
[16:37] <sergiusens> popey, ogra_ yes
[16:37] <ogra_> popey, still waiting that she gets up after the stressful vet visit ... then we'll see if she eats
[16:37] <popey> awww
[16:37] <sergiusens> popey, ogra_ I'm working on something for that now
[16:37] <popey> xnox: fyi, dpkg -i that package kicks me off the phone and I get get back in via adb
[16:37] <ogra_> (she is super hungry, but cant keep it in since  fri.)
[16:37] <xnox> popey: that's ok. reboot. and make sure adb still works.
[16:38] <popey> k
[16:38] <popey> \o/ saved by the terminal app ☻
[16:39] <popey> xnox: yup, adb shell still works
[16:39] <ogra_> how about after reboot ?
[16:39] <xnox> popey: ok, good.
[16:39] <ogra_> and does mtp still work too
[16:40] <popey> both work
[16:40] <ogra_> good
[16:40] <ogra_> even after a fresh boot ?
[16:40] <popey> alan@deep-thought:~$ adb shell
[16:40] <popey> root@ubuntu-phablet:/# uptime 16:40:20 up 1 min,  1 user,  load average: 1.95, 0.87, 0.33
[16:40] <popey> ☻
[16:40] <ogra_> yay
[16:40] <popey> xnox: anything else before I reflash?
[16:41] <xnox> popey: that's it thank you.
[16:41] <xnox> =)
[16:41] <popey> kk, np
[16:41] <ogra_> xnox, you should probably also check with plars and doanac ... since they are thw biggest adb consumers here
[16:42] <ogra_> (UTAH relies on some stuff working in adb)
[16:44] <plars> xnox: I can give it a try
[16:44] <doanac> what's the nature of the change?
[16:44] <xnox> doanac: enabling adbd over /dev/qemu_pipe for the emulator: http://paste.ubuntu.com/6319185/
[16:44] <xnox> plars: ^ diff
[16:45] <xnox> plars: doanac: cross-built package http://people.canonical.com/~xnox/repo/android-tools-adbd_4.2.2+git20130218-3ubuntu17_armhf.deb
[16:45] <plars> xnox: it kicked me out when I installed
[16:45] <plars> xnox: hopefully it completed?
[16:45] <xnox> plars: correct, should work fine at reboot.
[16:45] <ogra_> oh man, that code is so awfully patched all over the place
[16:46] <xnox> ogra_: plars: the upstart job is stopped and restarted on upgrade =/
[16:46]  * ogra_ looks forward to have udb one day :)
[16:46]  * plars restarts
[16:46] <xnox> hence it kicks the person out.
[16:47] <ogra_> well, you want the new binary to be used after upgrade i guess
[16:47] <ogra_> how does ssh handle that btw
[16:47] <xnox> ogra_: but killing existing connections is not nice. ssh does not kill active connections across restart.
[16:48] <xnox> ogra_: and it doesn't stop in preinst, it does restart in postinst.
[16:48] <ogra_> so it keeps a potential insecure binary in use despite me having the security fix installed ?
[16:48] <xnox> ogra_: i'm not sure, ask ssh maintainer =)
[16:48] <ogra_> heh
[16:48] <plars> xnox: I haven't played much with mtp, but it still kicks me out of the adb session when mtp attaches, and when I tried to actually browse files, I got a segfault from gvfs when I tried to unmount
[16:49] <plars> xnox: I can't say for sure if that's a new thing or not though
[16:49] <ogra_> plars, yeah, thats a bigger thing
[16:49] <ogra_> we need to redesign the property handling there
[16:49] <plars> xnox: otherwise adb seems to work ok for me though
[16:49] <ogra_> for both actually
[16:49] <xnox> plars: ack, thanks.
[16:50] <xnox> stgraber: so the android-emulator in the archive is a bit bust, but the *generic* images are ok in it.
[16:50] <xnox> stgraber: at the moment my "sdcard" build script is this:
[16:50] <xnox> stgraber: http://paste.ubuntu.com/6319243/
[16:51] <xnox> which is quite crude. I'd rather boot the emulator once into recovery with "system image files in places where systemimages expect them"
[16:51] <xnox> stgraber: and let it deploy everything onto my empty "ext4" formatted sdcard labeled USERDATA.
[16:51] <ogra_> xnox, whats crude about it ...
[16:52] <xnox> stgraber: what would be the next step to enable system-image updates?
[16:52] <xnox> ogra_: it's not a readonly system-image update ;-)
[16:53] <ogra_> xnox, just delete line 27 then :P
[16:53] <xnox> ogra_: and downloading a tarball over http with no verification what's-so-ever.....
[16:53] <ogra_> xnox, you would be a king with that script on xda devellopers (or other embedded linux fora)
[16:54] <xnox> ogra_: because of sh, instead of "bash" and "set -e, set-x" ?
[16:54] <xnox> =))))
[16:54] <ogra_> haha, yeah
[16:54] <ogra_> and because it might actually work afterwards
[16:55] <stgraber> xnox: hmm, so you should probably switch that script from shell to python and then have it do something similar to phablet-flash where it grabs system-image.ubuntu.com/<channel>/<device>/index.json, looks for the last full image and grab the rootfs from there
[16:55] <stgraber> as the rootfs published on cdimage.u.c isn't the same as what's published on system-image.u.c
[16:57] <stgraber> xnox: though that script looks like a good first step. I was talking with slangasek about this a few days back, and I guess we'll probably have to patch the emulator a bit to behave like we want... basically having the emulator let us specify a partition number for the boot image and for the recovery image, implement the boot/recovery switch and have it understand the abootimg format.
[16:58] <stgraber> doesn't sound exactly trivial to do, but we'll need that if we want our emulator to be vaguely close to reality
[16:58] <ogra_> stgraber, why do we need the recovery image ?
[16:58] <stgraber> (once we have that, we can generate an mmc image with a working recovery partition and pre-populated cache partition, have the emulator boot that and the rest will get setup just as it would on hardware
[16:58] <stgraber> ogra_: for the upgrader
[16:59] <ogra_> ah
[16:59] <ogra_> how about a partitioned img then ?
[16:59] <ogra_> with proper labeling etc ...
[16:59] <ogra_> sounds easier than having to patch the android code
[16:59] <stgraber> yep, that's what I suggest above, have one massive .img which contains the standard gpt partition layout
[17:00] <stgraber> then patch the emulator to deal with that properly, telling it what's the boot partition, what's the recovery partition and have it implement the firmware bit to allow flipping between the two (what reboot -f recovery does)
[17:01] <ogra_> oh, that needs to be patched in ?
[17:01] <xnox> stgraber: a poorman's "abootimg" support is unpack abootimg and specify -kernel vmlinuz -boot initramfs command-line args.
[17:01] <ogra_> i would have ecxepected this to be the standard
[17:01] <stgraber> ogra_: yeah, the emulator doesn't support that...
[17:01] <ogra_> ouch
[17:01] <stgraber> xnox: sure, but that doesn't let you do the reboot -f recovery magic which we need for updates
[17:02] <xnox> ogra_: emulator does direct kernel + initramfs boot, there is no boot/recovery partitions by default.
[17:02] <stgraber> xnox: and it doesn't let the device update its boot/recovery partitions from the booted system, which we need too
[17:03] <xnox> stgraber: and to get my images to be downloadable with phablet-flash, I should publish abootimg with my emulator?
[17:07] <stgraber> xnox: so ideally the emulator would take two parameters that'd be GPT labels for the boot and recovery partition. Those would be in the usual abootimg format, so the emulator would know how to read those too. phablet-flash in this world would just create the disk image with the right parition layout and dump the content of the recovery and cache partition in there before starting the emulator in recovery mode.
[17:08] <xnox> stgraber: i think at the moment it takes 4 .img files, jams them together, and represents them as a single MTD device with 4 labels/partitions, which also means using yaffs2 filesystem.
[17:09] <xnox> stgraber: there is also an sdcard support, which simply takes a single .img file. But i don't think it knows how to boot of the sdcard.
[17:10] <xnox> i'll check, but it might be an easy shim / chain initrd from the mtdblock device onto partitions of the sdcard.
[17:10] <xnox> stgraber: w.r.t. reboot there is a special pipe device in the emulator over which one can request to "reboot itself"
[17:11] <stgraber> xnox: yeah, my issue there is that I'd rather not have to patch our system to special case the emulator, if we have to do that, then we can't rely on the emulator doing the same thing as hardware...
[17:11] <stgraber> xnox: do you have a vUDS session for the emulator work? sounds like something we should discuss there
[17:12] <xnox> stgraber: not yet.
[17:15] <ogra_> stgraber, ++
[17:30] <xnox> stgraber: can you explain /data /userdata to me? As far as I can tell at the moment I get no usable (RW) /data/ mounted inside the android container.
[17:32] <stgraber> xnox: /userdata is the userdata partition, which then contains an android-data directory which is bind-mounted to /android/data and is then bind-mounted inside the container as /data
[17:33] <Hashcode> ogra_ I'm trying to catch up and fix my ubuntu touch builds today :p..  does the build system repack changes to ubuntu-root now?
[17:33] <ogra_> Hashcode, the system-image step that stgraber maintains does, yes
[17:33] <xnox> stgraber: right, so i should "mkdir android-data" on my "userdata" fs.
[17:33] <stgraber> xnox: the initrd does that for you...
[17:34] <xnox> stgraber: hm.
[17:34] <Hashcode> ogra_ should I do a local_manifest change to get that or is there a doc onit?
[17:35] <Hashcode> er.. stgraber ^^ where should I look for your system-image build step change which repacks ubuntu-root during the build?
[17:35] <ogra_> Hashcode, i'm not sure the third party stuff is completely implemented yet
[17:36] <stgraber> Hashcode: lp:~ubuntu-system-image/ubuntu-system-image/server/
[17:36] <ogra_> (for third party packagers that provide their own system-image server)
[17:36] <ogra_> ah, seems it is :P
[17:36]  * ogra_ leaves that to stephane then :)
[17:36] <stgraber> ogra_: no, it's not, but he just asked about the repacking step not about running his own server ;)
[17:37] <Hashcode> stgraber: thanks
[17:37] <ogra_> heh
[17:37] <ogra_> well, repackaging wont help without server :)
[17:37] <ogra_> (or will it)
[17:37] <stgraber> xnox: all the paths listed in /etc/system-image/writable-paths are created at boot time if missing, which includes android-data
[17:37] <Hashcode> I guess the reason I'm asking is I may need to add a set of udev ules
[17:38] <Hashcode> rules
[17:38] <stgraber> ogra_: won't be terribly useful since the upgrader will reject those indeed :)
[17:38] <ogra_> yeah
[17:38] <ogra_> Hashcode, oh, thats different, file a bug against lxc-android-config and just attach the rules file
[17:38] <Hashcode> ah k
[17:39] <ogra_> i'll pull it into the next upload (assign the bug to me)
[17:39] <Hashcode> may take me a bit, I'm like 2 versions behind
[17:39] <Hashcode> Trying to play catch up
[17:39] <ogra_> yeah, no hurry
[17:39] <Hashcode> These porting docs need work!
[17:39] <Hashcode> *duck*
[17:39] <ogra_> at least in trusty the architecture shouldnt change much anymore
[17:40] <ogra_> agreed !
[17:40] <Hashcode> Yeah I went straight to trusty
[17:40] <ogra_> we kind of left it behind, it was hard even for ourselves to keep up with the pace of changes we did
[17:40] <ogra_> so the doc definitely needs love here
[17:41] <Hashcode> yeah
[17:41] <ogra_> now that the heavy lifitng is done
[17:41] <Hashcode> hopefully the pace slows down for you guys :p
[17:41] <ogra_> i doubt that
[17:42] <ogra_> but the low level architecture is done ... it wont change much anymore
[17:42] <ogra_> going from "running on top of android" to "flipped container" and then to "readonly system-image" wont happen again i hope :)
[17:42] <Hashcode> it's odd i'm getting kernel boot, and ubuntu root start, but init is stopping after /userdata mount
[17:43] <Hashcode> Oh
[17:43] <xnox> stgraber: hm, i guess i'm doing something odd. thanks a lot for pointers though.
[17:43] <Hashcode> Are we on loopback system now?
[17:43] <ogra_> for the nexus devices we are, yes
[17:43] <Hashcode> hm
[17:43] <Hashcode> My build is still putting out a flash .zip for /system.. should I worry about that yet?
[17:43] <ogra_> we keep the cdimage zips around for ports though
[17:44] <ogra_> we dont use ot test them ourselves though
[17:44] <ogra_> *or
[17:44] <Hashcode> How are you integrating the system.img now?
[17:44] <Hashcode> Just drop it in to a dir?
[17:44] <ogra_> phablet-flash drops it into the booted (and modified) recovery mode ...
[17:45] <ogra_> the rest is magic :)
[17:45] <Hashcode> I'm not using phablet-flash :/  But I see a check for it in the /userdata/system.img location
[17:45] <ogra_> yes, that lives inside the ubuntu-system.img
[17:46] <ogra_> in fact the code below that check is what makes our loopback setup work (assuming you look at the initrd touch script)
[17:47] <ogra_> if i were you i would firstz try to get up to date with the old flipped model though
[17:48] <ogra_> there are plans to enable ports to use system-image as well but as stgraber said above, thats not done yet, so you wont have much benefit from using system-image
[17:48] <Hashcode> yeah, I'll just stick with this
[17:48] <Hashcode> right now I'm seeing a 20sec delay between the ext3 mount attempt (fail) and the successful ext4 mount
[17:49] <ogra_> wow
[17:49] <Hashcode> kind of odd
[17:49] <Hashcode> and then init stops
[17:49] <Hashcode> http://pastebin.com/raw.php?i=gTwCRhQz
[17:51] <ogra_> Hashcode, so what is it recovering for 20sec ?
[17:52] <ogra_> looks like a bad fs to me
[17:52] <Hashcode> ogra_ good question, but it does that every time.  That's the ext4 fs
[17:52] <Hashcode> Oh
[17:52] <Hashcode> hrm
[17:52] <Hashcode> I'm in recovery and it looks fine, i'll have to add some debug
[17:53] <ogra_> clearly ect4 kicks in at 3sec ...
[17:53] <ogra_> *ext4
[17:53] <Hashcode> At first I was thinking bad device location
[17:53] <Hashcode> /dev/mmcblk0p13 vs. /dev/block/mmcblk0p13 but ubuntu's /dev locations are diff
[17:53] <ogra_> thats fine
[17:53] <Hashcode> yeah
[17:54] <ogra_> everything in ubuntu will use the ubuntu location
[17:54] <ogra_> the panic is most likely not related to the fs error
[17:54] <ogra_> but rather init trying to open a console device and not finding one
[17:55] <Hashcode> yeah
[17:55] <ogra_> (upstart likes your console to be a real device ... while android gets aloing with fake ones)
[17:55] <ogra_> that will likely require some kernel config changes
[17:55] <Hashcode> I'll re-review the kernel changes too
[17:55] <Hashcode> might be something I'm missing
[17:55] <Hashcode> I mount userdata like this in the .rc file: wait noatime nomblk_io_submit,commit=20,barrier=0
[17:56] <ogra_> iirc w-flo added some info how he did that for his port to the porting doc
[17:56] <Hashcode> yeah
[17:56] <ogra_> CONFIG_HW_CONSOLE and CONFIG_VT or some such
[17:57] <Hashcode> Ah I see that
[17:57] <Hashcode> yeah
[17:57] <Hashcode>  CONFIG_VT=y and CONFIG_VT_CONSOLE=y
[18:00] <xnox> ogra_: can i schedule gcc-arm-linux-androideabi rebuild against newer gcc-4.7 sources + subsequent android rebuild & check the world does not explode?
[18:01] <xnox> it will be a bump 4.7.3-7 -> 4.7.3-8ubuntu1
[18:01] <xnox>  SVN 20130821 (r201895) & linaro  4.7-2013.08  => SVN 20131020 (r203880) & linaro 4.7-2013.10
[18:05] <ikdus> Hey! Anyone managed to get Ubuntu Touch working on a x86 device?
[18:06] <ogra_> xnox, sounds safe, go for it
[18:15] <janimo`> ikdus, I don't think so
[18:15] <Vyom> First let Ubuntu Touch manage to run on Android *successfully* -_-
[18:15] <ogra_> there was some discussion recently to roll x86 rootfs tarballs for 14.04
[18:15] <sergiusens> barry, hey, is the best option to get the build to run system-image-cli -i?
[18:16] <ogra_> Vyom, ?? we dont run on android
[18:16] <Vyom> I meant on Nexus 7.. my bad
[18:16] <sergiusens> barry, my followup questionis, is that interface stable
[18:16] <ogra_> sergiusens, you could peek at the file this reads from
[18:16] <ogra_> sergiusens, if you want to prevent subprocess stuff
[18:17] <ogra_> it is somewhere in /etc/system-image/
[18:17] <ogra_> (was it channel.ini ?)
[18:17] <sergiusens> ogra_, it's ok, I still need to shell in or subprocess the pull somehow
[18:22] <Guest82401> Hi all!
[18:22] <Guest82401> Here is Russian?
[18:23] <ikdus> ogra_: Are they available anywhere?
[18:23] <Guest82401> Advise what to put Ubuntu on the tablet iros PD10?
[18:24] <ikdus> ogra_: I menan, those tarballs
[18:24] <ikdus> *mean*
[18:24] <ogra_> ikdus, sure on cdimage.ubuntu.com
[18:24] <ogra_> ikdus, oh, you mean the x86 ones
[18:24] <ogra_> no, there was only discussion about potentially producing them
[18:24] <ikdus> Aw..
[18:25] <Guest82401> ???
[18:25] <ogra_> 14.04 is the april release
[18:25] <ogra_> (04, 2014)
[18:27] <Guest82401> Advise what to put Ubuntu on the tablet viewpad 10 pro?
[18:27] <Guest82401> help me plees!!!!
[18:27] <killer_hobo> Hey there, not sure if this is the place to say it, but anyways: I've tested Touch on a brand new Galaxy Nexus, with literally nothing on (no SIM, no screen, no WiFi, no open apps). The battery was empty approx. 22 hours later. Another serious problem is that the UI is super slow and jittery.
[18:29] <oreneeshy> rsalveti: hello
[18:30] <Guest82401> Recommend this what Linux install?
[18:32] <Guest82401> ubuntu for touch screen is for the x86 platform?
[18:32] <oreneeshy> ogra_: HI
[18:32] <Guest82401> ку ку
[18:32] <Mathis> Hi everyone !
[18:33] <killer_hobo> Guest82401: To check if your device is already supported, see: https://wiki.ubuntu.com/Touch/Devices
[18:33] <janimo`> ogra_, are there any pointer to the talks about 14.04 x86 prebuilt images?
[18:34] <barry> sergiusens: sorry i don't understand the first question
[18:35] <barry> sergiusens: system-image-cli --info doesn't have a guaranteed output format, but i predict that the general format of "keyish thing: value" will not change.
[18:36] <sergiusens> barry, ack, I just want something I can programatically query to know I'm already running an upgradeable image
[18:36] <Guest82401> I saw this list! I wonder whether there is another platform for x86? or will there ever be?
[18:36] <sergiusens> barry, any suggested key or any other option?
[18:36] <kichuku> Hi all
[18:37] <barry> sergiusens: if you want/can use dbus, call .Info() on s-i-dbus.  at least that has a format that will only be extended in a backward compatible way (or more accurately, new values added to the end of the signature).
[18:37] <barry> sergiusens: but for all practical purposes, s-i-cli --info won't change any time soon... unless there's info you need that's missing!
[18:38] <kichuku> Any of you successfully using Ubuntu touch on nexus 4?
[18:38] <sergiusens> barry, nothing is missing; I just don't want phablet-flash to break along the way :-)
[18:38] <barry> :)
[18:39] <barry> sergiusens: so far, no plans to change --info
[18:39] <sergiusens> barry, great, that's all I need to know :-)
[18:40] <sergiusens> barry, I can do dbus too  btw if that feels cleaner to you
[18:42] <barry> sergiusens: no preference from me!  whatever works best for you is fine
[18:50] <Hashcode> ogra_ what sets $device?
[18:52] <sergiusens> popey, ogra_ doanac can you check https://code.launchpad.net/~sergiusens/phablet-tools/1218270/+merge/192927
[18:53] <mterry> ogra_, is there a way to get more space in my root partition on the phone?  I've installed a lot of -dev packages and such, and I'm running out of space
[18:58] <popey> sergiusens: sure, will test here
[19:00] <Hashcode> ogra_ I'm seeing a lot of "init: lxc-android-boot main process (343) terminated with status 1" type messages.. where can I look to debug that?
[19:01] <kirkland> so I installed Ubuntu Touch about a month-and-a-half ago;  now, I'd like to update it to pull down the GA release
[19:01] <kirkland> can I do that using the system update?  or do I need to phablet flash it?
[19:02] <popey> kirkland: you probably have the cdimage-touch version if it's that old
[19:02] <popey> kirkland: adb shell system-image-cli -i
[19:02] <popey> does that return something sane?
[19:02] <popey> http://paste.ubuntu.com/6319959/ like that
[19:07] <ainen> Has anyone built for m7ul successfully? I'm having issues.
[19:11] <oreneeshy> sergiusens: hi
[19:11] <ainen> hello
[19:11] <doanac> sergiusens: playing with branch now
[19:12] <sergiusens> oreneeshy, hey!
[19:12] <oreneeshy> sergiusens: :-)
[19:12] <oreneeshy> sergiusens: installing utouch on an n7
[19:12] <oreneeshy> performance is really crap
[19:13] <oreneeshy> sergiusens: any package somewhere that can improve?
[19:13] <sergiusens> oreneeshy, that's mir; adb shell rm /home/phablet/.display-mir; adb reboot
[19:14] <sergiusens> doanac, thanks
[19:14] <oreneeshy> sergiusens: trying
[19:15] <popey> sergiusens: so if I reflash with phablet-flash from https://code.launchpad.net/~sergiusens/phablet-tools/1218270/+merge/192927 it won't wipe my data?
[19:16] <oreneeshy> sergiusens: nice thanks
[19:17] <sergiusens> popey, that's the point; unless you explicitly say --bootstrap
[19:18] <popey> ok, will test
[19:18] <ogra_> mterry, i fear not, stgraber might know a way
[19:18] <sergiusens> popey, the data partition isn't formatted if you are already on an upgradeable image
[19:19] <popey> kk
[19:19] <stgraber> mterry: you'll need to dd some extra space at the end of /userdata/system.img, then do a resize2fs
[19:20] <ogra_> stgraber, we should provide a tool for that ;)
[19:20] <ogra_> once we have all that spare time and dont know what else to do ;)
[19:20] <stgraber> right :)
[19:21] <ogra_> Hashcode, you need /system mounted
[19:22] <mterry> :-/
[19:22] <ogra_> Hashcode, there should be logs in  a) /var/log/lxc/ and b) in /var/log/uptstart/
[19:23] <Hashcode> yeah I'm looking through the upstart logs now
[19:23] <ogra_> Hashcode, there is an lxc-android-boot upstart job that creates an fstab entry for /system usually (if your partition label is known)
[19:23] <Hashcode> it kept looking for my udev rules
[19:23] <ogra_> ah, yeah
[19:23] <Hashcode> I didn't realize it needed to go into /usr/lib/lxc-android-config/
[19:24] <ogra_> yeah, it would be better if we could  just generate them on the fly from ueventd.rc ...
[19:25] <ogra_> but sadly android isnt very reliable in that area, it chowns and cmods files in /dev all the time from its init scripts
[19:25] <Hashcode> ah
[19:25] <Hashcode> also seeing some mountd-proc errors
[19:25] <Hashcode> "chmod: cannot access '/proc/slabinfo': No such file or directory"
[19:25] <Hashcode> so I need to turn that on in the kernel
[19:25] <ogra_> which means human intervention is needed to adjust the stuff manually
[19:26] <Hashcode> I think I have slub currently
[19:26] <ogra_> ah, yeah
[19:29] <ogra_> heh, that looks like someone pulled the plug in oakland
[19:46] <Bray90820_> Why would i get a status 7 error while trying to install a phablet flash
[19:46] <Bray90820_> sorry if i said that wrong
[19:51] <sergiusens> Bray90820_, what do you mean?
[19:53] <Bray90820_> i am trying to install ubuntu touch but but it fails with status 7
[19:53] <Bray90820_> using the phablet flash method
[19:53] <sergiusens> Bray90820_, what are you running?
[19:55] <Bray90820_> what phone?
[19:55] <Bray90820_> sergiusens: do you mean what phone
[19:56] <sergiusens> Bray90820_, I'm not sure what you mean with _method_
[19:56] <Bray90820_> Phablet flash
[19:56] <Bray90820_> do you know what phablet flash is
[19:56] <sergiusens> Bray90820_, phablet-flash with no arguments doesn't work
[19:56] <sergiusens> Bray90820_, yes, my name is on most of the commits
[19:56] <Bray90820_> what do you meanby that
[19:57] <sergiusens> Bray90820_, what are you running? phablet-flash ubuntu-system; phablet-flash cdimage-touch ?
[19:57] <sergiusens> Bray90820_, can you pastebin the output logs?
[19:57] <Bray90820_> from cwm?
[19:58] <sergiusens> Bray90820_, let's start from scratch, can you tell me exactly what you are doing, step by step and be very verbose?
[20:01] <Bray90820_> I downloading the ubuntu cdimag and the cm 10.1 image i needed and put them on my SD card I boot my phone into CWM wipe data flash cm 10.1 everything wrks fine  then I try to flash the ubuntu cdimg and i fails with status 7
[20:03] <Henk_> hey guys, Ive messed up my nexus 4 and just have the bootloader left...it doesnt let me add any custom software by sideload and it wont boot ubuntu tough after factory reset... any ideas?
[20:03] <sergiusens> Bray90820_, so you are not really using phablet-flash at all
[20:04] <Bray90820_> the cdimage can't be installed through cwm
[20:04] <Bray90820_> ?
[20:04] <sergiusens> Byeither that or expand on this " then I try to flash the ubuntu cdimg and i fails with status 7"
[20:06] <Bray90820_> i go install zip from sd card select ubuntu cdimage it tries to fkash it but then it stops with status 7
[20:06] <sergiusens> Bray90820_, did you flash the device zip first and then the ubuntu zip?
[20:06] <sergiusens> Bray90820_, so to confirm, you are not using phablet-flash or _the_ phablet-flash method
[20:06] <Bray90820_> i assume by device zip you mean the cm zip
[20:07] <sergiusens> Bray90820_, no, unless you got it from one of the ports
[20:07] <sergiusens> Bray90820_, this is not an android add-on
[20:07] <Bray90820_> sergiusens: on the wiki it gves me the cm image and the cdimage
[20:07] <sergiusens> Bray90820_, which device?
[20:07] <sergiusens> Bray90820_, and wiki link
[20:08] <Bray90820_> it's the tmobile g2/HTC vision/desire z
[20:08] <Bray90820_> it's labeled as desire z on the wiki
[20:09] <Bray90820_> and as to my knowledge i need to flash the cm image first then the ubuntu image
[20:09] <Bray90820_> https://wiki.ubuntu.com/Touch/Devices
[20:14] <Hashcode> ogra_ I can see my system part get mounted, but when init.*.rc runs all my services are coming back "cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'".. seems like something isn't mapping correctly?
[20:18] <Henk_> could someone help me out with a backup.ab for a nexus 4?
[20:18] <sergiusens> Bray90820_, have you tried phablet-flash community --wipe -d vision
[20:18] <sergiusens> Bray90820_, like stated here? https://wiki.ubuntu.com/Touch/Devices/flipped_vision
[20:19] <Bray90820_> I have not
[20:20] <Bray90820_> I prob should
[20:21] <Bray90820_> how would i d the phablet-flash community --wipe -d vision
[20:22] <Bray90820_> Could i just format /data and/cache
[20:25] <Bray90820_> sergiusens: Could i just format /data and/cache
[20:30] <Bray90820_> Here is something i never thought about
[20:31] <Bray90820_> maybe the Desire z version doesn't work on the G2
[20:38] <Bray90820_> Anyways i'm gonna get going
[20:38] <Bray90820_> see you later
[20:50] <bzoltan> chwatson: I made a .click with Zoltan instead of Zoltán and it works fine
[20:58] <fishscene> Just flashed my Nexus 7. VERY pleased to see the screen flashing issue has been resolved. I can't seem to find the bug report, so I'd like to say Thanks to the person(s) who resolved that issue. \:D/
[21:26] <Hashcode> ogra_ how do I adb into the android shell now?
[22:01] <kirkland> popey: http://paste.ubuntu.com/6320803/
[22:01] <popey> kirkland: thats quite an old image
[22:02] <ogra_> thats no system image
[22:02] <kirkland> popey: so there's no apt-get upgrade that can take me from there to GA?
[22:03] <Hashcode> ogra_ I think I have most of this working, but /system fails to mount in the lxc, and I can't seem to adb into  the container to see whats up
[22:04] <popey> kirkland: no, you need to reflash
[22:04] <kirkland> popey: okay, so I should just blast this one entirely and start anew?
[22:04] <kirkland> lovely
[22:04] <ogra_> Hashcode, /system/bin/logcat works from ubuntu
[22:04] <popey> yeah, phablet-flash ubuntu-system --channel trusty
[22:04] <ogra_> kirkland, apt and dpkg are dead technology on the phone :P
[22:05] <Hashcode> ogra_ right all of the services in the lxc are stopped because the bins can't be found (during init)
[22:05] <popey> \o/ killing all the things
[22:05] <Hashcode> Oct 28 21:37:07 ubuntu-phablet kernel: [    7.263304] fs_mgr: Cannot mount filesystem on /dev/block/mmcblk0p11 at /system
[22:05] <Hashcode> Oct 28 21:37:07 ubuntu-phablet kernel: [    7.263335] init: fs_mgr_mount_all returned an error
[22:05] <kirkland> ogra_: I know, I was kidding about that :-)
[22:05] <ogra_> we only use them to build the image ...
[22:05] <Hashcode> ogra_ but /system is mounted by ubuntu
[22:05] <kirkland> popey: trusty?  why not saucy?
[22:06] <Hashcode> so on the android side, it's "waiting for Surfaceflinger" etc.
[22:06] <ogra_> Hashcode, right ... hmm
[22:06] <Hashcode> I think the boot process removes the adbd binary in android side
[22:06] <Hashcode> And that's why I'm having an issue connecting to it
[22:06] <Hashcode> on 5555, etc
[22:07] <ogra_> Hashcode, yes, you can move the code snippet out of the way in /var/lib/lxc/android/pre-start.d/
[22:07] <Hashcode> ah ok
[22:07] <popey> kirkland: saucy is dead to us ㋛
[22:08] <popey> kirkland: saucy will almost certainly get near-zero updates, trusty will get near-daily updates
[22:08] <kirkland> popey: okay, so once I'm on that, I should be able to update it easily?
[22:08] <popey> yes, over the air updates
[22:08] <ogra_> kirkland, yeah, the GUI offers you OTA updates regulary
[22:09] <kirkland> popey: ogra_: great, thanks guys!
[22:09] <popey> np
[22:09] <kirkland> popey: I'm flashed, rebooting
[22:09] <kirkland> ruh roh
[22:09] <kirkland> ERROR:phablet-flash:Command 'adb push /home/kirkland/Downloads/phablet-flash/imageupdates/pool/ubuntu-a542f511e5de48d2172a80244671b15a76a085eb6d69f16a473c514a9a4c524f.tar.xz /cache/recovery/' returned non-zero exit status 1
[22:10] <popey> is your device attached?
[22:10]  * popey pages sergiusens 
[22:10] <fishscene> I read the conversation and I'm a bit confused. I regularly flash my device using the development channel - is that the one that is being updated on a near-daily basis?
[22:11] <popey> fishscene: you dont need to flash it clean each day
[22:11] <popey> in system settings -> update you can over the air update
[22:11] <kirkland> popey: yeah;  it powered itself off;  I just powered it back on, and it's hanging on the google logo
[22:11] <popey> you _can_ flash cleanly of course
[22:11] <popey> kirkland: phablet-flash ubuntu-system --channel trusty -b
[22:11] <popey> try that
[22:11] <fishscene> I don't - just once a week, usually on Friday. But I'd like to tap into the daily.
[22:12] <ogra_> fishscene, theoretically it is, practically we wait for the first gree image on http://reports.qa.ubuntu.com/smokeng/trusty/touch/ before switching the dvel channel to trusty
[22:12] <ogra_> *green
[22:12] <popey> kirkland: i have seen it fail without -b before
[22:12] <kirkland> popey: hmm, into what state do I need to boot my device?
[22:13] <kirkland> popey: it's no longer booting into Touch, after that failed flash
[22:13] <fishscene> ok, Thanks!
[22:13] <ogra_> recovery ... but then you need to use -d mako
[22:13] <ogra_> (if thats a nexus 4)
[22:14] <Hashcode> ogra_ is there no way to chroot to the lxc? (can't adbd.. no /system/bin/sh for it)
[22:15] <ogra_> just copy it in place
[22:15] <Hashcode> oh I could push it
[22:15] <kirkland> ogra_: it is a nexus 4
[22:16] <kirkland> ogra_: I rebooted into recovery
[22:16] <kirkland> ogra_: and I'm trying "phablet-flash ubuntu-system --channel trusty -b -d mako"
[22:19] <popey> kirkland: working now?
[22:23] <thomi> barry: commented on your bug report (https://bugs.launchpad.net/autopilot/+bug/1242835).
[22:23] <thomi> barry: think the best thing to do now is to change the bug title to "Port autopilot test suites to python3" and make it affect every touch application in the rdepends list
[22:24] <thomi> but before we can land that, we need to talk to the CI team to make sure that if we depend on python3-autopilot in those packages that it'll do what we expect
[22:24] <thomi> I can do that first part.
[22:24] <barry> thomi: hi!
[22:24] <thomi> :)
[22:26] <barry> thomi: just read the comment.  yeah, i'd be willing to help, but as i've mentioned before, i just can't get the test suite to pass in *trunk* on trusty
[22:26] <barry> (autopilot test suite)
[22:26] <thomi> we should fix that.
[22:26] <thomi> I mean, it works for me, so I'd like to know what's going wrong for you
[22:26] <barry> thomi: it's the protocol mismatch problem.
[22:26] <thomi> what does 'dpkg -l | grep autopilot' show?
[22:28] <barry> ii  autopilot-desktop                                           1.3.1+13.10.20131003.1-0ubuntu1            all          Autopilot support for the ubuntu Desktop platform
[22:28] <barry> ii  libautopilot-gtk:amd64                                      1.3+13.10.20130628-0ubuntu1                amd64        Makes GTK+ applications introspectable by autopilot.
[22:28] <barry> ii  libautopilot-qt                                             1.3+13.10.20130814-0ubuntu1                amd64        This project makes Qt applications introspectable by autopilot.
[22:28] <barry> ii  python-autopilot                                            1.3.1+13.10.20131003.1-0ubuntu1            all          Utility to write and run integration tests easily
[22:28] <barry> ii  python-autopilot-trace                                      1.3.1+13.10.20131003.1-0ubuntu1            amd64        Support for tracing in autopilot
[22:28] <barry> ii  python-autopilot-vis                                        1.3.1+13.10.20131003.1-0ubuntu1            all          The visualisation application for Autopilot.
[22:28] <barry>  
[22:28] <barry> so yeah, they look like 1.3.1's
[22:28] <thomi> yeah, that's the problem
[22:28] <thomi> barry: if you feel like using the ppa, add ppa:autopilot/experimental
[22:28] <barry> thomi: maybe the 1.4 versions aren't in trusty yet?
[22:28] <thomi> I expected autopilot 1.4 to land in trusty already, but that's been held up
[22:29] <thomi> yeah
[22:29] <barry> thomi: okay, that makes perfect sense then.  the ppa has all the 1.4 versions?
[22:29] <thomi> correct
[22:29] <thomi> I believe that the problems we had that were preventing 1.4 from landing in trusty have been resolved
[22:30] <thomi> I need to follow that up this week to see what's happening there
[22:31] <barry> thomi: cool.  for now i'll add the ppa and re-run the tests, but i'm sure the results will be better.  just ping me when you know what's up with the 1.4's landing in trusty (as soon as i see them, i'll delete the ppa)
[22:31] <thomi> will do.
[22:32] <Hashcode> ogra_ so android lxc mount on system is failing "mount: Device or resource busy" have you heard of that?
[22:33] <barry> thomi:
[22:33] <barry> W: Failed to fetch http://ppa.launchpad.net/autopilot/experimental/ubuntu/dists/trusty/main/binary-amd64/Packages  404  Not Found
[22:33] <barry>  
[22:33] <barry> W: Failed to fetch http://ppa.launchpad.net/autopilot/experimental/ubuntu/dists/trusty/main/binary-i386/Packages  404  Not Found
[22:33] <barry>  
[22:33] <thomi> nuts - that's right, sorry - the PPA hasn't been seeded yet. pitti found that, and I forgot to follow up
[22:34] <thomi> just asking the CI folks to poke that PPA
[22:34] <barry> thomi: okay, no worries.  i'll let you sort all that out.  i'm nearing eod anyway :)
[22:34] <thomi> OK, lets talk tomorrow as well then
[22:34] <barry> thomi: +1
[22:36] <popey> kirkland: success?
[22:43] <sr20dett> Is there an irc app for ubuntu touch?
[22:44] <sr20dett> I dont see on in the core apps
[22:48] <popey> sr20dett: no
[23:01] <sergiusens> popey, sorry; was afk, still need me?
[23:01] <popey> dont think so
[23:02] <popey> kirkland was having problems flashing his device
[23:02]  * popey enters S3
[23:04] <Hashcode> ogra_ what process mounts /system on ubuntu side?
[23:09] <Hashcode> seems like maybe I'm missing something that bind mounts these to the lxc rootfs
[23:32] <Hashcode> Are there any repo changes for the trusty build?  Like do I need to reinit against a different manifest?