[01:17] <OrokuSaki> QUESTION =)   sudo schroot -c saucy-armhf -u root --host=armhf --build=armhf  (or should --buold me amd64)?????
[01:18] <OrokuSaki> Should build be with amd64??? I think so after some reading
[01:28] <asac> stgraber: hey, i think ... with some luck we want to punch the unity stuff in in like 30 minutes
[01:28] <asac> and then wait for proposed etc.
[01:28] <asac> are you available then to kick an image?
[01:33] <stgraber> asac: yep
[01:37] <stgraber> asac: I'll be around for another 2 hours at least, possibly a bit longer
[01:38] <asac> stgraber: ok ... hope not just for us :/
[01:39] <stgraber> asac: nah, preparing my talks for Plumbers next week and fixing some bugs in LXC
[01:46] <asac> omg - unity8 is landing :)... didrocks is pushing the button
[01:46] <asac> kgunn: ^^ :)
[01:46] <didrocks> (and crossing fingers :p)
[01:49] <cwayne_> unity8 as in, with mir?
[01:49]  * asac hopes for a good proposed tick
[01:51] <didrocks> cwayne_: yep
[01:52] <cwayne_> didrocks, :D
[01:52]  * cwayne_ crosses fingers as well
[01:53] <stgraber> so will everything just magically switch to Mir on touch? I'm surprised this isn't going to the archive with an ubuntu-touch-meta change and some changes to disable surfaceflinger in Android.
[01:56] <asac> stgraber: plan is to land everything today
[01:57] <asac> and then tomorrow folks double check that they just need to flip the atomic switch
[01:57] <asac> and upload afterareds the meta
[01:57] <asac> so no... not magic
[01:57] <asac> 21:56 < asac> stgraber: plan is to land everything today
[01:57] <asac> 21:56 < asac> and then tomorrow folks double check that they just need to flip the atomic switch
[01:57] <asac> 21:56 < asac> and upload afterareds the meta
[01:57] <asac> 21:56 < asac> so no... not magic
[01:57] <asac> today ... tomorrow is magic day
[01:59] <stgraber> k
[01:59] <asac> stgraber: so i tried the system update with todays image
[02:00] <asac> stgraber: there were issues and didnt really work (probablyu because download mangaer doesnt like this flaki hotel network)
[02:00] <asac> stgraber: howver, the diff was 166M
[02:00] <asac> isnt that pretty big?
[02:01] <stgraber> yeah, that's pretty big. What channel are you on? daily or daily-proposed?
[02:01] <asac> stgraber: i am on daily ... i hope :)
[02:01] <kgunn> asac: hells yeah!!! didrocks thank man!
[02:01] <asac> wanted to ride the "daily"
[02:02] <asac> kgunn: yeah first step ... now we want to kick an image and see green before going to bed :-P ... tomorrow is then hopefully the by-default switch
[02:02] <asac> stgraber: cant see 100+M diff
[02:02] <asac> in http://system-image.ubuntu.com/daily/maguro/
[02:03] <asac> stgraber: its really odd ... the -full has 25M only here: http://system-image.ubuntu.com/daily/maguro/
[02:03] <stgraber> asac: yeah, last delta for maguro (from 4 to 5) was 61MB total, so maybe you were more than one image behind?
[02:03] <asac> guess I dont understand how it works
[02:03] <asac> stgraber: 5 days
[02:04] <stgraber> asac: that's the full of the Android partition, the full for the Ubuntu system is in http://system-image.ubuntu.com/daily/ubuntu as it's shared between devices
[02:04] <asac> maybe 10 proposed images
[02:04] <asac> oh
[02:04] <asac> ic
[02:04] <asac> hnmm
[02:04] <stgraber> asac: can you do: adb shell system-image-cli -i ?
[02:04] <asac> stgraber: i dont see the 166M or so
[02:04] <asac> at all there
[02:04] <asac> ok let me try
[02:05] <asac> hmmm
[02:05] <asac> stgraber: system-image-cli -i
[02:05] <asac> current build number: 28
[02:05] <asac> device name: maguro
[02:05] <asac> channel: daily-proposed
[02:05] <stgraber> asac: right, the only way you can get to 166MB is with multiple deltas and the only way that should be possible is if you're on daily-proposed instead of daily, 3-4 days of daily-proposed would explain that delta
[02:05] <asac> guess i wanst on daily :/
[02:05] <asac> guess that makes sense
[02:05] <stgraber> ok, good, that makes sense then :)
[02:05] <asac> stgraber: can i install the previous and try the update from daily?
[02:05] <asac> stgraber: would like to try that tomorrow (and then stick on daily)
[02:06] <stgraber> asac: yes, you can flash an old daily with: phablet-flash ubuntu-system --revision=-2
[02:06] <stgraber> asac: that will flash the device with the before last image in the daily channel, then you can update from that to the latest in the UI
[02:07] <asac> stgraber: -2? not -1?
[02:07] <stgraber> -1 would give you the last image
[02:07] <stgraber> (it's a list index, so -1 is the latest image, -2 is the one before that, ...)
[02:07] <asac> stgraber: i want the image before the one we just pushed
[02:07] <asac> stgraber: :)
[02:07] <asac> ok
[02:08] <asac> stgraber: i somehow feel -1 would make more sense still :)
[02:08] <asac> for an enduser lik me
[02:08] <asac> hehe
[02:08] <asac> but all good ... dont worry
[02:08] <stgraber> end users usually want the latest which is the default :)
[02:09] <asac> i said "an end user like me" ... which probably is not the standard end user
[02:10] <asac> stgraber: will do that the reflash and upgrade test tomorrow at the office... wifi is too bad  here
[02:11] <asac> ok ... of course unity is stuck in proposed for a bit
[02:12] <asac> okay another hour :)
[03:09] <bzoltan> asac: seb128:  it is not so that I have not done testings. All last week I hardly did anything else but testing and discovering the autopilot testability. I am tracking my results here: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjIHgoRj36gldDlqM1lORHpxd2NUMi1ZSGNrVTZaQXc#gid=0
[03:10] <bzoltan> asac: seb128:  let me explain that... I have used 4 different base to test: (1) cdimage-touch, (2) pending cdimage-touch, (3) cdimage-touch upgraded from saucy, (4) cdimage upgraded from SDK PPA
[03:11] <bzoltan> asac: seb128:  I was mostly focusing on the gallery, notes, browser apps to test with their own autopilot tests to see how the different images and different UITK behaves.
[03:13] <bzoltan> asac: seb128:  to be precise, I could never reproduce the same test results on two of these 1-4 combinations. Never, not even once... latest when the gallery app give green light on pending cdimage and I installed our PPA release UITK it failed... I force removed the UITK and reverted to the version what was on the image and the tests _failed_
[03:14] <bzoltan> asac: seb128:  I was holding back UITK MRs because I could not prove that they do not break the tests... even if it is obvious that the UITK has nothing to do with the failures.
[03:16] <bzoltan> asac: seb128:  I have flagged this situation out to bfiller and pmcgowan... I have no idea how the Jenkins and the http://reports.qa.ubuntu.com dashes execute their tests... but on a Saucy Ubuntu destop PC the  phablet-test-run test executions do not give reliable results and so  the SDK cannot be verified with this tool before sending MRs
[03:21] <asac> bzoltan: run it on the phone
[03:21] <asac> its not true what you say... just try
[03:21] <bzoltan> asac: these tests are run on th ephone
[03:21] <asac> harder
[03:21] <bzoltan> asac: :) you kidding right?
[03:22] <asac> no i am not
[03:22] <asac> people say that all the time
[03:22] <asac> and in the end it turns out it was reliable ... in almost all cases
[03:23] <bzoltan> asac: I got the logs in that sheet ...
[03:24] <asac> bzoltan: which sheet?
[03:24] <bzoltan> (2013-09-11 06:09:48)
[03:24] <bzoltan> asac: seb128:  it is not so that I have not done testings. All last week I hardly did anything else but testing and discovering the autopilot testability. I am tracking my results here: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjIHgoRj36gldDlqM1lORHpxd2NUMi1ZSGNrVTZaQXc#gid=0
[03:24] <asac> not sure what that means
[03:24] <bzoltan> asac: seb128:  let me explain that... I have used 4 different base to test: (1) cdimage-touch, (2) pending cdimage-touch, (3) cdimage-touch upgraded from saucy, (4) cdimage upgraded from SDK PPA
[03:24] <bzoltan> asac: seb128:  I was mostly focusing on the gallery, notes, browser apps to test with their own autopilot tests to see how the different images and different UITK behaves.
[03:24] <bzoltan> asac: seb128:  to be precise, I could never reproduce the same test results on two of these 1-4 combinations. Never, not even once... latest when the gallery app give green light on pending cdimage and I installed our PPA release UITK it failed... I force removed the UITK and reverted to the version what was on the image and the tests _failed_
[03:25] <bzoltan> asac: I am not sure if you have received these lines
[03:25] <asac> nope
[03:25] <asac> let me try to decipher
[03:25] <bzoltan> asac: I put them in private message too
[03:26] <asac> bzoltan: which image did you try against?
[03:26] <asac> (which day?)
[03:26] <bzoltan> I have used 4 different base to test: (1) cdimage-touch, (2) pending cdimage-touch, (3) cdimage-touch upgraded from saucy, (4) cdimage upgraded from SDK PPA
[03:26] <bzoltan> asac:  ^
[03:27] <bzoltan> which day? That is what I am doing every day...
[03:27] <bzoltan> for about a week now
[03:27] <asac> let me check something
[03:27] <bzoltan> asac:  since the SDK broke the Gallery app I forced the SDK team to start using these autopilot tests before MRs
[03:27] <asac> right
[03:28] <bzoltan> asac: I am logging all output and checking all combinations ... not sure if I should be called liar :)
[03:30] <bzoltan> asac:  The tests procedure I expect to work is to flash the device with cdimage/pending and get an OK result with phablet-test (on device of course)... install the UITK MR and run the same tests... I have never got OK results ... even if the UITK clearly does not break anything
[03:30] <asac> bzoltan: sorry, i am surely not saying you are a liar
[03:31] <bzoltan> asac: sorry, I interpreted this * (2013-09-11 06:21:25) asac: its not true what you say...  * that way ... I have difficult days.
[03:31] <asac> bzoltan: was trying to say that loads of folks said that and in the end it evapored
[03:32] <asac> and they can happily reproduce
[03:32] <asac> i suspect in oyur case you might have been unlucky with the images you based on
[03:32] <asac> e.g. they might have been busted with crashes - which cause flakiness
[03:32] <asac> e.g. if you start serializing a .crash file
[03:32] <asac> etc.
[03:32] <bzoltan> asac: very possible
[03:32] <bzoltan> asac: that is why I was looking for the right image to get green tests on stock image
[03:33] <asac> right
[03:33] <asac> so we managed to hit green finally on todays image again
[03:33] <asac> after backing out landings that caused all those crashes
[03:33] <bzoltan> asac: true that the pending gives different test results
[03:33] <asac> bzoltan: if you would be willing to give that one more try that would be all i can ask for... if you still see that send me the logs and i will go and try myself again
[03:34] <asac> bzoltan: dont try all autopilots
[03:34] <bzoltan> asac: no problem
[03:34] <asac> bzoltan: we really need to solve so you can run the tests
[03:34] <bzoltan> asac: I am starting with the gallery lately ... that one and the browser are the two most rich test set
[03:34] <asac> bzoltan: http://reports.qa.ubuntu.com/smokeng/saucy/image/4142/
[03:35] <bzoltan> asac:  I know, I am desperate to get it fixed... I have not done much else lately
[03:35] <asac> ask for help earlier :)
[03:35] <bzoltan> asac: I can not test on RO image
[03:35] <asac> right
[03:35] <asac> bzoltan: http://reports.qa.ubuntu.com/smokeng/saucy/image/4143/
[03:36] <asac> thats the RW image
[03:36] <asac> it had ZERO hand holding from anyone in recent days
[03:36] <bzoltan> asac:  I told it to Bill and to Pat and to Gunther
[03:36] <bzoltan> asac: OK, I will re run my tests on that
[03:36] <asac> so there is away that you can 100% run it like we run it in utah
[03:37] <asac> including provisioning the phone, botting it etc.
[03:37] <asac> bzoltan: so if you see stuff in /var/crash after the tests
[03:38] <bzoltan> aac: Is this 20130910.2 now the one what comes as cdimage-touch ?
[03:38] <asac> bzoltan: flakiness can happen because timing is key in autopilot and such a big file write can delay stuff very very long
[03:38] <asac> e.g. if a coredump is produced
[03:38] <asac> bzoltan: yes thats the latest blessed image
[03:38] <asac> dont even need pending
[03:39] <asac> bzoltan: also not sure what you carry in your sdk ppa
[03:39] <bzoltan> aac:  cool... thanks for your advices
[03:39] <asac> what we are really interested in is to get a check on what is staged in daily-release ppa
[03:39] <bzoltan> asac: I did install  only the UITK packages
[03:39] <didrocks> asac: bzoltan: https://launchpad.net/~ubuntu-unity/+archive/daily-build
[03:40] <bzoltan> asac: that is what I want to test too...
[03:40] <bzoltan> didrocks:  thanks
[03:40] <asac> bzoltan: ok so you picked that ppa?
[03:40] <didrocks> yw ;)
[03:40] <asac> ok yeah try that
[03:41] <cyphermox> asac: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=ubuntu-ui-toolkit&field.status_filter=published&field.series_filter=
[03:43] <asac> bzoltan: so if you had the RO image installed you have to run a brute force wipe install thingy to get a good RW back
[03:43] <asac> just in case
[03:44] <bzoltan> asac:  ahh... how to do that? I had the RO on  my device
[03:44] <asac> stgraber: do you know how to use phablet-flash if you want back RW?
[03:44] <asac> just --wipe enough?
[03:44] <asac> or --do-bootstrap or something
[03:45] <asac> bzoltan: plars says its just -b (for bootstrap)
[03:45] <asac> so phablet-flash cdimage-touch -b
[03:45] <asac> bzoltan: did you do that?
[03:46] <bzoltan> asac: I am doing it rightnow
[03:47] <asac> bzoltan: maybe start with a very simple test suite
[03:47] <asac> and run it a few times
[03:47] <asac> bzoltan: maybe try share-app-autopilot
[03:47] <asac> a few times
[03:48] <asac> once thats working reliably go for something longer running
[03:48] <bzoltan>  asac:  ok
[03:49] <asac> bzoltan: reboot in between of course :)
[03:49] <asac> every test in utah gets a fresh boot (but not a fresh reflash)
[03:50] <bzoltan> asac:  ok... originally I reflashed the device between those tests
[03:50] <asac> bzoltan: though i am sure i was running stuff without reboot and had no troubles at some point
[03:50] <asac> bzoltan: yoiu dont need that
[03:50] <asac> but shouldnt hurt really
[03:51] <asac> stgraber: people are sure here that we have < 10 minutes then image kick
[04:01] <Mirv> hello
[04:10] <plars> asac, bzoltan: make sure to use --pending if you want latest
[04:34] <bzoltan> asac: same happens as before ... the gallery tests is green on the stock image, then I install the UITK from the SDK PPA and the gallery test fails ->https://pastebin.canonical.com/97322/
[04:34] <bzoltan> plars:  It is not the latest I need :) but simple anything what works for testing the UITK
[05:47] <AskUbuntu> how to install ubuntu on spice - 495 android phone | http://askubuntu.com/q/344109
[06:55] <sergiusens> cwayne, the .writable_image was merged earlier today
[06:56] <sergiusens> stgraber, asac you really want --revision -1 for (current - 1). From an implementation perspective that will grab index -2
[07:08] <dholbach> good morning
[08:08] <riddimdonkey> hello
[08:28] <riddimdonkey> what format must a usb drive be in to write an img file of live cd for mac
[08:31] <riddimdonkey> what format must a usb drive be in to write an img file of live cd for mac
[08:31] <riddimdonkey> ?
[08:31] <deiu> fat32?
[08:32] <riddimdonkey> and a fat32 usb drive will be able to be selecrted as a target disk to boot from
[08:32] <riddimdonkey> ?
[08:33] <deiu> it should
[08:36] <riddimdonkey> 	Partition Map Scheme : 	Master Boot Record 	Disk Identifier : 	disk2 	Media Name : 	Media 	Media Type : 	Generic 	Connection Bus : 	USB 	USB Serial Number : 	10092250020176 	Device Tree : 	IODeviceTree:/PCI0/EHC1@1D,7 	Writable : 	Yes 	Ejectable : 	Yes 	Location : 	External 	Total Capacity : 	3.98 GB (3,984,588,800 Bytes) 	Disk Number : 	2 	Partition Number : 	0 	S.M.A.R.T. Status : 	Not Supported   2013-09-11 01:35:50 -
[08:37] <riddimdonkey> sorry about that.  it doesnt seem to like the partion that the usb drive has on it
[08:37] <JamesTait> Good morning all, happy Hot Cross Bun Day! :-D
[08:37] <riddimdonkey> says  can not initialize disk
[10:07] <Saviq> nic-doffay, there?
[10:31] <nic-doffay> Saviq, yeah
[10:31] <nic-doffay> Saviq, hangout?
[10:31] <Saviq> nic-doffay, you missed our mtg ;)
[10:32] <Saviq> nic-doffay, did you check jounih can join?
[10:32] <nic-doffay> Saviq, one sec let me pull up my calendar.
[10:32] <Saviq> nic-doffay, you scheduled it for half an hour ago
[10:32] <Saviq> nic-doffay, and jounih didn't reply
[10:33] <nic-doffay> Saviq, you're right, I remembered 11:30 for some stupid reason, my apologies. I'll get in touch with jounih now...
[10:33] <nic-doffay> Saviq, I don't see him online...
[10:33] <Saviq> nic-doffay, indeed
[12:29] <AskUbuntu> What is "the best" Ubuntu Touch-compatible smartphone device out there (effective Sept. 2013)? | http://askubuntu.com/q/344227
[12:35] <Rhoxus> Hey, whats the proper command to make the touch image writable?
[12:36] <Rhoxus> cause touch /userdata/.writable_image didn't work for me on ubuntu terminal or adb shell
[12:37] <jdstrand> pmcgowan: hi! can you look at bug #1223850? I feel like there is a task for some qtdeclarative package but I have no idea which one
[12:38] <pmcgowan> jdstrand, yeah thats a qpa work item, was discussing with ricmm yesterday
[12:38] <pmcgowan> then we use QtDekstopServices API
[12:56] <sergiusens> ogra_, https://code.launchpad.net/~sergiusens/ubuntu-seeds/share-app--/+merge/185043
[13:03] <john-mcaleely> anyone know how to extract a screenshot from a phone?
[13:04] <rsalveti> john-mcaleely: /system/bin/screencap
[13:04] <john-mcaleely> rsalveti, thank you!
[13:04] <lool> anyone got this:
[13:04] <lool> writing 'bootloader'...
[13:04] <lool> FAILED (remote: (InvalidState))
[13:04] <lool> while trying to reflash android 4.3.3 on grouper
[13:04] <rsalveti> lool: that's interesting :-)
[13:05] <lool> I also get weird warnings like:
[13:05] <lool> ******** Did you mean to fastboot format this partition?
[13:05] <lool> rsalveti: I think I know what's going on
[13:06] <lool> it's probably refusing to install the bootloader because it might brick the device; I guess there is some test for "successfully booted recovery" or such
[13:06] <lool> hmm except boot fails
[13:07] <rsalveti> lool: try flashing 4.2.2 instead
[13:07] <lool> good idea
[13:08] <Rhoxus> anyone knows how to make ubuntu touch writable? cause touch /userdata/.writable_image didn't work for me on ubuntu terminal or adb shell
[13:12] <seb128> boiko, hey, question about the dialer-app ... is there a design document or a blueprint listing the features for v1 somewhere?
[13:13] <boiko> seb128: let me find it here
[13:13] <seb128> boiko, more specifically, are "call forwarding" and "call waiting" on that list/is that something you plan to add to the app?
[13:14] <seb128> boiko, we have it in the system settings design but I wonder if that wouldn't make more sense to be part of the dialer-app
[13:17] <sergiusens> ogra_, https://code.launchpad.net/~sergiusens/ubuntu-seeds/share-app--/+merge/185043
[13:17] <boiko> seb128: so, call forwarding I never heard anything about implementing it, so I would say it is post v1
[13:18] <seb128> boiko, awe said it was on the ofono's work list for septembre ... do you know who we should check with? pmcgowan?
[13:18] <seb128> or bfiller?
[13:19] <boiko> seb128: call waiting we might have some basic support, but probably more something like: when you are in a call and another one comes in, you have the option to ignore or answer and hangup the active one
[13:19] <boiko> seb128: bfiller I would say
[13:19] <bfiller> seb128: yes, what boiko is saying is correct
[13:19] <bfiller> no call forwarding
[13:19] <bfiller> for 13.10
[13:21] <seb128> bfiller, somebody should update the PRD, it's listed as needed for ELS and it's on the current design
[13:21] <seb128> bfiller, services tab, C-8
[13:21] <bfiller> seb128: noted, I'll talk to pmcgowan about getting it updated
[13:21] <seb128> bfiller, thanks
[13:23] <seb128> boiko, ok, so call waiting is likely to be a feature of the dialer-app?  the settings design has that screen: https://wiki.ubuntu.com/PhoneApp?action=AttachFile&do=get&target=phone-settings-call-waiting-on.png
[13:23] <seb128> boiko, would it make sense to have a gsetting key to turn the option on/off?
[13:23] <ogra_> ricmm, http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/
[13:24] <seb128> boiko, where should I open a bug report to track respecting that setting from your side? telephony-service?
[13:24] <boiko> seb128: well, starting another call probably won't be supported
[13:24] <seb128> mpt, ^ btw
[13:24] <boiko> seb128: I guess open it for the dialer-app and telephony-service
[13:24] <pmcgowan> seb128, I just added a v1 defer tab yesterday, will get there
[13:24] <seb128> mpt, should we just drop the phone panel for 13.10 since most of its content is not going to be supported?
[13:24] <seb128> pmcgowan, thanks
[13:25] <ogra_> ricmm, http://people.canonical.com/~ogra/touch-image-stats/
[13:35] <lool> rsalveti: turns out they have broken signature on the bootloader in 4.3.3 recovery images; writing 4.2.2 indeed works; writing it and upgrading from there now -- might get an updated bootloder or not, we will see
[13:37] <plars> bfiller: do you know who can look at the webbrowser failures on http://reports.qa.ubuntu.com/smokeng/saucy/image/4164/webbrowser-app-autopilot/ - I don't see osomon around
[13:38] <rsalveti> lool: interesting, cool
[13:38] <bfiller> plars: yikes, what changed?
[13:39] <ogra_> plars, we're inspecting here, it looks more like a toolkit or unity8 issue
[13:39] <ogra_> bfiller, ^^
[13:39] <bfiller> ogra_: thanks
[13:40] <ogra_> asac, didnt you say you tested on my maguro ? it doesnt boot :P
[13:43] <ogra_> in fact it fails to mouont the rootfs and sits in the initrd
[13:45] <bfiller> sergiusens: is there a new way to do phablet-network-deploy with ro image? it's not working for me
[13:45] <plars> bfiller: lots of things changed, but not webbrowser, thanks for checking on it ogra_
[13:45] <bfiller> plars: I'll run it on my device and see if I get same failure
[13:45] <ogra_> bfiller, "phablet-flash system-image"
[13:46] <ogra_> (add --no-backup if you want to wipe the device)
[13:46] <bfiller> ogra_: what about script to auto deploy networking and openssh?
[13:46] <ogra_> err
[13:46] <bfiller> already did the phablet-flash system-image
[13:46] <ogra_> bfiller, "phablet-flash ubuntu-system"
[13:46] <ogra_> (sorry)
[13:46] <plars> bfiller: the new one I think is just phablet-network
[13:46] <bfiller> ah ok
[13:46] <plars> bfiller: so you may need to update your phablet-tools
[13:47] <ogra_> to upgrade on the device run system-image-cli via adb
[13:47] <plars> ogra_: I recently discovered that even with --no-backup, if you ever made it a writable image, it's still in that case. You have to manually remove that file to make it really ro again
[13:47] <sergiusens> ricmm, https://lists.launchpad.net/ubuntu-phone/msg04035.html
[13:47] <ogra_> bfiller, we have ssh preinstalled but disabled, i havent found a proper solution for setting up the network yet
[13:47] <sergiusens> bfiller, phablet-network
[13:47] <sergiusens> bfiller, no deploy
[13:48] <ogra_> (the usb0 device that is)
[13:48] <cjohnston> ogra_: which build?
[13:48] <cjohnston> (asac here)
[13:48] <bfiller> ogra_: ack, so just adb shell access for now?
[13:49] <cjohnston> ogra_: plars installed and ran it... i was sitting right next to him
[13:49] <ricmm> timp: ping
[13:49] <ogra_> bfiller, well, i try to find a proper solution for this that doesnt break usb0 for the rest of the world ....
[13:49] <plars> cjohnston, ogra_: that was on my maguro, not ogra_'s
[13:49] <cjohnston> sure
[13:49] <ogra_> ah !
[13:49] <ricmm> timp: is it possible that some of your toolbar changes landed that could break the AP tests?
[13:49] <ogra_> phew
[13:49] <cjohnston> ogras phone didnt finish install
[13:49] <ricmm> for example http://reports.qa.ubuntu.com/smokeng/saucy/image/4152/messaging-app-autopilot/386990/
[13:49] <cjohnston> or something
[13:49] <ogra_> ok
[13:49] <cjohnston> i gave up because it looked weird
[13:49] <cjohnston> and plars offered testing
[13:49] <ogra_> tghen all is fine
[13:49] <cjohnston> so... :)
[13:50] <timp> ricmm: I hope not.
[13:50] <cjohnston> ogra_: try flashing it please if you want
[13:50] <cjohnston> if it still fails it would be interessted
[13:50] <timp> ricmm: it did last week, but that change was reverted.
[13:50]  * cjohnston hands over to cjohnston again
[13:50] <ogra_> cjohnston, well, looking at the tests i dont really feel like i would want to use that :)
[13:50] <timp> ricmm: after that I split up the MR, and only a small one landed. I tested it with notes-app, gallery-app and webbrowser-app autopilot tests
[13:50] <ricmm> take a look at that log
[13:50] <timp> ricmm: if you see something breaking, please tell me and we can have a look at it.
[13:52] <timp> zsombi: ^ look at that log. full of the binding loops that you are working on
[13:52] <timp> zsombi: http://reports.qa.ubuntu.com/smokeng/saucy/image/4152/messaging-app-autopilot/386990/
[13:53] <zsombi> timp: oh, crap!
[13:53] <zsombi> timp: I saw it has been introduced in revno 621
[13:54] <timp> zsombi: I guess it happens whenever an app updates the background color
[13:54] <zsombi> timp: than bug seems to be critical to be fixed, it may have unexpected behavior on the app functionality
[13:55] <plars> pulling up the bottom menu doesn't seem to work in any app for today's image
[13:55] <plars> ogra_: ^
[13:56] <xnox> plars++
[13:57] <mpt> seb128, it isn't?
[13:57] <seb128> mpt, <boiko> seb128: so, call forwarding I never heard anything about implementing it, so I would say it is post v1
 seb128: call waiting we might have some basic support, but probably more something like: when you are in a call and another one comes in, you have the option to ignore or answer and hangup the active one
[13:58] <stgraber> sergiusens: oh, I thought it was passing it directly as the index, ok.
[13:58] <seb128> mpt, how do you want to track those? bugs on u-s-s and ubuntu-ux for the design part?
[14:00] <asac> rsalveti: http://people.canonical.com/~ogra/touch-image-stats/20130911.changes
[14:00] <rickspencer3> plars, is it broken with Mir or SF?
[14:00] <asac> rsalveti: can you help identifying what busted the image by backing out your stuff?
[14:00] <asac> locally?
[14:00] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/4157/
[14:01] <asac> rsalveti: or look at the changes and give me a better blame idea
[14:01] <plars> rickspencer3: I think I'm on sf
[14:01] <rsalveti> asac: sorry, can you summarize the issue?
[14:01] <rsalveti> asac: sure, but hybris is a packaging change, no code change in there, so it's probably something else
[14:01] <plars> rickspencer3: yeah, I don't think we fully have mir in there yet
[14:02] <rsalveti> but I can take a look once I know what the issue is all about :-)
[14:03] <asac> rsalveti: look at the dashboard
[14:03] <asac> all those apps regressed
[14:03] <asac> rsalveti: hard to say what is causing it
[14:03] <asac> if you have ideas thats good
[14:03] <asac> if not i have to backout everything one by one
[14:03] <rsalveti> asac: did you try reverting platform-api and unity8?
[14:03] <asac> so i try to ask those that uploaded directly to do that for their part
[14:03] <xnox> "<plars> pulling up the bottom menu doesn't seem to work in any app for today's image"
[14:03] <sergiusens> asac, it's being looked into here
[14:03] <asac> sergiusens: i want to know what causd it
[14:03] <asac> not the fix
[14:03] <asac> thanks
[14:04] <asac> rsalveti: not sure... i assume ricmm should try backing out unity8
[14:04] <asac> but
[14:04] <rsalveti> from that list, I'd try reverting qtubuntu, platform-api and unity8
[14:04] <asac> rsalveti: can you tell us exactly the binary pckages?
[14:05] <asac> plars: ^^
[14:05] <asac> I think we can try two backouts
[14:05] <rsalveti> asac: plars: libplatform-api1-hybris, libubuntu-application-api1, libubuntu-platform-hardware-api1, qtubuntu-android, unity8, unity8-private
[14:06] <asac> plars: can you try that combination?
[14:06] <asac> rsalveti: can you try that?
[14:06] <asac> :)
[14:06] <asac> we can try more
[14:06] <rsalveti> asac: in a meeting here, can try in a few
[14:06] <ricmm> rsalveti: what about that?
[14:06] <asac> rsalveti: ok lets see who comes first
[14:06] <asac> ricmm: http://people.canonical.com/~ogra/touch-image-stats/20130911.changes
[14:06] <seb128> asac, hey, can we land the indicators? ;-)
[14:06] <ricmm> I know that, but what does platform-api have to do with anything?
[14:06] <asac> after i backed out everything
[14:07] <asac> that landed yesterday
[14:07] <asac> that wasnt unity :)
[14:07] <asac> j.k/.
[14:07] <asac> ricmm: i dont know
[14:07] <ricmm> the failing tests are Toolbar.opened() failing
[14:07] <asac> ricmm: look at the changes and tell us what to backout
[14:07] <ricmm> we are assessing wether it is at the unity8 level of the SDK level or other components
[14:07] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/4157/
[14:07] <ricmm> until I have that answer I cant tell you what to backout
[14:07] <ricmm> so, give us a bit
[14:07] <ricmm> before shooting stuff
[14:08] <asac> ricmm: how can you assess? you
[14:08] <asac> dont even see any real errors in the autopilots
[14:08] <ricmm> I do see them, if you take a closer look you'll see thats its all about the toolbar not coming up
[14:08] <ricmm> try it on your phone, the toolbar is a no-op
[14:08] <ricmm> never shows up, hud always does instead
[14:08] <plars> right
[14:08] <ricmm> most apps' autopilot tests depend on the toolbar
[14:08] <ricmm> thats why the large number of failures
[14:09] <rsalveti> ricmm: not saying we should backout everything on that list, I'm saying that those packages are the ones I'd first revert and give it a try
[14:09] <rsalveti> to try to isolate the issue
[14:09] <rsalveti> see if it makes any difference
[14:09] <ricmm> theres only 2-3 things that could've caused that internally to unity8/toolkit/apps
[14:09] <ricmm> so, trying each point at a time
[14:09] <ricmm> asac: where are you?
[14:09] <asac> in the CI room
[14:09] <asac> duff
[14:09] <ogra_> rickspencer3, we ship Mir but dont use it yet
[14:10] <mpt> boiko, Richard added call waiting to the ELS feature list on August 1st.
[14:10] <boiko> bfiller: ^
[14:11] <seb128> mpt, the prd has it in the "v1 defered" tba
[14:11] <seb128> tab
[14:11] <seb128> mpt, with rest/rotation/regulatory info/bluetooth/lock sound and few others ... how do you want to track those? on your design status google doc?
[14:11] <mpt> seb128, that is evidence that the tab shouldn't exist. It's duplicating and therefore inevitably out of sync.
[14:12] <ogra_> asac, let do ricmm his inspection, we are on it
[14:12] <ogra_> (since before yu guys started)
[14:12] <seb128> mpt: well, that tab just got added because we are looking at defering things we are not going to manage to do for v1
[14:12] <seb128> mpt: we have limited resources and a fixed schedule, we need to defer work
[14:12] <mpt> seb128, understood, but the rest of the PRD already has columns for when things are scheduled.
[14:13] <seb128> I wish google doc edit had an useful changes' log
[14:13] <seb128> it's hard to know what got changed and when :/
[14:14] <pmcgowan> mpt, folks were asking for an explicit list, as they could not track status changes
[14:14] <mpt> seb128, I worked out the August 1st date by bisecting the revisions. :-)
[14:14] <pmcgowan> mpt, I will update the PRD itself once that list is agreed
[14:15] <mpt> pmcgowan, ok, that makes sense. Perhaps call it "Proposed deferrals" to avoid confusion.
[14:15] <seb128> pmcgowan, thanks for the explicit list btw, I'm one of those having a difficult time seeing what changed/when, so it's useful ;-)
[14:16] <pmcgowan> mpt, I can do that
[14:16] <pmcgowan> seb128, me as well
[14:16] <cjwatson> xnox: How far did you get with cross-building a QML extension, and is it written up anywhere?  Implementing the chroot-management support for that kind of thing is pretty much next on my list for click.
[14:18] <ogra_> cjwatson, see the ubuntu-phone ML
[14:18] <cjwatson> Aha
[14:18] <xnox> cjwatson: done & published for cmake =)
[14:18] <ogra_> cjwatson, https://wiki.ubuntu.com/Touch/CrossCompile
[14:19] <cjwatson> Perfect, will review, thanks
[14:21] <xnox> cjwatson: apart from a bug in cmake, it works okish for cross-compiling with cmake. Plus a few things would be nice to get into saucy e.g. debbug 722045
[14:21] <xnox> debian #722045
[14:21] <seb128> dholbach, hey
[14:22] <seb128> dholbach, so, mpt updates the updates panel's design to include system and apps ... do you know if anyone is working on implementing that/can help on it? (you said some people were wanting to do the app update panel by then)?
[14:23] <dholbach> ralsina, ^
[14:23] <seb128> dholbach, danke
[14:23] <ralsina> seb128: I'll explain in 2' :-)
[14:24] <seb128> dholbach, rsalveti: https://wiki.ubuntu.com/SoftwareUpdates?action=AttachFile&do=get&target=phone-setting-updates-checking-existing.png
[14:25] <cyphermox> ogra_: http://paste.ubuntu.com/6092708/   <-- avahi config
[14:25] <rsalveti> awe_: ro.serialno
[14:25] <lool> dholbach: can't actually change priority of it, but I think LP #1219185 should be high and targetted at 13.10
[14:26] <dholbach> bzoltan1, ^
[14:26] <ralsina> seb128: basically, adding app updates into settings now is too hard. So we are going to do almost exactly the same UI but as a standalone app (it actually alreay exists)
[14:26] <lool> dholbach: cause we need to settle the definition of what ubuntu-sdk-13.10 is, and then remove all the --ignore-missing-framework stuff
[14:26] <lool> well, probably there's only one (in the pk click plugin)
[14:26] <seb128> rsalveti, why is it too hard?
[14:27] <ralsina> seb128: and then, once image updates are more stabilized in terms of API, didrocks and I will take care of integrating everything in a coherent form
[14:27]  * rsalveti reading
[14:27] <cjwatson> lool: We can hope.  I bet it's sprinkled all over though
[14:27] <ralsina> seb128: I assume you asked me? Because there's too tight a coupling between the settings updates page and image updates
[14:28] <seb128> rsalveti, sorry that was for ralsina
[14:28] <rsalveti> seb128: no worries :-)
[14:28] <ralsina> seb128: at least that's the veredict by didrocks and gatox, who wrote both halves
[14:29] <seb128> ralsina, shrug, what does it mean for system updates? are they moving to that standalone app? if not, what's the design for that split solution, and was mpt involved in the discussion?
[14:29] <seb128> ralsina, the design was just updated to have both in the setting, if that's not the case, what's the design for the system updates?
[14:29] <ralsina> seb128: system updates stay where they are, app updates go in a standalone app, I have tried to get mpt into the discussion, but have had little success
[14:30] <ralsina> seb128: "just updated" you mean aug 29th or is there a more recent update?
[14:30] <seb128> ralsina, shrug, so you are going for a solution which has no design?
[14:30] <ralsina> seb128: I am going for "we need to adjust the design to match what we can deliver"
[14:31] <ralsina> seb128: as an intermediate step towrds delivering the design a bit later
[14:31] <seb128> ralsina, btw I disagree it would be hard to have the click packages in the same UI, most of the work is in the backend and that would be separate files, you would just need to pack items in a list on the UI side
[14:31] <ralsina> seb128: didrocks disagrees, I have no technical opinion on the matter
[14:32] <seb128> ralsina, https://wiki.ubuntu.com/SoftwareUpdates#Phone has been updated yesterday and today
[14:32] <ralsina> seb128: sigh, checking
[14:32] <ralsina> seb128: it had broken images yesterday
[14:32] <timp> ogra_: do you know of a way to see what changed from today's stable image to today's pendin image (cdimage-touch)?
[14:32] <ralsina> mpt: ping
[14:32] <timp> boiko: ah I was also asking here
[14:32] <timp> :)
[14:33] <ogra_> timp, grab my script from http://people.canonical.com/~ogra/touch-image-stats/
[14:33] <ogra_> (see the README, you can just make it compare random manifests of images)
[14:38] <mpt> seb128, ralsina, there was an e-mail thread about it yesterday iirc, citing engineering difficulties in combining them, with the conclusion being to finish the current separate implementations.
[14:38] <ralsina> mpt: exactly
[14:38] <ralsina> mpt: can we talk about that so we find an intermediate design we can follow?
[14:39] <ralsina> mpt: we aim to provide pretty much the same UI, but the alert about updates may need to be split into "there is a system update" and "there are application updates"
[14:39] <seb128> mpt, ralsina: shrugh, I wasn't Cced on that email
[14:39] <timp> boiko: ^ see ogra's url, you can see changes there since the previous image
[14:40] <ralsina> seb128: didn't think of adding you, will do the next time
[14:40] <seb128> ralsina, thanks, can you fwd me that conversation? I'm supervision the system settings work and it's hard to know where we are going if people decide to do changes without letting us know
[14:41] <seb128> ralsina, I started some work on the new design :/
[14:41] <ralsina> seb128: sure thing
[14:41] <seb128> ralsina, thanks
[14:41] <ralsina> seb128: miscommunication :-/
[14:43] <seb128> ralsina, yeah...
[14:43] <ralsina> seb128: sent
[14:44] <mfisch> lool: I've updated the MP addressing your comments
[14:44] <mpt> ralsina, I just got done adding a lot more detail about the presentation of updates. <https://wiki.ubuntu.com/SoftwareUpdates?action=diff&rev2=139&rev1=138> If you're implementing an apps-only update utility it should be fairly easy to follow that design and just ignore the bits that are specifically about system updates.
[14:44] <ralsina> mpt: cool, that was the idea, thanks!
[14:45] <seb128> ralsina, mpt, didrocks: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1223911
[14:46] <mpt> seb128, and conversely for you to ignore all the parts about non-system updates. ;-)
[14:46] <seb128> ralsina, I still fail to see where is the implementation difficulty, it's basically another delegate/model to add to the UI
[14:47] <ralsina> seb128: ok, I am open to integrating it if you say it's doable, you'd have to talk to gatox (he's away for a little bit) he's implemented the app updates bits already
[14:48] <seb128> ok
[14:48] <seb128> ralsina, well, to me most of the work is in the backend/building the model/datas
[14:48] <Saviq> stgraber, ping
[14:48] <seb128> ralsina, the UI is basically a list of elements, packing them in a standalone qml or an integrated one should be about the same
[14:48] <ralsina> seb128: snce "plan b" of shipping a separate app is 95% done, we have a nice fallback if it turns out harder than you expect
[14:49] <seb128> right
[14:51] <ralsina> seb128: last thing about this ;-) there is a +1 from John Lea also about doing separate app as an intermediate step if needed
[14:52] <seb128> ralsina, ok, let's do that as step 1, we have all tons to do
[14:52] <seb128> ralsina, we can look at merging if there are spare cycles before release
[14:53] <ralsina> seb128: cool
[14:53] <xnox> sergiusens: ogra_: so all the webapps that are part of "webapps-demo" package are now packaged as click apps and available from the app store. (with added benefit of proper apparmor profiles for webapps)
[14:54] <pmcgowan> xnox, nice
[14:54] <xnox> sergiusens: ogra_: removing the webapps-demo seed package is easy, but I'm not sure how to propose inclusion of click apps.
[14:54] <pmcgowan> dbarth, ^^
[14:55] <xnox> sergiusens: ogra_: and wether we want them pre-installed, as they will be available out-of-the box from the click scope / searchable etc.
[14:55] <xnox> sergiusens: ogra_: that's amazon, eBay, facebook (webapp), Gmail, twitter, ubuntuone.
[14:56] <xnox> I have others in the store as well - google+, tumblr
[14:56] <xnox> and more will be comming.
[14:57] <ogra_> xnox, they just need to land at http://people.canonical.com/~ubuntu-archive/click_packages/ (and in the list file)
[14:57] <ogra_> (for bein preinstalled)
[14:58] <ogra_> xnox, sergiusens can pull them in
[14:58] <xnox> ogra_: sergiusens: right. I'll prepare URLs and file a bug against "ubuntu-seeds" to historise the request.
[14:59] <ogra_> xnox, probably ust file it against ubuntu-touch-meta
[14:59] <ogra_> *just
[15:00] <stgraber> Saviq: pong
[15:01] <xnox> ogra_: ack.
[15:01] <Saviq> stgraber, hey, did I ping you before about the idea to use a container for read-write development on the phone, while leaving the real root read-only?
[15:02] <ogra_> Saviq, how would you do that without an overlayfs ?
[15:02] <ogra_> (apart from creating a fully duplicated chroot installation for the container)
[15:04] <Saviq> ogra_, I'd be fine with both
[15:04] <ogra_> ??
[15:04] <ogra_> how do you mean both ?
[15:04] <ogra_> there is no overlayfs
[15:04] <ogra_> (and there wont be)
[15:04] <Saviq> ogra_, oh, well
[15:05] <Saviq> ogra_, full chroot would be just fine IMO
[15:05] <mfisch> lool: lets also discuss upstart when you're back
[15:05] <Saviq> ogra_, what I'm getting at is that that would greatly simplify using the device for real as well as allow developing on it
[15:05] <ogra_> Saviq, that wouldnt have access to the screen though
[15:06] <ogra_> so to test whatever you do, you would need to make the system RW  and copy over your binaries ...
[15:06] <Saviq> ogra_, why couldn't it have access to screen?
[15:06] <Saviq> ogra_, obviously we'd need to stop whatever is running on the RO part
[15:06] <ogra_> and if you do that you can as well just make the whole thing RW and dont need a container
[15:07] <Saviq> ogra_, yeah, of course, as soon as you need to mess with the RO system it beats the purpose
[15:07] <ogra_> right
[15:07] <ogra_> i'd rather like to see us improving the RW mode
[15:08] <ogra_> (or just tell people that want to do plumbing work (which is the only reason you would need such a mode)  to use the non ro image
[15:09] <Saviq> :/
[15:09] <Saviq> so no ro image for me :P
[15:09] <ogra_> right, neither for me (or most of my team)
[15:09] <elfangor> I got a nexus 4 and as soon as i have it i put ubuntu touch. Right know i have the latest current version. I start listenning music with it but i find out that the phyisical button doesn't work. Since i haven't reading they didn't work i am little afraid the problem come from my device. Anyone can make me breath? :)
[15:09] <seb128> boiko, https://bugs.launchpad.net/ubuntu-system-settings/+bug/1223924
[15:09] <Saviq> I was just under the impression that we could/should converge on the ro image, only getting out when necessary
[15:10] <Saviq> but maybe that's indeed overkill
[15:10] <ogra_> we should definitely solve the RW issues on the RO image
[15:11] <seb128> mhr3_, hey
[15:11] <ogra_> but thats unlikely to happen for 13.10
[15:11] <seb128> mhr3_, what info is useful in a bug report about desktop dash stating "no result matching your search" when opening the dash (with nothing typed in the text entry)
[15:11] <mhr3_> seb128, hey there, do you need me to point you to someone?
[15:12] <seb128> mhr3_, lol, I might :p
[15:12] <seb128> mhr3_, let's see who you find to blame this time ;-)
[15:12] <mhr3_> seb128, which scope processes are running, when does that happen (startup?), any way to repro reliably...
[15:13] <mhr3_> seb128, i'm afraid this one will be on me
[15:13] <seb128> mhr3_, it's happening in my current session, dunno if it's going to happen again (it started during the session)
[15:13] <mhr3_> so congrats you got me this time :P
[15:13] <seb128> e.g it was fine earlier
[15:13] <seb128> haha
[15:14] <seb128> mhr3_, http://paste.ubuntu.com/6092887/
[15:14] <mhr3_> seb128, yea, i saw that too at one point... wasn't able to debug it yet
[15:14] <dbarth> xnox: well, i just made them go in preinstalled with sergiusens :/
[15:14] <mhr3_> seb128, hmm... i386, you live in the past :P
[15:15] <seb128> mhr3_, indeed ;-)
[15:15] <seb128> mhr3_, the good old times
[15:15] <mhr3_> seb128, can you run `libunity-tool -s /usr/share/unity/scopes/application.scope -q "" -r`?
[15:15] <mhr3_> eh.. applicationS
[15:16] <seb128> mhr3_, http://paste.ubuntu.com/6092896/
[15:16] <dbarth> ogra_: webapps-demo can be removed though, as there's a script in the making to upload them into the preinstall list
[15:16] <mhr3_> seb128, `libunity-tool -s /usr/share/unity/scopes/applications.scope -q "" -r -t 1`?
[15:16] <ogra_> stgraber, http://paste.ubuntu.com/6092897/
[15:16] <seb128> mhr3_, http://paste.ubuntu.com/6092899/
[15:17] <mhr3_> seb128, and `libunity-tool -s /usr/share/unity/scopes/home.scope -q "" -r -t 1 --print-search-reply`
[15:17] <stgraber> barry: ^
[15:17] <ogra_> dbarth, yep, i know ... we need sergiusens for adding them, then i'll flip the seeds
[15:17] <seb128> mhr3_, http://paste.ubuntu.com/6092901/
[15:17] <stgraber> ogra_: server seems to be responding fine here, bad wireless maybe? if that's an actual bug, then it's something to do with barry's downloader code.
[15:17] <xnox> dbarth: what do you mean? at the moment only these are pre-installed - http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[15:18] <ogra_> stgraber, oh, yoou are right
[15:18] <mhr3_> seb128, so you see files, but not apps in home?
[15:18] <seb128> mhr3_, no, I see an empty home with the "no result matching your query" string
[15:18] <seb128> mhr3_, apps/file lenses are working fine
[15:18] <barry> stgraber: sorry, i don't know how far back to scrollback ;)
[15:19] <stgraber> barry: just a couple minutes :) http://paste.ubuntu.com/6092897/
[15:19] <mhr3_> seb128, not even if you change the string and then clear it?
[15:19] <stgraber> barry: though it looks like it's just a wireless issue
[15:19] <seb128> mhr3_, that fixed it :p
[15:19] <seb128> mhr3_, but I swear I tried that earlier and it didn't work
[15:19] <barry> stgraber, ogra_ yes.  that's almost definitely caused by network connectivity issues
[15:19] <mhr3_> seb128, so you see even apps now?
[15:19] <seb128> mhr3_, oh, buggy again
[15:20] <ogra_> barry, could we have a more informative error ?
[15:20] <seb128> mhr3_, yes, even apps
[15:20] <barry> ogra_: it's all going to change anyway when LP: #1196991 lands
[15:20] <ogra_> ah, k
[15:20] <seb128> mhr3_, easy to bug, I type something that has no match and esc to clear the entry
[15:20] <seb128> mhr3_, e.g just typed mhr3 and esc
[15:20] <ogra_> thanks !
[15:20] <mhr3_> seb128, hm, but yea, there's a bug there somewhere, it's just hard without being able to inspect the internal state
[15:21]  * ogra_ tries to find out why his network doesnt work ... ip and routing seem ok 
[15:21] <mhr3_> seb128, pkill -f unity-scope-home first and then try to repro
[15:21] <seb128> mhr3_, it happens every time I type something that has no exact match and esc
[15:21] <seb128> mhr3_, eg type garbage and esc
[15:21] <dbarth> xnox: yep, and the rest of the default webapps-demo ones will make it into this list
[15:21] <mhr3_> seb128, works fine here
[15:22] <ogra_> [systemimage] Sep 11 15:21:52 2013 (1560) all files available in /tmp/system-image
[15:22] <ogra_> [systemimage] Sep 11 15:21:56 2013 (1560) preparing to reboot
[15:22] <ogra_> [systemimage] Sep 11 15:21:56 2013 (1560) rebooting
[15:22] <seb128> mhr3_, I can still reproduce after killing the lens
[15:22] <ogra_> :)
[15:22] <mhr3_> seb128, in that case i will need your computer :)
[15:23] <mhr3_> seb128, when are you stopping by london? ;)
[15:25] <divis1969> trying to follow Porting Guide 2.0 but phablet-dev-bootstrap is using phablet-10.1 branch instead of phablet-saucy. Does it need to be corrected?
[15:25] <xnox> beuno: are there URLs to directly pull click apps from the store? or e.g. to predict them =0
[15:25] <seb128> mhr3_, haha
[15:25] <seb128> mhr3_, doesn't happen in a guest session :/
[15:25] <beuno> xnox, no, all downloads are authenticated with oauth
[15:26] <mhr3_> seb128, anyway, pls open a bug for libunity and unity-scope-home
[15:26] <seb128> mhr3_, my upstart log are filed with
[15:26] <seb128> (unity-scope-home:13159): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed
[15:26] <xnox> beuno: is that the reason why click apps / scope stopped working on ubuntu-touch? I guess I should login/setup ubuntu1 account?
[15:27] <mhr3_> seb128, yea, i already opened a bug about that, shouldn't have anything to do with this
[15:27] <seb128> ok
[15:27] <cwayne_> asac, so is mir in today's daily-proposed?
[15:27] <beuno> xnox, no, there's a temporary workaround to do un-authed requests, which expires on Sep 15th  (<---- ralsina)
[15:27] <xnox> beuno: right, but at the moment there is no UI to setup accounts =/
[15:27] <xnox> beuno: or specifically ubuntu1 account on ubuntu touch.
[15:28] <beuno> xnox, it's being worked on by ralsina's team, being added to Online Accounts
[15:29] <xnox> beuno: ok, cool =)
[15:29] <bfiller> sforshee: do you know who is working the issue on maguro the screen brightness continuously dims even during activity and doesn't honor the indicator setting?
[15:29] <sergiusens> dbarth, xnox what's up?
[15:30] <xnox> sergiusens: just a moment. Filing a bug with details. Will be assigned to you. Will be quicker than reading backscroll.
[15:30] <seb128> mhr3_, https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1223933
[15:31] <sergiusens> xnox, ok, seems confusing, this is better, thanks
[15:31] <seb128> mhr3_, not that when I do a query and clear it, home lists only apps
[15:31] <seb128> mhr3_, is it supposed to list files as well?
[15:31] <sforshee> bfiller: that's probably the autobrightness. We need to get a way for disabling autobrightness from the UI, but I don't know who is working on it.
[15:31] <sforshee> rsalveti, ricmm: ^
[15:32] <rsalveti> maybe seb128 knows
[15:32] <mhr3_> seb128, yes, you should see apps and files by default
[15:32] <rsalveti> otherwise it'd be in the indicator
[15:32] <sforshee> rsalveti: part of it is getting the interfaces between unity and powerd ironed out
[15:32] <bfiller> sforshee: how do I disable it from command line?
[15:33] <sforshee> bfiller: well you could run 'powerd-cli display dc disableab', but you have to keep that active
[15:33] <sforshee> I think that command is right
[15:33] <seb128> bfiller, sforshee: there is a setting panel for that but it didn't get implemented yet ... do we have a backend to enable/disable the auto mode, which one?
[15:33] <seb128> sforshee, bfiller: one issue with the powerd-cli is that it needs sudo (or did that change?)
[15:34] <bfiller> sforshee: seems like autobrightness is broken though - assuming it's enabled now and it doesn't work right
[15:34] <ogra_> cjwatson, hmm, so i have ssh on the image but starting it for the first time does not generate keys ... adding a -d to the commandline in the upstart job doesnt seem to log anything anywhere
[15:34] <sforshee> seb128: the interface for communicating setting to powerd isn't defined yet. A display request could be used for it
[15:34] <bfiller> at least on maguro it's quite broekn
[15:34] <sforshee> bfiller: we're using tables from android to map ambient brightness to screen brightness
[15:34] <ralsina> beuno, xnox: that's being merged today, probably
[15:35] <cjwatson> ogra_: mm, yeah, keys live in /etc
[15:35] <sforshee> bfiller: if you just don't like the brightness level that's being selected, then those are to blame
[15:35] <ogra_> cjwatson, right, it doesnt even do that if i switch the image to writable
[15:35] <cjwatson> ogra_: maybe run it with config options to fetch host keys from somewhere else
[15:35] <sforshee> bfiller: but if you're seeing a real problem with the implementation you should file a bug
[15:35] <cjwatson> ogra_: it doesn't generate host keys on start, it expects that to have been done in maintscripts
[15:35] <ogra_> cjwatson, shouldnt it automatically generate keys ?
[15:35] <ogra_> oh !
[15:35] <bfiller> sforshee: ok I will. it's totally unusable on maguro. can't keep the screen bright it always dims immediately even during use
[15:36] <ogra_> ok, i thought i had seen it do that in the past
[15:36] <cjwatson> ogra_: I've debated it fairly extensively in the past, came out on this side, can't remember exactly why just now, also am in a meeting :)
[15:36] <sforshee> bfiller: that sounds like not liking the brightness levels which are being picked ;-)
[15:37] <dholbach> Saviq, sorry, I got tied up in a few other things - test-building it now
[15:39] <Saviq> dholbach, that's fine, we still need a review of the changes
[15:39] <bfiller> sforshee: sounds like the levels are wrong to me, not about not liking it :) it's just wrong
[15:39] <Saviq> dholbach, as they were rejected by upstream for "we don't want to touch this" reasons
[15:39] <sforshee> bfiller: they _should_ be the same ones that android uses
[15:39] <Saviq> dholbach, i.e. there's a complete rework on the horizon (but not on any roadmap)
[15:39] <dholbach> Saviq, oh ok... I thought it was a cherry-pick from upstream trunk
[15:40] <Saviq> dholbach, unfortunately not
[15:40] <dholbach> in that case I might be the wrong one to review it :-/
[15:40] <Saviq> dholbach, yeah, mzanetti will
[15:40] <dholbach> Saviq, let me know once it's reviewed and I'd be happy to sponsor it for you
[15:40] <Saviq> dholbach, thanks
[15:46] <seb128> didrocks, asac: so, can we get an indicator landing today?
[15:46] <didrocks> seb128: same than hub-content, let's try to get a green image first
[15:46] <didrocks> i'll keep you posted
[15:47] <didrocks> if people wouldn't update Mir ABI when we are asking to not, things would at least be better
[15:47] <seb128> didrocks, we are trying to get a green image for a week, we can't keep blocking work for everyone for ever :/
[15:47] <seb128> asac, ^
[15:47] <seb128> that's getting ridiculous, we need fixes/work to land
[15:48] <didrocks> seb128: please, I have enough already with the Mir team to deal with to argue on that right now
[15:48] <didrocks> 3rd time on 3 that they screw us
[15:48] <seb128> didrocks, send asac on IRC then or get the stacks unblocked
[15:49] <seb128> didrocks, sorry you get the ping, but you're the one who can ack/nack those landing and we need things to land
[15:49] <didrocks> seb128: I need to know the current status first
[15:49] <didrocks> which is really hard to get to
[15:49] <didrocks> so I'll change room soon
[15:49] <didrocks> and try to know where we are at
[15:49] <didrocks> in 10 minutes
[15:49] <didrocks> as I told to ken on #ubuntu-desktop
[15:49] <seb128> didrocks, ok, thanks
[15:50] <mterry> seb128, I see you're busy, but good news.  I've fixed lightdm so that logind will work in the autologin-phablet-user case (working on a release).  You mentioned when testing my branch that you got a black screen.  I'm 90% sure that means you haven't reflashed your device this week
[15:50] <mterry> seb128, testing my new lightdm and my other ubuntu-touch-session branch, I can get system-settings to correctly toggle AccountsService values
[15:50] <didrocks> seb128: will keep you posted, don't worry
[15:51] <seb128> mterry, the black screen was because I didn't have the autologin config, I got that fixed but then ran into the logind issue
[15:51] <seb128> mterry, I just need the lightdm fix pitti approved right?
[15:51] <seb128> didrocks, thanks
[15:51] <mterry> seb128, right (if you'd flashed, you'd have the autologin bits already)
[15:51] <mterry> seb128, yeah
[15:51] <xnox> sergiusens: bug 1223945
[15:52] <seb128> mterry, right, I hate doing that though because then I need to reinstall all my rdepends and pbuilder and stuff :p
[15:52] <mterry> Fair
[15:52] <seb128> mterry, I do ubuntu-system-settings builds on the device
[15:52] <mterry> Just saying
[15:52] <seb128> right
[15:52] <seb128> my fault
[15:52] <seb128> mterry, but I should be good to test again, when you upload lightdm ;-)
[15:52] <sergiusens> xnox, thanks, that's what I am already doing btw, there's a staged MR for the seeds and I'm adding dbarth's package into the list
[15:53] <mterry> seb128, testing new build now, bbiab
[15:53] <xnox> sergiusens: what's dbarth's package?
[15:53] <seb128> mterry, ok; finger crossed ;-)
[15:53] <xnox> sergiusens: can I see it?
[15:56] <sergiusens> xnox, sorry, hated discussion here https://code.launchpad.net/~xnox/ubuntu-seeds/ubuntu-touch.remove-webapps-demo/+merge/185092
[15:56] <sergiusens> xnox, *heated
[15:56] <xnox> sergiusens: ok.
[15:59] <mfisch> ssweeny / mterry: would lightdm landing allow us to customize locales?
[16:01] <sergiusens> xnox, oh, the dbarth package, I gave you the seed... one sec
[16:01] <sergiusens> xnox, https://code.launchpad.net/~dbarth/webapps-demo/click-packages/+merge/184639
[16:01] <asac> seb128: i am here
[16:02] <asac> seb128: go to the mir team and tell him to do your work
[16:02] <seb128> asac, good morning ;-)
[16:02] <sergiusens> xnox, the webapps-demo-click package will eventually end up in ppa:phablet-team/ppa and I'll pull/extract the click from there
[16:02] <asac> seb128: the indicators?
[16:02] <asac> which ones?
[16:02] <asac> did tedg touch them?
[16:02] <seb128> asac, the whole set, and I guess he did touch bits yes
[16:02] <asac> can you get a test log from him?
[16:03] <asac> seb128: ok... i will your indicators before we do the default unity/mir switch
[16:03] <asac> after getting the fix in
[16:03] <seb128> asac, I guess not, but current messaging menu is buggy, hud doesn't work, indicator-datetime blocks/segfault
[16:03] <asac> that ricmm submitted... unfortunately we have to revert commit mir
[16:03] <seb128> asac, all those are fixed for days and nothing is landing
[16:03] <asac> which did a cowboy library transition
[16:04] <seb128> yeah, I read about that
[16:04] <pmcgowan> sergiusens, I did not understand that comment about webapps
[16:04] <pmcgowan> we wont have anything in the PPA
[16:04] <seb128> asac, I don't get why mir changing soname prevent us to land indicators though
[16:04] <asac> seb128: how sure that indicators will not regress unity8 tests?
[16:04] <asac> i feel indicators have side effects on unity8
[16:05] <xnox> sergiusens: which does seem sub-optimal in the long run. The packaging seems suboptimal (e.g. shipping clicks inside deb), e.g. why did we bother implementing seeding and installing click packages directly via http://people.canonical.com/~ubuntu-archive/click_packages/click_list then? and I'm not sure those semantics are correct in multi-user world going forward. Where pre-installed clicks should be registered for each user.
[16:05] <seb128> asac, they could yes
[16:05] <asac> seb128: we can land you at the same time if you are happy to lead the blame war in case unity is still not fixed after ricmm's upload
[16:05] <seb128> asac, but we can't keep not landing anything forever, we are already behind on work and that keeps slowing us down
[16:05] <cjwatson> xnox: The --all-users semantics are fine actually.
[16:05] <xnox> cjwatson: hm. ok.
[16:05] <cjwatson> xnox: I agree shovelling the click packages through debs is cumbersome but if it works for now, I'm kinda meh on it
[16:06] <xnox> sergiusens: cjwatson: it's oding "--user=phablet" at the moment.
[16:06] <seb128> asac, well, I'm on holidays tonight, so I'm happy to have no landing for 3 weeks, don't go complain that we meet none of the goal cycles at the end then
[16:06] <cjwatson> Oh
[16:06] <cjwatson> Yeah, OK, that's completely wrong, I misread
[16:06] <asac> seb128: you are gone tonight
[16:06] <asac> ?
[16:06] <seb128> asac, yes
[16:06] <asac> let me talk to didrocks
[16:06] <asac> and risk it
[16:06] <cjwatson> dbarth: Please s/--user=phablet/--all-users/ before landing that
[16:06] <seb128> thanks
[16:06] <xnox> cjwatson: sergiusens: and "not shipping icons cause they don't work", well they do work from within clicks (just regressed in recent images)
[16:07] <cjwatson> dbarth: hm, what's this about "doesn't install the aa-exec frontend"?
[16:07] <sergiusens> xnox, I'm not going to use that postinst job
[16:07] <sergiusens> xnox, just dpkg-deb the deb and take out the click package
[16:07] <cjwatson> dbarth: I guess that's bug 1223085?  I plan to fix that and would appreciate people not working around it in ways that will be hard to undo later
[16:08] <sergiusens> xnox, wrt to icons, cjwatson told me we switched from using the desktop hook in click to the one tedg wrote, he said he had a fix soon
[16:08] <sergiusens> cjwatson, I'm not going to use the postinst job fwiw
[16:08] <asac> seb128: ok talkdd to didrocks... we are doing a parallel approach
[16:08] <asac> that means: we land the mir/unity fixes now, kick off an image, but DONT wait for results
[16:08] <cjwatson> icons> right
[16:08] <asac> and land your stuff right after
[16:09] <asac> seb128: too late?
[16:09] <seb128> asac, no, that's fine, I'm going to be around another 5 hours to finish thing (with dinner in between)
[16:09] <asac> ok .. .so lets hope this goes good
[16:09] <seb128> asac, thanks
[16:10] <jdstrand> cjwatson: re "I suspect we ought to arrange to run system-level hooks at boot", stgraber is assigned to bug #1215092 already, which I think is quite closely related
[16:10] <asac> and noone else uploads a lib transition :)
[16:10] <seb128> asac, fingers crossed ;-)
[16:10] <asac> seb128: thanks so much for your patience
[16:10] <asac> we will soon be better at all this
[16:10] <seb128> asac, thanks for finally unblocking things
[16:10] <seb128> asac, I hope
[16:10] <cjwatson> jdstrand: Well, I could equally have an upstart job that runs "click hook install-system" just as I currently have a user-session upstart job that runs "click hook install-user"; I think that would be nice and orthogonal
[16:11] <asac> seb128: any other stacks yoiu wan to land?
[16:11] <seb128> asac, things were going smooth for most of the cycle, but for a week we keep hitting walls
[16:11] <asac> seb128: so the problem really is that we dont have good visualization of the amount of packages waiting
[16:11] <asac> and their age
[16:11] <asac> once we hvae that we will ensure things are fair and decent
[16:11] <cjwatson> jdstrand: I certainly don't want each individual system-level hook provider to have to worry about this
[16:11] <seb128> asac, @stacks: HUD would be nice
[16:11] <jdstrand> cjwatson: sure, just an fyi. we need that bug fixed for other reasons (ie, policy updates outside of click)
[16:12] <asac> seb128: is that your work? how old is the stuff waiting?
[16:12] <seb128> asac, but indicators is enough to make me happy
[16:12] <cjwatson> jdstrand: So how about I add an upstart job that does that nowish, and then it can migrate to something else later if need be
[16:12] <asac> seb128: who is owner of hud?
[16:12] <asac> you?
[16:12] <asac> guess unity team?
[16:12] <seb128> asac, not it's not, I just know that Anti mentioned that currently hud was not working and he wanted to land the fix
[16:12] <seb128> asac, tedg was looking after it
[16:12] <seb128> tedg, ^ is that still you?
[16:13] <asac> where is he?
[16:13] <asac> wellark?
[16:13] <jdstrand> cjwatson: I think that works ok for you, but we still have to account for when, say, apparmor-easyprof-ubuntu is updated
[16:13] <cjwatson> jdstrand: sure
[16:13] <tedg> Yeah, Wellark was doing the latest fixes.  But I get involved as well.
[16:13] <tedg> There were a couple issues he landed fixes for.
[16:14] <jdstrand> cjwatson: I was only mentioned the bug since it was related and so you were aware of it
[16:14] <jdstrand> s/mentioned/mentioning/
[16:14] <cjwatson> yep, thanks
[16:17] <pmcgowan> asac, that hud fix is from last week, good to get it if we can
[16:18] <asac> pmcgowan: what does it fix?
[16:18] <pmcgowan> asac, bug where the hud does not show up first time app is launched
[16:19] <pmcgowan> I forget the second one...
[16:23] <didrocks> asac: mir busted out, rebuild of unity-mir/unity8 in progress
[16:31] <achiang> bfiller: hey, for some of our web apps like the current facebook app, we seem to get some rather ugly html sent down to us. is that because we're not sending a mobile user-agent in our browser?
[16:32] <pmcgowan> achiang, its cause we are ;)
[16:33] <pmcgowan> there is an MR to improve FB specifically and webapps guys are experimenting with overrides
[16:33] <achiang> pmcgowan: ok, twitter is kinda ugly too
[16:33] <pmcgowan> they all are
[16:33] <pmcgowan> the web is a mess
[16:34] <achiang> ok
[16:34] <pmcgowan> achiang, the websites are coded to look for android or iphone etc
[16:34] <pmcgowan> rather than what they should
[16:35] <achiang> pmcgowan: that's some quality stuff ;)
[16:35] <achiang> pmcgowan: in other news, i can't get my system settings to respond at all
[16:36] <pmcgowan> achiang, ?
[16:36] <cwayne_> mzanetti, hey, do you happen to know what's going on with the welcome screen (or point me to who would)?  It used to use the custom background, but it no longer does as of today
[16:37] <achiang> pmcgowan: i launch system settings, but none of the controls work. i can't even get the app to scroll up/down to expose the bottom controls
[16:37] <achiang> pmcgowan: i just flashed ubuntu-system yesterday
[16:37] <pmcgowan> hmm
[16:37] <pmcgowan> not seeing that, did the same
[16:37] <pmcgowan> getting the update now
[16:38] <achiang> pmcgowan: i was hoping to update OTA ;)
[16:38] <achiang> pmcgowan: but i'll do a usb flash
[16:38] <pmcgowan> seb128, hey when I select download, should it provide feedback? or did I just miss the button
[16:38] <pmcgowan> seb128, ah no feedback
[16:39] <michyprima> hey guys
[16:39] <michyprima> trying to port ubuntu touch to my phone but I can't undestand the step abou the apq8064-tabla-snd-card.conf file
[16:39] <pmcgowan> seb128, I assume thats in the works and no need to bug it
[16:39] <michyprima> I don't really understand where my ucm directory should be
[16:43] <cwayne_> pmcgowan, ping
[16:43] <didrocks> asac: ricmm: FYI, the build for unity8 and unity-mir are waiting for some free buildds (launchpad estimates 15 minutes)
[16:43] <cwayne_> pmcgowan, any idea who i should ask about the welcome screen background?
[16:45] <pmcgowan> cwayne_, in terms of how its applied? Id say mterry
[16:45] <michyprima> anyone would throw an hand?
[16:46] <cwayne_> mterry, pingaling
[16:49] <pmcgowan> michyprima, the guys that might be able to help are a bit busy today in case you dont get a reply
[16:49] <michyprima> oh I see.. too bad the wiki is not that clear on that part :(
[16:54] <achiang> pmcgowan: re-flashing w/usb seems to fix the system settings issue
[16:56] <mzanetti> cwayne_: mterry
[16:56] <cwayne_> mzanetti, thanks
[17:09] <asac> didrocks: can you ask someone to bump the build score?
[17:09] <asac> infinity: 13:06 < didrocks> 16:43:40> asac: ricmm: FYI, the build for unity8 and unity-mir are waiting for some free buildds (launchpad estimates 15 minutes)
[17:09] <asac> not sure if it started
[17:09] <asac> ... guess so
[17:09] <asac> didrocks: did the build start?
[17:10] <asac> cjwatson: ogra said we might have a lower build score in our daily-relesae ppa than the normal archive?
[17:11] <asac> cjwatson: can we make that equal at least in case?
[17:11] <cjwatson> asac: Which archive are we talking about here?
[17:12] <mterry> cwayne, sorry was at lunch, what's up?
[17:12] <cjwatson> ~ubuntu-unity/daily-build-next?
[17:12] <asac> cjwatson: daily-release ppa vs. main
[17:12] <asac> cjwatson: the one where we copy stuff directly to from
[17:12] <cjwatson> (When I ask for which archive I normally mean the fully-qualified name)
[17:12] <asac> i will get you the real name
[17:13] <cwayne__> mterry, hey, so it seems that as of today, the welcome screen background is no longer using our custom background
[17:13] <cjwatson> asac: If this is ~ubuntu-unity/daily-build-next, ogra is mistaken.
[17:13] <cjwatson> >>> lp.load("~ubuntu-unity/+archive/daily-build-next").relative_build_score
[17:13] <cjwatson> 1500
[17:13] <cwayne__> mterry, any idea how i can debug/fix?
[17:13] <asac> cjwatson: https://launchpad.net/~ubuntu-unity/+archive/daily-build
[17:13] <asac> that one
[17:13] <cjwatson> >>> lp.load("~ubuntu-unity/+archive/daily-build").relative_build_score
[17:13] <cjwatson> 1500
[17:13] <mterry> cwayne, yup!  Sorry, I alerted some people I knew were using different backgrounds, but didn't know you were
[17:14] <cjwatson> However, it's scored lower than the security PPA that's currently building
[17:14] <cjwatson> >>> lp.load("~ubuntu-mozilla-security/+archive/ppa").relative_build_score
[17:14] <cjwatson> 3055
[17:14] <asac> cjwatson: ogra didnt say it was the case, but that i better should check with you that our score is sane
[17:14] <cwayne__> mterry, this is even worse than when you didn't invite me to your birthday party :(
[17:14] <cwayne__> mterry, lol, so how fix?
[17:14] <mterry> cwayne, so as of recent builds, the user session background and welcome screen background can be different and are set different ways.  User session is same as always, via the GNOME gsettings key
[17:14] <cjwatson> I would be inclined to say that it is sensible for an archive used for security fixes to be scored higher than a daily-release archive, TBH
[17:15] <mterry> cwayne, the welcome screen background is now grabbed via AccountServices.  I can get the command line to manually set it, hold on...
[17:15] <asac> cjwatson: its sane
[17:15] <cwayne__> mterry, great, thanks
[17:15] <asac> cjwatson: is 1500 the same score as the normal archive?
[17:15] <cjwatson> asac: The normal archive is 0
[17:15] <asac> e.g. main
[17:15] <asac> oh
[17:15] <cjwatson> But it's a little more complicated than that
[17:15] <cjwatson> https://help.launchpad.net/Packaging/BuildScores
[17:16] <cjwatson> If Chris Coulson confirms I can cancel his builds if need be, to make way; I just don't want to cancel what might be a critical security patch
[17:17] <cjwatson> Anyway, the true situation is the opposite of what Oliver told you, I'm afraid
[17:17] <asac> sure dont touch that
[17:17] <mterry> cwayne, try this: dbus-send --print-reply --system --dest=org.freedesktop.Accounts /org/freedesktop/Accounts/User32011 org.freedesktop.Accounts.User.SetBackgroundFile string:/path/to/file
[17:17] <cwayne__> mterry, so how come this isn't in a gsettings key as well?
[17:17] <asac> cjwatson: well, thats good news :)
[17:18] <mterry> cwayne, because both the phablet and lightdm users needs access to it
[17:18] <cjwatson> asac: I've also rebalanced one i386 builder to amd64 to help
[17:18] <asac> nice
[17:18] <mterry> cwayne, and the phone system-settings design allows for users to set welcome and shell backgrounds
[17:18] <asac> cjwatson: question i had yesterday was: how did we get to the magic number of 5 i386 buildres :)
[17:18] <cjwatson> It'll probably build unity8 and unity-mir in succession, but better than waiting for firefoxes
[17:18] <cwayne__> mterry, isnt there supposed to be a key to make them both the same?
[17:18] <asac> cjwatson: do we do systematic sizing ?
[17:19] <cwayne__> or is that also an option in AccountsService
[17:19] <mterry> cwayne, on the desktop, we have this same AccountsService setting, but Unity keeps it in sync with gsettings, unlike what will happen on phone
[17:19] <asac> cjwatson: maybe you know?
[17:19] <mterry> cwayne, system-settings can just set both to the same value then
[17:19] <cjwatson> asac: It's fairly subjective, but most of the time (except when we're doing mass test rebuilds) 5 is more than adequate
[17:19] <cwayne__> mterry, ah, ok
[17:19] <dbarth> cjwatson: thanks for the heads up about the bug; i was indeed trying to workaround the issue
[17:19] <cjwatson> asac: We could ask IS for more if you think you can get hardware budget from somewhere
[17:20] <cwayne__> mterry, and this should work on the r/o image right?
[17:20] <asac> cjwatson: right. so i think our "adequate" might change if we go serious about trying to keep things all good every day
[17:20] <cjwatson> It's not a particularly fixed or magic number or anything
[17:20] <asac> happy to chat with elmo if its a budget issue and see
[17:20] <asac> right
[17:20] <cjwatson> In fact it's actually 8 i386/amd64 builders that we adjust back and forward as needed
[17:20] <asac> guess armhf is a problem
[17:20] <mterry> cwayne, should
[17:20] <cjwatson> armhf is no problem
[17:20] <asac> as getting those machines sounded like a major effort
[17:20] <asac> sorry
[17:20] <cwayne__> mterry, thanks for the help sir
[17:20] <mterry> cwayne, (it didn't at first, but we poked a hole for AS data)
[17:20] <asac> growing armhf easily
[17:20] <cjwatson> Since the Calxeda box we're gratuitously oversupplied with armhf builders
[17:21] <asac> right. sorry. didn tsay its a problem, just not easy to grow simply through budget
[17:21] <cjwatson> No, that's true, but it's the last of our architectures that's going to be an issue
[17:21] <asac> :)
[17:21] <asac> for now
[17:21] <asac> thanks
[17:21] <cjwatson> Well, everything is for now :)
[17:21] <asac> will check with didrocks if we need a rescore or any more help
[17:21] <asac> given that we do lunch i assume
[17:22] <asac> its all okaish and i really hope the securty uploads finish not too long ahead
[17:22] <cjwatson> feel free to SMS me if it's an emergency build situation out of hours and other buildd admins aren't available
[17:22] <asac> cjwatson: thanks. i will remember that, but i try very hard to find ways that allows folks to have decent work hours (e.g. find organizational solutions that scale) so that is certainly a last resort :)
[17:23] <seb128> pmcgowan, download where?
[17:23] <asac> so far we always found one :)
[17:23] <asac> (yesteday adam was around)
[17:23] <cjwatson> There are a few other folks in https://launchpad.net/~launchpad-buildd-admins/+members, indeed
[17:24] <pmcgowan> seb128, sorry what was the context?
[17:24] <seb128> pmcgowan, "<pmcgowan> seb128, hey when I select download, should it provide feedback? or did I just miss the button"
[17:24] <seb128> pmcgowan, sorry I was away, just read the scrollback and you pinged with that question
[17:24] <seb128> ?
[17:25] <pmcgowan> seb128, ah, in the update, I push download and it doesnt provide feedback, but it does it
[17:26] <seb128> pmcgowan, hum, it should display a progress bar/counter ... I need to test, we did most of the work with the mock service, maybe the real service has a bug/behave differently
[17:26] <pmcgowan> seb128, I just did an update but got no progress
[17:26] <cwayne__> mterry, seems to work, now to try it in our custom tarball and see if it works there..
[17:27] <seb128> pmcgowan, can you file a bug (https://bugs.launchpad.net/ubuntu-system-settings/+filebug), I'm going to check that in a bit
[17:27] <pmcgowan> seb128, will do
[17:27] <seb128> pmcgowan, thanks
[17:29] <ogra_> asac, cjwatson, i was only referring to standard PPAs, i didnt know the dailies get special treatment
[17:29] <ogra_> (though i was assuming they do)
[17:30] <cjwatson> ogra_: Entirely standard PPAs run on a separate build farm from the main archive, so their relative scoring doesn't matter; anything that shares a build farm with the main archive is non-standard to begin with by being devirtualised
[17:31] <ogra_> ah, good to know, thanks
[17:31] <cjwatson> ogra_: But as far as I'm aware uploads to devirt PPAs with relative_build_score==0 are scored identically to uploads to main in the primary archive
[17:31] <cjwatson> You can look at the BuildScores page above to calculate it; I believe it's up to date
[17:31] <ogra_> yeah, i got that from the backlog
[17:32] <cjwatson> devirt public PPAs, that is; private PPAs get a general bonus
[17:33] <cjwatson> Oh, package set bonuses don't apply to PPAs, so I guess that would tend to put the primary archive slightly ahead for a lot of packages.  Anyway
[17:35] <cjwatson> Maybe somebody ought to ask the TB for an ubuntu-touch packageset generated from its seed, so that we can score it up to the level of core
[17:35] <ogra_> ++
[17:36]  * ogra_ will write a mail 
[17:43] <cjwatson> Heh, and unity8 failed to build due to being timed poorly with respect to unity-mir
[17:43]  * cjwatson will retry them
[17:43] <cjwatson> Let's just see if the armhf one gets past installing build-deps first ...
[17:45] <cwayne__> mterry, hey, so that command you sent me is pretty hardcoded for the phablet user isn't it?  can we set it for all users? or change the default maybe?
[17:45] <mterry> cwayne, you can change the id number for whatever user you want
[17:45] <mterry> cwayne, but can't set a new default
[17:46] <cwayne__> mterry, so i can't do it for 'all users'
[17:46] <cwayne__> id have to figure out their uid?
[17:46] <asac> didrocks: ricmm: did the fix land?
[17:46] <mterry> cwayne__, yeah
[17:46] <asac> or still build issues?
[17:46] <asac> oh see colins comments up
[17:46] <cjwatson> asac: see my comment just above
[17:46] <asac> ignore
[17:46] <didrocks> asac: i386 built, amd64 about to start
[17:46] <asac> :(
[17:46] <asac> :)
[17:46] <cjwatson> didrocks: er, no, i386 unity8 didn't build
[17:46] <cjwatson> I retried it
[17:47] <cjwatson> unity-mir built everywhere
[17:48] <didrocks> cjwatson: but unity8 built and published now https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956031
[17:48] <didrocks> (after your retry)
[17:48] <didrocks> this is what I meant
[17:48] <cjwatson> didrocks: Oh FFS.  asac said daily-build not daily-build-next.
[17:48] <didrocks> ah
[17:48] <cjwatson> This is why I wanted the exact archive name. :-(
[17:49] <didrocks> yeah, daily-build-next to win some time
[17:49] <cjwatson> So I've been scoring up the wrong things due to being told the wrong thing.
[17:49] <asac> well, the archive above was the archive we looked at yesterday
[17:49] <didrocks> cjwatson: as I didn't want latest Mir and crap in daily-build, I've used another path to avoid waiting for everything to be deleted
[17:49] <cjwatson> Maybe we can just let everything build in sequence and you lot can go and have coffee or something :-)
[17:50] <anders3408> hello, just before i ask for help, is this the corret place to get some help in ubuntu touch porting ? :)
[17:50] <ogra_> *slurp*
[17:50] <didrocks> cjwatson: if only … ;)
[17:50] <didrocks> for powerpc
[17:50] <cjwatson> Or failing that somebody can give me exact links for what you want built
[17:50] <didrocks> as I don't want it to wait 4 hours to see that it will build-dep
[17:50] <cjwatson> didrocks: Meh, it's beating amd64 right now
[17:50] <didrocks> I will kill the job
[17:50] <cjwatson> Huh?  You don't need to
[17:50] <didrocks> and force the publication
[17:50] <didrocks> so that proposed get it
[17:51] <cjwatson> How about we not force things, that usually just makes matters worse
[17:51] <cjwatson> Exactly what builds are you waiting on?  I can cancel things to make way, if need be
[17:51] <cjwatson> URLs, preferably
[17:51] <didrocks> cjwatson: oh ignore me, I implemented the logic in dailies
[17:51] <didrocks> as powerpc never published
[17:51] <didrocks> it will just ignore the arch
[17:51] <didrocks> and dailies won't wait on it
[17:51] <asac> didrocks: how many different routes have we? just daily-build and -next?
[17:51] <didrocks> (as britney doesn't)
[17:51] <cjwatson> Fine
[17:51] <asac> is that artehr daily-build-1 and daily-build-2 ?
[17:52] <asac> rather
[17:52] <didrocks> asac: just one daily-build, I just used daily-build-next to win 20 minutes not having to clean the ppa and wait for a publisher cycle
[17:52] <didrocks> I warned sil2100 in advance about it
[17:52] <asac> right. so seems we maintain multiple ppas
[17:52] <didrocks> just wanted to win some time
[17:52] <asac> to get multiple path into the archive
[17:52]  * genii makes a fresh pot of coffee
[17:52] <didrocks> asac: this ppa is used for diverging n to n+1
[17:53] <didrocks> asac: let me continue making things moving (need change on the list of packages because of new dependency) and we can discuss then
[17:53]  * cjwatson notes that he has a critical bug fix waiting behind all of this, so, you know, I was just going to go eat instead :)
[17:53] <asac> well, i will just remember that i have not enough clue to give any help :)
[17:53] <didrocks> (but I explained -next this morning in the presentation btw :p)
[17:53] <didrocks> cjwatson: enjoy
[17:53] <didrocks> heh
[17:53] <asac> didrocks: right. but in this case you use -next for something else
[17:53] <didrocks> asac: the advice is normally the right one, just that I abused the system
[17:53] <didrocks> right
[17:54] <asac> we surealy are not yet diverging for ubuntu+1 here
[17:54] <didrocks> let me finish the test unblock
[17:54] <didrocks> asac: we are for autopilot
[17:54] <didrocks> I mentionned it
[17:54] <didrocks> but as it's not "on" yet
[17:54] <didrocks> I abused the system to win 20 minutes
[17:54] <asac> right
[17:54] <didrocks> 20 minutes I would prefer not loosing in discussion, but unblocking the rest ;)
[17:54] <asac> and i wasted cjwatson's time because of that :(
[17:54] <ogra_> didrocks, to late ?
[17:54] <asac> anyway
[17:58] <didrocks> ogra_: "to late"?
[17:58] <didrocks> asac: ok, let me explain to you now
[17:58] <didrocks> so, we have daily-build -> distro
[17:58] <didrocks> when upstream want to diverge
[17:58] <didrocks> and n+1 isn't opened yet
[17:58] <ogra_> didrocks, to late to prevent you losing 20min in discussions, already happened :)
[17:58] <asac> didrocks: its ok
[17:58] <asac> didrocks: i can figure
[17:58] <didrocks> ok ;)
[17:58] <cjwatson> everything in ~ubuntu-unity/daily-build-next has been built or is currently building now
[17:58] <anders3408> so i have a dmesg that prints out :  init: upstart-local-bridge main process (222) terminated with status 1 init: upstart-local-bridge main process ended, respawning   init: ureadahead main process (226) terminated with status 5 but that process says me nothing, i have not worked much with ubuntu touch, only aosp compiling
[17:59] <didrocks> asac: just writing: daily-build-next -> next
[17:59] <cjwatson> FYI
[17:59] <didrocks> ogra_: heh ;)
[17:59] <didrocks> cjwatson: yeah, that's perfect, the tests are starting as well
[17:59] <asac> didrocks: thats clear and sane... misusing is is what makes me feel pain. we should have daily-1 daily-2 daily-3 if deleting stuff slows us down i guess
[18:00] <asac> so lets add that as a point to discuss
[18:00] <didrocks> asac: good comment btw
[18:00]  * asac crosses fingers
[18:01] <didrocks> asac: you're lying, I don't see you crossing your fingers ;)
[18:01] <didrocks> (we have new build-dep on unity-mir btw)
[18:02] <didrocks> dep on libunwind8hud though
[18:02] <didrocks> which isn't in the archive
[18:02] <didrocks> ricmm: help ^
[18:02] <ricmm> uh, what?
[18:02]  * didrocks dives a little bit
[18:03] <thomi> asac: didrocks, we need to talk about that at some point
[18:04] <ricmm> didrocks: wheres the blocking build/job?
[18:04] <ricmm> 11.4 built fine in the daily-build ppa
[18:04] <didrocks> build is not "installing"
[18:04] <asac> thomi: at best we dont invest in -next at this point
[18:05] <ricmm> oh a run dep?
[18:05] <sergiusens> cjwatson, can we run a manual sync for the click stuff?
[18:05] <asac> thomi: but rather write more good tests for a few more weeks
[18:05] <sergiusens> cjwatson, to pull in xnox's webapps
[18:05] <didrocks> ricmm: so, unity8 deps on libunity-mir1, which deps on libmirserver1 which deps on libgoogle-glog0  which deps on libunwind8
[18:05] <didrocks> (it's a new dep)
[18:05] <thomi> asac: so I'm landing click packages in 1.3, which will land in saucy. Almost all other big AP features will go in 1.4, which is for 'T'
[18:05] <didrocks> ricmm: let me try something
[18:06] <ricmm> didrocks: where did the +hud suffix come from?
[18:06] <thomi> asac: any idea when/if the touch images will be based in T sources?
[18:06] <asac> thomi: first week of T cycle is the goal
[18:06] <didrocks> ricmm: possibly a typo somewhere, let me try
[18:06] <didrocks> ricmm: will keep you posted
[18:06] <thomi> asac: awesome :)
[18:06] <asac> thomi: but, we rdont want to invest in features at this point
[18:06] <asac> we have so many things and bugs to do
[18:07] <didrocks> +1
[18:07] <didrocks> +1
[18:07] <didrocks> +1
[18:07] <didrocks> (so +3 ;))
[18:07] <asac> thomi: i think in your case its about helping engineering teams to get more tests
[18:07] <asac> if they are willing to work with you (of course)
[18:07] <anders3408> not that i cant wait, but does you guys also helps people porting ubuntu touch for other phones ? or is it only for running systems that you help ?
[18:07] <thomi> asac: sure, but that doesn't affect me.
[18:08] <asac> thomi: you cannot help on that?
[18:09] <thomi> asac: I don't understand..
[18:09] <asac> thomi: so for instance, go in the phonedations room and help them sort out their phone test story
[18:09] <thomi> asac: we'll talk later, I'm in a meeting now
[18:09] <asac> thomi: pitti did all the ground investment
[18:09] <asac> and its not used, so would be sad if we dont go the final mile
[18:09] <asac> thomi: sure. talk later
[18:10] <sergiusens> ogra_, https://code.launchpad.net/~sergiusens/ubuntu-seeds/share-app--/+merge/185043
[18:14] <didrocks> ricmm: asac: intel passed, we are at 50% to celebrate
[18:14] <ricmm> lol
[18:14] <ricmm> didrocks: so what happened with libunwind8 ?
[18:14] <didrocks> \o/
[18:15] <ricmm> I dont see the dep being a hard dep, and I see versions in the archive
[18:15] <ricmm> so should work
[18:15] <didrocks> ricmm: typo, my fault, mind broken, not enough sleep
[18:15] <ricmm> understandable
[18:15] <didrocks> + jet lag
[18:15] <didrocks> ok, so party \o/
[18:15] <didrocks> manual publication for the packaging change
[18:15] <didrocks> let me review that
[18:15] <didrocks> and release the "stuff"
[18:16] <didrocks> (just waiting for amd64 to publish)
[18:16] <didrocks> but tests pass, we live in a wonderful world…
[18:17] <ogra_> oh, i just found an easy way to have working Mir without any further work !
[18:17] <ricmm> ogra_: get out
[18:17] <didrocks> ricmm: +         libunity-mir1,
[18:17] <didrocks> are you the one adding that?
[18:17] <didrocks> (if not, I'll check the Vcs)
[18:18] <ricmm> didrocks: to unity8? yes
[18:18] <ricmm> it links to it dynamically on runtime
[18:18] <didrocks> ah, dynamic linking
[18:18] <ricmm> need the rdep on it
[18:18] <ricmm> black magic and fairy dust
[18:18] <didrocks> urgh ;)
[18:18] <didrocks> but when you add a version
[18:18] <didrocks> like a new API
[18:18]  * ogra_ throesw a "ln -s /system/bin/surfaceflinger /usr/bin/Mir" at ricmm 
[18:18] <didrocks> you have to handle the dep yourself?
[18:19] <ricmm> I assume
[18:19] <didrocks> ricmm: good luck ;)
[18:19] <ricmm> ;)
[18:19] <didrocks> I think we should discuss about it
[18:19] <didrocks> but not now
[18:19] <didrocks> not today
[18:19] <didrocks> ;)
[18:20] <ricmm> yea not now
[18:20] <ricmm> today lets be happy
[18:20] <ricmm> and see a green dashboard
[18:20] <didrocks> I'll be happier once amd64 will publish
[18:20] <ricmm> but I agree, we can think of a better way later
[18:20] <didrocks> and I push THE button
[18:20] <ricmm> \o/
[18:21] <ogra_> sergiusens, "echo -n rndis,adb > /data/property/persist.sys.usb.config"
[18:25] <jdstrand> diwic: hi! I commented on bug #1211380. please followup with tyhicks if you have any questions
[18:27] <ricmm> didrocks: all seems to be published in the ppa, no?
[18:27] <didrocks> ricmm: it's built
[18:27] <didrocks> not everything is published yet
[18:27] <didrocks> (not amd64 for unity8)
[18:28] <ricmm> right
[18:28] <didrocks> ricmm: you can stare as well: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-2.1build/257/console :)
[18:28] <ricmm> perfect, once it publishes you hit the magic button
[18:28] <ricmm> and it goes to archive? ;)
[18:28] <cwayne__> so when will it be in a daily-proposed image?
[18:28] <didrocks> ricmm: right, I've already pre-looked at the diff
[18:28] <didrocks> and decided I don't hate you so much for the libunity-mir1 direct dep :p
[18:29] <asac> mterry: hey
[18:29] <asac> mterry: this screen unlock script
[18:29] <ricmm> didrocks: \o/
[18:29] <asac> mterry: you think you can do it?
[18:30] <didrocks> last time I asked, it was a sed in a QML file
[18:30] <mterry> asac, so in a couple weeks, we'll be using lightdm to manage the unlock screen, will you still need it then?  Or is this a short term thing?
[18:30] <asac> mterry: we need it tomorow
[18:30] <asac> its soo screwy here
[18:30] <asac> mterry: this discussion really goes on for month
[18:30] <asac> i know you havent been involved
[18:30] <asac> but everybody agrees that if you deliver that part
[18:30] <asac> the rest will come in a day or two
[18:31] <didrocks> ricmm: published!
[18:31] <asac> mterry: thing is i spend probably 10 hours talking to people per week
[18:31] <asac> that say that stuff isnt reproduci ble
[18:31] <asac> and the unlock screen is the biggest piece because we have tests that need screen unlocked and others that dont
[18:31] <didrocks> asac: ricmm: pressing THE button
[18:31] <asac> didrocks: !!!nice!!!
[18:32] <asac> mterry: so we want to write a fail-safe script that always does exactly the thing that our automation does so we dont need to argue
[18:32] <ricmm> didrocks: \o/
[18:32] <mterry> asac, OK...  So you need a script that when run in a session will unlock the greeter, if locked.
[18:32] <asac> all the time with everyone about how they cant reproduce something
[18:33] <asac> mterry: its supposed to be run from autopilot
[18:33] <asac> not sure if thats best in session or root or phablet user without session
[18:33] <asac> mterry: guess you know ?
[18:33] <mterry> asac, OK.  (why can't autopilot just drive the mouse and pull it aside?)
[18:33] <asac> i believe the autopilot stuff is run in a session
[18:33] <asac> mterry: dont ask that please
[18:33] <mterry> heh
[18:33] <asac> was discussed hundreds of times
[18:33] <asac> mterry: you are the only one who can safe us now :)
[18:34]  * mterry is confused, but will look into it
[18:34] <didrocks> done, copy to -proposed will be active in 2 minutes. Then, it will be too late, the crack will be in *forever*
[18:34] <mterry> asac, probably will require a change to unity8 to allow being driven like that
[18:34] <mterry> asac, this won't work once we switch to a real lightdm greeter...  you'd be OK with that?
[18:34] <asac> mterry: we want to keep the same feature with lightdm
[18:34] <asac> e.g. keep the same command
[18:34] <asac> and change so it does the right thing
[18:35] <mterry> uhh
[18:35] <mterry> hm
[18:35] <asac> big problem?
[18:35] <mterry> asac, with lightdm as the greeter, do you envision the session actually getting locked?
[18:35] <mterry> (during autopilot)
[18:35] <doanac> ogra_: can you take a look at my update to https://code.launchpad.net/~doanac/phablet-tools/adb-errors/+merge/182515
[18:36] <asac> mterry: you mean as part of a test "test if locking works"?
[18:36] <asac> mterry: or what does "locking" mean? setting password?
[18:37] <ogra_> doanac, note that we now ship ssh by default and i'm about to also add some stuff to make usb networking work (might take until end of the week until thats 100% there though)
[18:37] <ricmm> didrocks: DONE
[18:37] <ricmm> still not see it in proposed
[18:37] <ricmm> is it in an image yet?
[18:37] <ricmm> ;)
[18:37] <mterry> asac, locking here is switching from the session to the lightdm greeter
[18:38] <mterry> asac, which means switching X/Mir session, switching from one user to the other
[18:38] <mterry> asac, how does that work in an autopilot context?
[18:40] <cwayne> mterry, btw, after changing the welcome screen bg,, the old one is still shown briefly on startup
[18:40] <cwayne> just fyi
[18:40] <mterry> cwayne, curious, I'll look at it
[18:41] <mterry> cwayne, 'old' being the default one?
[18:41] <cwayne> mterry, yep
[18:41] <doanac> ogra_: does that mean we can drop that RNDIS patch i never finished for phablet-tools?
[18:41] <ogra_> doanac, well, i will kind of re-ab-use it :)
[18:41] <doanac> excellent :)
[18:47] <brion> Hey all -- are the Ubuntu mobile/touch templates for Ubuntu SDK separate from the main Ubuntu SDK PPA now?
[18:47] <brion> I've only got 'other Projects', 'Non-Qt Project', and 'Import Project' in the new-projects dialog
[18:47] <brion> whereas the tutorial says to look under 'Ubuntu' for 'Simple Touch UI' http://developer.ubuntu.com/resources/tutorials/getting-started/currency-converter-phone-app/
[19:00] <pmcgowan> brion, no you should see those templates
[19:00] <brion> hmm
[19:00] <pmcgowan> brion, did you just upgrade or reinstall?
[19:01] <brion> pmcgowan: fresh install. ubuntu 13.04 64-bit, upgraded packages then installed the phablet-tools and ubuntu-sdk PPAs
[19:02] <pmcgowan> brion, what does apt-cache policy qtcreator-plugin-ubuntu say?
[19:03] <mterry> asac, I might have disconnected and missed your reply about greeter+autologin
[19:03] <brion> pmcgowan: https://gist.github.com/brion/6528236
[19:07] <didrocks> asac: ogra_: FYI, it seems there is an issue with the binary copy to distro, nothing is appearing in -proposed
[19:07] <didrocks> pinged colin if he's around, last time, he was the only one to be able to give logs
[19:07] <didrocks> (it only happened once in a 10 months, of course, it needs to happen again)
[19:07] <didrocks> now
[19:08] <pmcgowan> brion, all looks right, what is in options>build&run>qtversions
[19:08] <pmcgowan> brion, its probably one of the qt4/qt5 coexistence issues
[19:08] <pmcgowan> thought we fixed this
[19:08] <brion> pmcgowan: just "Auto-detected" and "Manual" ...
[19:09] <pmcgowan> and there is a path in manual or no?
[19:09] <brion> pmcgowan: nothing happens when i click on "Manual"
[19:09] <brion> i don't see any paths
[19:09] <pmcgowan> hmm
[19:09] <pmcgowan> ok so add one
[19:09] <brion> "Select a qmake executable" uhhhh
[19:10] <pmcgowan> /usr/bin/qmake
[19:10] <asac> didrocks: check with infinity
[19:10] <asac> he is sitting right next to you?
[19:10] <asac>  :)
[19:10] <asac> infinity: seems we have problesm with stuff not appearing in -proposed
[19:10] <brion> "Qmake Not Executable" "The quake executable /usr/bin/qmake could not be added:" [OK]
[19:10] <asac> 5:07 < asac> mterry: i see what you mean. i dont think it matters for our case though...
[19:10] <asac> 15:07 < asac> we basically want currently a provisioning solution
[19:11] <asac> 15:07 < asac> that ensure that we can bring the device  in the initial state we want for running tests
[19:11] <asac> 15:07 < asac> if we want to test lock and unlock after that
[19:11] <asac> 15:08 < asac> that would be part of a specific test ... so ther you can use autopilot swipe, type etc. to unlock the screen again
[19:11] <asac> 15:08 < asac> what people dont want is to use autopilot logic to prep the device
[19:11] <asac> 15:08 < asac> (AFAIUI)
[19:11] <asac> 15:08 < asac> didrocks: in the archive?
[19:11] <asac> 15:09 < asac> lets kick an image then and land the indicators
[19:11] <brion> quake is a symlink to qtchooser, which is marked executable
[19:11] <asac> 15:09 < asac> or any problems came up?
[19:11] <brion> *qmake
[19:11] <asac> mterry: ^^
[19:11] <brion> hmm. pmcgowan https://gist.github.com/brion/6528352 <- this happens if i try to run qmake from CLI
[19:11] <mterry> asac, OK.  So we're talking a one-time unlock before running tests
[19:11] <pmcgowan> brion, hmm
[19:12] <asac> mterry: exactly... prepping the device
[19:12] <asac> mterry: after boot
[19:12] <pmcgowan> brion, ha
[19:12] <mterry> asac, is manually configuring the device to enable lightdm autologin in scope?   That would be easiest solution once we actually switch to lightdm greeter.  (long term, we'll still need a short term thing)
[19:12] <pmcgowan> we are missing something now
[19:12] <asac> mterry: it explicitley hsouldnt give me info whether unlocking really works (e.g. its not testing the lock screen)
[19:13] <brion> wheee :)
[19:13] <asac> mterry: not thats not possible
[19:13] <mterry> asac, like, if you drop a file in /etc/lightdm/lightdm.conf.d and reboot?
[19:13] <mterry> ok
[19:13] <asac> mterry: we had the same with this intro thing :)
[19:13] <pmcgowan> brion, but what, you installed using  ubuntu-sdk ?
[19:13] <didrocks> asac: already tried to check with infinity
[19:13] <brion> pmcgowan: yep… followed directions on http://developer.ubuntu.com/get-started/ for adding the PPA
[19:14] <didrocks> asac: he doesn't know where those logs are
[19:14] <didrocks> asac: I just tried a second copy
[19:14] <didrocks> no chance
[19:14] <didrocks> I'm trying locally now
[19:14] <didrocks> with my creds
[19:14] <pmcgowan> mhall119, have you seen this issue recently that brion is having?
[19:14] <asac> infinity: is colin the only one who can help us?
[19:14] <asac> e.g. who knows this?
[19:15] <pmcgowan> brion, try install qt5-default
[19:15] <brion> hmmm
[19:15] <infinity> asac: I need some context on that question.
[19:16] <cwayne> stgraber, ping
[19:16] <brion> pmcgowan: to be certain, I did a general 'apt-get update && apt-get upgrade' and now i'm getting some output from qmake
[19:16] <infinity> asac: Oh, didier's missing copies?
[19:16] <brion> wtf….
[19:16] <brion> something must have gone awry in the install o_O
[19:16] <asac> infinity: didrocks cannot figure why his stuff doesnt show up in proposed
[19:16] <pmcgowan> uhoh
[19:16] <asac> infinity: unity8 i guess
[19:16] <brion> ok and it says qt5-default is installed… lemme try poking the qt versions again
[19:17] <pmcgowan> brion, maybe restart qtc and see
[19:17] <asac> 15:09 < didrocks> 19:07:24> asac: ogra_: FYI, it seems there is an issue with the binary copy to distro, nothing is appearing in -proposed
[19:17] <asac> infinity: ^^
[19:17] <brion> \o/ yay
[19:17] <infinity> asac: Right, I'm sitting next to him.
[19:17] <brion> pmcgowan: ok after adding the qt 5.0.2 system version (just specifying /usr/bin/qmake) now i see the ubuntu project templates
[19:17] <brion> that was damn odd :)
[19:18] <cwayne> aquarius, hi, didnt you make an html5 app at some point for canonical 2fa?
[19:18] <brion> pmcgowan: thanks for the help! will try later and see if i can repro it on another fresh install...
[19:18] <pmcgowan> brion, indeed, sorry, will follow up on it
[19:18] <aquarius> cwayne, I did
[19:18] <aquarius> cwayne, kryogenix.org/canonicalauth
[19:18] <cwayne> aquarius, awesome, thanks!
[19:19] <asac> didrocks: can you already put the indicators in the other ppa?
[19:19] <asac> didrocks: i feel its super delay and its getting super late for seb128's vacation
[19:19] <didrocks> asac: one sec, I'm handling and trying everything I can to publish first
[19:19] <didrocks> asac: the indicators should be run automatically by dailies
[19:19] <asac> didrocks: right. but we might need to wipe and rebuild (which could start while we fight this other thing)
[19:19] <asac> didrocks: just an idea
[19:20] <asac> whatever works best
[19:20] <asac> guess its better to stay focussed at this time :)
[19:20] <brion> at https://wiki.ubuntu.com/Touch/Install "To install and get updates, run the following command: phablet-flash (cdimage-touch|cdimage-legacy|ubuntu-system|community) -b" -- it seems to want me to choose one, not copy that whole command...
[19:20] <ogra_> fixit !
[19:20] <brion> i assume i want cdimage-touch ?
[19:20] <cwayne> mzanetti, ping
[19:21] <ogra_> brion, depends what youo want to do
[19:21] <brion> I want…. to test Ubuntu touch? :)
[19:22] <ogra_> brion, then use ubuntu-system and you will be able to do OTA updating
[19:22] <mterry> asac, does this need to work even if the user has a password set?
[19:22] <brion> aha
[19:22] <ogra_> if you want to hack around in the image use cdimage-touch, thats readwrite
[19:22] <brion> lemme see if i can edit that wiki page
[19:22] <ogra_> (while ubuntu-system is RO)
[19:23] <ogra_> brion, yeah, would be nice to add a few sentences too explain the different options
[19:23] <brion> i just want to try installing qml apps …
[19:23] <brion> shouldn't need to mess with the base system
[19:24] <brion> hmm ubuntu one won't log me in.. that's the same system as launchpad right?
[19:24] <pmcgowan> brion, you can run the apps on your desktop system
[19:24] <pmcgowan> if you just want to see qml apps
[19:24] <ogra_> brion, right, it uses launchpad auth
[19:24] <brion> pmcgowan: my desktop system doesn't have a touchscreen, i'd kinda like to see how they run 'for real'
[19:25] <pmcgowan> sure
[19:27] <stgraber> cwayne: pong
[19:27] <brion> there we go, logged in :D
[19:27] <cwayne> stgraber, hi, can we get a tarball signed please? :)
[19:27] <cwayne> stgraber, https://jenkins.qa.ubuntu.com/job/feifei-image/ <-- that one now
[19:28] <stgraber> cwayne: http://paste.ubuntu.com/6093942/
[19:29] <cwayne> stgraber, thanks!
[19:32] <ogra_> asac, cjwatson said to SMS him in urgent cases ... i guess this is one
[19:39] <sergiusens> ogra_, http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[19:40] <ogra_> yeah
[19:40] <brion> bah… Moin syntax isn't what I'm used to. :D lemme fix those bullet points
[19:40] <ogra_> bfiller, any objections to me uploading demo-assets to the archive and at the same time disabling all binaries we dont use atm (everything but video and music)
[19:42] <brion> ok, added a couple notes on https://wiki.ubuntu.com/Touch/Install
[19:42] <cwayne> bfiller, hey, who would i ask about maliit questions?
[19:42] <ogra_> thanks
[19:42] <bfiller> ogra_: why disable them? they won't be installed by default and will be there if designers or someone want to install
[19:42] <bfiller> cwayne: tmoenicke or me
[19:43] <ogra_> bfiller, ok, fine, i have no clue whats in them, i always  only used the video and music lens
[19:43] <ogra_> if the content is fine for the archive i'll happily upload as is
[19:43] <cwayne> bfiller, so we're trying to do a chinese localized image, but maliit isn't fitting on the screen (the keys are too big).  any idea on how to fix it?
[19:45] <bfiller> ogra_: I think the plan was to ultimately  drop this package completely (which I still favor). But if we're going to upload I'd do it as is
[19:45] <bfiller> cwayne: that worked at one point
[19:45] <bfiller> for last chinese demo
[19:45] <ogra_> bfiller, well, we stil want to be able to test video playback
[19:45] <ogra_> and the UI looks really empty without them
[19:46] <ogra_> let me ask asac
[19:46] <ogra_> i can indeed just rip them out
[19:46] <cwayne> bfiller, hm, but quite a bit's changed since then i think
[19:46] <bfiller> ogra_: yeah, regarding if the content is suitable for the archive - I don't know if I can answer that. I *think* it is but..
[19:47] <jdstrand> larsu: hi! I'm affected by bug #1215644
[19:47] <asac> ogra_: what?
[19:47] <jdstrand> larsu: that bug says it is fixed in 13.10.1+13.10.20130830.2-0ubuntu1, but I have 13.10.1+13.10.20130903-0ubuntu1 installed
[19:48] <jdstrand> larsu: there is a comment about unity8 needing to also be fixed. should it have its own task?
[19:48] <bfiller> cwayne: yes quite a bit has changed and probably it's broken now
[19:49] <bfiller> cwayne: we've just redone how we are doing layouts and that will affect chinese and other langs. Is slated for this month to fix the language support
[19:49] <ogra_> asac, i want to be done with the remaining PPA stuff by end of the week (or today)
[19:49] <ogra_> asac, which measn either uploading the demo stuff to the archive or to rip it out
[19:50] <bfiller> ogra_, asac : reforwarding the email thread we had on this subject..
[19:50] <jdstrand> larsu: I'm adding the unity8 task. please adjust as necessary
[19:51] <mhall119> pmcgowan: I don't use qmake much, so no I haven't seen it
[19:52] <jdstrand> ChickenCutlass: hey, if you haven't seen it yet, can you have someone look at bug #1223586
[19:53] <ChickenCutlass> jdstrand, ack
[19:53] <jdstrand> ChickenCutlass: whoever looks at it can talk to sarnold (he conducted the review)
[19:53] <jdstrand> ChickenCutlass: thanks! :)
[19:53] <ChickenCutlass> rsalveti, ^^^^^^
[19:54] <rsalveti> jdstrand: ChickenCutlass: yup, saw that yesterday, thanks
[19:54] <rsalveti> will take a better look later this week
[19:54] <jdstrand> cool
[19:56] <ChickenCutlass> rsalveti, looks like most of these are just legacy stuff left around and never cleaned up
[19:56] <ChickenCutlass> rsalveti, after the hacking to just get it to work
[19:59] <rsalveti> ChickenCutlass: right, but there are some comments in there regarding the original linker as well
[19:59] <rsalveti> but will reply it in details later
[19:59] <ChickenCutlass> right
[20:00] <asac> ogra_: problem is solved ... so no sms
[20:00] <asac> :)
[20:01] <ogra_> yay
[20:09] <ogra_> bfiller, so the final decision is to rip all demos out of the imagfe but keep it available in the (disabled) PPA
[20:09] <bfiller> ogra_: works for me :)
[20:18] <prp-e> Hi guys. Is the ubuntu touch installable on ARM boards?! like cubieboard?!
[20:20] <timse> hi is there a updater or auto updater already installed on ubuntu phone?
[20:20] <timse> im using a nexus 4
[20:22] <pmcgowan> timse, yes, the ubuntu-system image has auto updates
[20:23] <pmcgowan> prp-e, not that I know of, folks mainly porting to android devices
[20:23] <wellsb> beuno: Since a fix seems to have been committed for the icon_url issue in the click store, is there any action I need to take to get things on course?  Should I re-upload icon64, or will the server rectify things automatically?
[20:23] <timse> is there a gui for the updater?
[20:23] <prp-e> Ok. I work on another mobile linux distro.
[20:25] <pmcgowan> timse, yes its in the settings panel - update, the gui is still in development but it works
[20:25] <timse> thx
[20:26] <timse> im on an daily build will be the update process the same like on ubuntu desktop - i will get dailys as long as the stable versionis not finished and the stable version will be updated then?
[20:32] <timse> please answer thats my last question ;)
[20:37] <pmcgowan> timse, its till in development, so you will get updates each time an image passes all required tests
[20:37] <timse> yes i know
[20:37] <pmcgowan> timse, I would need to check the default once 13.10 releases
[20:38] <timse> but will be the stable when its released be flasht if im on daily buidls?
[20:38] <pmcgowan> timse, whether you need to then opt in again for dailies or opt out
[20:38] <pmcgowan> yes
[20:38] <timse> thx
[20:39] <grantbow> After dismissing it, how can I relaunch the intro tour?
[20:47] <wellsb> beuno, JamesTait: I guess when click package index is updated to reference icon_urls.64 instead of icon_url, there won't be a problem.  I'll just wait for this fix
[20:48] <larsu> jdstrand: thanks. It's blocked on a merge to unity, which is blocked by a qmenumodel release, which is blocked for reasons that are beyond me :)
[20:50] <jdstrand> larsu: ack
[20:55] <grantbow> Quick question: how can I relaunch the intro tour after dismissing it? This is a great demo for the SF Ubuntu Hour.
[20:57] <plars> grantbow: I think 'dbus-send --system --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts/User32011 org.freedesktop.DBus.Properties.Set string:com.canonical.unity.AccountsService string:demo-edges variant:boolean:true' should work
[21:00] <grantbow> plars: thanks! testing now
[21:01] <JamesTait> wellsb, I think when the fix gets rolled out to production we'll probably re-index, so if your app already has an icon_64 it should Just Work.
[21:02] <wellsb> JamesTait: Excellent.  Thanks
[21:03] <robert_ancell> mterry, btw that VT patch seems to be all kinds of wrong, but I assume it's blocking the phone stuff so we can sort it out properly in the future :)
[21:08] <grantbow> plars: I put it in a script named demo and it returned "method return sender=:1.28 -> dest=:1.49 reply_serial=2"
[21:08] <grantbow> plars: but it didn't launch the intro tour
[21:08] <plars> grantbow: yep, now you can either reboot the device, or you should be able to just do somethin like 'sudo -iu phablet /sbin/restart unity8'
[21:09] <grantbow> ah
[21:09] <ogra_> shouldnt need /sbin :)
[21:11] <mterry> robert_ancell, sorry!  :-/
[21:11] <mterry> robert_ancell, I left it overnight for ya, but wanted to squeeze it in today
[21:11] <mterry> robert_ancell, talk to me about how wrong it is
[21:11] <anders3408> hey .. Does ubuntu touch uses /cache partition ? as somehow that partitions it not being added to /etc/fstab
[21:12] <ogra_> anders3408, only for image upgrades
[21:12] <ogra_> (via recovery mode)
[21:12] <anders3408> so on bootup it shouldnt be needed ?
[21:12] <ogra_> nope
[21:13] <anders3408> ogra_:  would you mind to look at my dmesg, http://paste.ubuntu.com/6094290/ as i cant figurer out why some processes is being terminated
[21:13] <anders3408> like ureadahead and upstart-local-bridge and lxc-android-config and lxc-android-boot
[21:15] <grantbow> plars: that worked, thank you very much!
[21:15] <plars> grantbow: np :)
[21:16] <robert_ancell> mterry, the main bit is we're solving an issue in logind in the DM - we're inferring that VTs are not available by vt_get_active() failing and then picking the magic number 1
[21:17] <mterry> robert_ancell, well, it's not so much a magic number as just the default, eh?
[21:17] <robert_ancell> mterry, I guess we need to make logind handle there not being VTs, which fits with the plans for it afaik
[21:18] <mterry> robert_ancell, because on the machine, /sys claims we're at VT 1
[21:18] <robert_ancell> mterry, did you confirm that VT support is disabled in the kernel?
[21:18] <Mark_____> hi
[21:18] <mterry> robert_ancell, I don't know what the story is with VTs in touch
[21:18] <Mark_____> hi guys im a noob here and i have some questions anyone care to help?
[21:19] <robert_ancell> mterry, anyway, I don't think there'll be any likely side-effects. Just need to remove it / change it once all this works properly
[21:19] <mterry> robert_ancell, I grant it's a bit of a hack.  But it seemed harmless (fallback for a fallback) and not a *crazy* thing to do
[21:19] <mterry> robert_ancell, sure
[21:19] <Mark_____> my problm is I have installed Ubuntu touch for the nexus4 and wanted to go back to android
[21:20] <robert_ancell> mterry, btw, where's the 1.7.15 commit?
[21:20] <plars> ogra_: do you know if this build we just got is likely to have a fix for the problems we saw this morning?
[21:20] <ogra_> anders3408, hmm, upstart usually writes logsinto /var/log/upstart for the jobs, take a look in there
[21:21] <anders3408> ogra_:  i dont have var/log at all , meaning log isnt found, but var is ofc :)
[21:21] <Mark_____> i am using a windows7 pc, i have the factory image of google, my pc recognized my device as nexus 4 but when i type adb reboot-bootloader its not working
[21:21] <ogra_> plars, can you quickl recap what that was ?
[21:21] <genii> Mark_____: https://wiki.ubuntu.com/Touch/Install#Restoring_Android
[21:21] <mterry> robert_ancell, did I not push that?
[21:21] <Mark_____> yup i did see that
[21:21] <robert_ancell> mterry, It seems not
[21:21] <plars> ogra_: lots of test failures, seemingly due to the toolbar menu being missing
[21:22] <anders3408> ogra_:  damn :) didnt look at var/log for the latest build :)
[21:22] <Mark_____> @genii i did see that but i cant seem to enter bootloader on my device
[21:22] <anders3408> now its there
[21:22] <ogra_> plars, i think the new unity8 was supposed to fix that ... iirc ricmm should know
[21:22] <mterry> robert_ancell, pushed.  I also cleaned up a few small oddities in the tree that were different from the tarball we shipped
[21:23] <mterry> debuild was giving me warnings about them
[21:23] <plars> ogra_, ricmm: looks like no I guess, no new unity8 in this build and early indications are that the same failures are there
[21:23] <robert_ancell> mterry, do you want to send the announcement to the lightdm list?
[21:23] <mterry> robert_ancell, sure.  You need like a README.release or something
[21:24] <robert_ancell> mterry, yeah, I was impressed you inferred everything else :)
[21:24] <Mark_____> :(
[21:25] <mterry> robert_ancell, sorry for going sorta behind your back on this one
[21:25] <genii> Mark_____: Is it seeing the device when you do: adb devices
[21:25] <mterry> robert_ancell, what is the mailing list?
[21:25] <ogra_> plars, seems its still in proposed
[21:26] <robert_ancell> mterry, lightdm@lists.freedesktop.org
[21:26] <mterry> robert_ancell, you might have to approve the message
[21:26] <robert_ancell> mterry, "I approve of this message"
[21:26] <mterry> :)
[21:26] <robert_ancell> mterry, just copy the ones I send - it's basically just the NEWS file
[21:27] <robert_ancell> mterry, http://lists.freedesktop.org/archives/lightdm/2013-September/000444.html
[21:28] <mterry> robert_ancell, yup, just sent
[21:29] <grantbow> plars: would it be ok if I blog the tour restart solution to planet.ubuntu.com and attribute your help in this channel?
[21:30] <grantbow> oops, ping timeout
[21:31] <anders3408> hmmm ogra_ so syslog says something usefull : ubuntu-phablet powerd[1159]: Could not determine device, running without config
[21:31] <anders3408>  
[21:34] <anders3408> does that make sense ogra_
[21:35] <anders3408> have added devicename.conf and rules to data partition*
[21:35] <ogra_> well, i think powerd uses the android bits (getprop) to determine the device name
[21:35] <ogra_> which only works if your container is fully working
[21:36] <anders3408> just reflashing atm then ill take a look at those /var/log/
[21:37] <ogra_> (the lxc-android-* upstart jobs start the container.... /var/log/upstart/ might have some info ... or /var/log/lxc)
[21:37] <anders3408> if it dont makes sense to me, will you be able to see anything from a syslog ? or
[21:37]  * ogra_ has to leave soon 
[21:37] <anders3408> ill look :)
[21:38] <anders3408> hmmm , no /var/log just after first flash... should it take some time before that part is made ?
[21:40] <ogra_> no, should be there by default
[21:40] <anders3408> hmmm.. seemse like twrp does not do its job correct all times
[21:41] <anders3408> just first time i flashed the same files, fstab was correct, now i just wiped all from twrp and reflashed, and fstab is empty ogra_
[21:43] <ogra_> fstab is generated on first boot by the lxc-android-boot.conf job
[21:43] <anders3408> ahhh okay :)
[21:45] <mterry> robert_ancell, awaits approval
[22:03] <anders3408> ogra_: if you still are on : lxc_conf - No such file or directory - stat(/proc/404/root/dev/lxc/tty2)
[22:07] <anders3408> ahhh :DCould not open device config /usr/share/powerd/device_configs/config-find5.xml: No such file or directory
[22:07] <didrocks> ogra_: here?
[22:08] <infinity> didrocks: I'll punt a build in ~3m when this publisher run is done.  Looks like everything should be in.
[22:08] <ogra_> didrocks, on my way out (shuttle bus comes in 5)
[22:09] <didrocks> infinity: ah, excellent, indeed, it's published in launchpad, we just need the publisher run to finish
[22:09] <didrocks> thanks!
[22:09] <ogra_> anders3408, yeah, obviously your container didnt start
[22:09] <didrocks> ogra_: ok, so infinity it triggering the build, we can SHIP IT! ;)
[22:09] <anders3408> ogra_:  Could not open device config /usr/share/powerd/device_configs/config-find5.xml: No such file or directory :)
[22:09] <didrocks> is*
[22:09] <didrocks> infinity: see you in a minute
[22:10] <ogra_> anders3408, sorry, i fear we have to continue tomorrow
[22:10] <ogra_> (we have to leave the office here)
[22:10] <anders3408> ogra_:  nvm :) now i got started :) and finally can get some good logs
[22:11] <ogra_> :)
[22:11] <anders3408> then i can see what i can find from there :)
[22:11] <ogra_> yeah
[22:11] <anders3408> oppo find  5 is very much like mako
[22:11]  * ogra_ waves 
[22:31] <mterry> Mirv, re: tests in some of the qt module packages, can't we run them in xvfb?
[22:31] <mterry> robru, ^
[22:32] <robru> mterry, mirv is unlikely to be around for at least 8 more hours I think... I'm emailing him.
[22:33] <mterry> oh ok
[22:42] <crocket> Can I install ubuntu on iPad 3?
[22:43] <anders3408> crocket: nope
[22:43] <crocket> Can I install ubuntu on android tablets?
[22:44] <anders3408> it depends on which tablet
[22:44] <anders3408> but some has it
[22:44] <wilee-nilee> crocket, There is a saucy download, however this is in development.
[22:44] <anders3408> crocket:  here is a general list : https://wiki.ubuntu.com/Touch/Devices/
[22:44] <crocket> anders3408: When will I see the first ubuntu phones and tablets?
[22:45] <anders3408> wilee-nilee:  you not saying that there is being worked on a ubuntu touch for ipad 3 :O
[22:51] <anders3408> wilee-nilee:  is it possible that you can take a log at a syslog for me ?  or any of your other maby ?
[22:51] <anders3408> im trying to port ubuntu touch to a new device much like mako
[22:51] <anders3408> http://paste.ubuntu.com/6094672/
[22:53] <anders3408> mterry or robru ?
[22:58] <wilee-nilee> anders3408, Ipad I have no idea I doubt it, I have none installed as of now. saucy and the pad version are both in development though
[22:58] <anders3408> ahh that sounds more likely
[22:58] <anders3408> wilee-nilee: if you have time, it would be nice if you would look at my log from above paste link
[22:59] <wilee-nilee> anders3408, I'm not really a log reader, so not your best help is all. ;)
[22:59] <anders3408> uhm okay, but if i have that debug line in the kernel cmd line, will that break bootup  ?
[23:15] <cjwatson> asac: sorry, I was putting the kids to bed and fell asleep in the process.  Did this copy thing I see in scrollback get sorted?
[23:16] <cjwatson> asac: also, re future expansion of armhf, it occurred to me later that the answer is easy: we'll be adding arm64 builders soon enough, and those should be able to build armhf too
[23:45] <robru> anders3408, hi, what's up?
[23:47] <anders3408> hi robru , i am trying to port ubuntu touch to a new device , but it gives me some issues. so far i still have no screen. syslog looks fine in the start but then it its giving me trouble, perhaps you could take a look at it ?
[23:48] <robru> anders3408, nope, i don't know the first thing about that stuff. i only ever used it on a nexus 7, phablet-flash does all the work for me. wouldn't even know where to begin. sorry
[23:48] <anders3408> ew :(
[23:48] <iBotPeaches> is that the oppo find5?
[23:48] <anders3408> iBotPeaches:  yep
[23:48] <iBotPeaches> I could never get my display to show, only adb working
[23:49] <anders3408> what did your syslog ends up with ?
[23:49] <iBotPeaches> plugging it in now, its been a few days. gonna grab new logs
[23:50] <cjwatson> asac: looks like it got sorted.  I posted the relevant log entry over in #ubuntu-release
[23:57] <niemeyer> Would anybody know what's the status of qt 5.1 re. Ubuntu 13.10?
[23:58] <niemeyer> I know about the PPA, but I have no idea if that's likely to make into 13.10 itself or if it's not going to make it