[00:17] <plars> things are looking quite a bit better on the automated tests with this one - mir is still pretty rough of course
[08:36] <Saviq> lool, https://code.launchpad.net/~saviq/unity8/revert-r376/+merge/189455
[09:11] <lool> cjwatson: gnutls26 >> sure; thanks for the heads up
[09:11] <lool> Saviq: looking
[09:12] <lool> rsalveti: ok thanks
[09:12] <Saviq> lool, I've a package coming up
[09:12] <Saviq> lool, like in 2 mins
[09:13] <cjwatson> lool: uploaded, thanks
[09:13] <cjwatson> http://people.canonical.com/~ubuntu-archive/proposed-migration/saucy_uninst.txt is actually looking almost acceptable now, with the ignorable exception of arm64
[09:14] <lool> Saviq: cool
[09:15] <lool> Saviq: should we sync a bit for plan over the week-end?
[09:15] <lool> I do have some other planned outside activities too  :-)
[09:15] <lool> Saviq: so right now, we have the reverts in archive, I built an image with them; it's not the highest pass rate ever, but nothing to be too ashamed off and it generally works; most AP fails are in apps, a brightness thing in unity8 AP tests
[09:16] <lool> generally speaking, I would be happy to promote is and call SF done
[09:16] <lool> ogra_: ^ your toughts
[09:16] <lool> *thought
[09:16] <ogra_> lool, i'm just flashing
[09:16] <ogra_> (morning etc)
[09:16] <lool> ogra_: Morgen ! :-)
[09:17] <Saviq> lool, ogra_ the biggest difference from my PoV is WiFi password input, which is in the indicator in the rolled back unity8, unity-notifications, indicator-network
[09:17] <lool> Saviq: Now Mirv actually did the testing of the CPU pegging unity8 and was happy with it, so what I'd like is either getting us all these revs into the image with the fix you've identfied
[09:17] <ogra_> the failures look like many of them are toolbar related
[09:17] <lool> Saviq: Yes, I rolled back the 3
[09:17] <Saviq> lool, yeah, I'd rather do that
[09:17] <ogra_> (from the apps)
[09:18] <Saviq> lool, http://people.canonical.com/~msawicz/unity8/ here is unity8 trunk + the fix/revert
[09:18] <lool> Saviq: so we do that on top of what was tested yesterday?  I think you have landed other things in unity8 trunk already
[09:19] <Saviq> lool, we only have a revert and a test-drop in trunk over what's released currently
[09:19] <Saviq> lool, so with the "new revert" we'd have two reverts and the test drop, so rather safe
[09:19] <Saviq> lool, and that's what you have in the packages I put up
[09:20] <ogra_> bug 1235480
[09:21] <lool> Saviq: looking
[09:22] <lool> Saviq: right, trunk looks good
[09:22] <lool> Saviq: I'll take the previous unity-notifications debs to test your unity8 build
[09:22] <Saviq> lool, so if you confirm the fix/revert helps with CPU - let's merge, release
[09:23] <Saviq> lool, yeah, it needs the "new" unity-notifications and indicator-client
[09:23] <Saviq> s/-client/-network/
[09:23] <Saviq> lool, so full dist-upgrade + my packages should work good
[09:25] <lool> Saviq: well I just took image 82 + your pcakages + old unity-notifications (qtdeclarative5-unity-notifications-plugin)
[09:26] <lool> just trying to unmount now
[09:27] <Saviq> lool, old unity-notifications and indicator-network will conflict with my packages - you need all three upgraded to their latest releases from trunks
[09:27] <Mirv> lool: yeah I didn't notice the CPU hoggage, it didn't seem bad performance wise as such
[09:28] <Mirv> maybe the autopilot tests themselves should notice it
[09:28] <Mirv> "idle, check cpu usage"
[09:30] <Saviq> lool, that is to say "sure, it'll work, but expect issues with WiFi password entry"
[09:30] <lool> Saviq: "old" means the one before my revert
[09:30] <Saviq> lool, ok then - yes :)
[09:30] <lool> Saviq: yesterday I reverted indicator-network, unity8, and unity-notifications in archive
[09:31] <lool> so I might get FS corruption, hopefully not
[09:31] <Saviq> lool, yeah, saw that now
[09:32] <lool> Saviq: so I have 7.82+13.10.20131004.1-0ubuntu2~sbuild3 installed, and top if quiet  \o/
[09:33] <lool> *is quiet
[09:33] <lool> screen of or screen on
[09:33] <lool> Saviq: so that looks good
[09:34] <lool> Saviq: let's upload all of this
[09:34] <Saviq> lool, yay
[09:34] <Saviq> lool, FYI some kind of SDK weirdness happened there - still need to investigate
[09:35] <Saviq> lool, the spinner 'caused the CPU usage even when it was, in theory, off and invisible
[09:35] <Saviq> -'
[09:36] <lool> Saviq: you mean in the code that you reverted, it should not be using CPU but is due to some SDK bug?
[09:37] <lool> Saviq: to clarify: are we good with just the revert we tested, or do we need another change for that spinner thing?
[09:39] <Saviq> lool, yes
[09:39] <Saviq> lool, we're good
[09:40] <Saviq> lool, I reverted the change that was broken - and was due to a SDK bug
[09:40] <Saviq> lool, with my MP unity8 is no-CPU-hogging anymore
[09:40] <Saviq> lool, but we still need to merge / release it
[09:40] <lool> Saviq: I've happroved the mp
[09:40] <Saviq> lool, thanks
[09:41] <lool> Saviq: I'm preparing the other uploads
[09:41] <lool> Saviq: will send MPs to resync bzr trunks with changelogs of uploaded reverts
[09:41] <Saviq> lool, yup, let me know if you need me to approve
[09:41] <lool> (since nothing sits in trunk, can't ask cu2d to resync somehow)
[09:42]  * Saviq hates nautilus + gvfs recently
[09:43] <Saviq> it was working so well last release, but with the new nautilus all kind of flakiness happens
[09:45] <lool> that reminds me, I've noticed now that mtp coming up kills my adb shell connection for a sec
[09:45] <lool> then it comes back
[09:45] <lool> like the connection gets closed, I have to reopen it
[09:50] <lool> uploaded indicator-network
[09:50] <lool> it will be blocked in unapproved, then in proposed
[09:51] <lool> Saviq: https://code.launchpad.net/~lool/indicator-network/resync-indicator-network-changelog/+merge/189458
[09:52] <Saviq> lool, +1
[09:52] <Saviq> lool, actually +2 - mtp is flaky for me, too - but that's with android as well
[09:54] <ogra_> setting a property resets the gadget
[09:55] <ogra_> when mtp comes up it adds a property to the gadget settings
[09:56] <lool> Saviq: https://code.launchpad.net/~lool/unity-notifications/resync-indicator-network-changelog/+merge/189459
[09:56] <lool> ogra_: aha
[09:56] <lool> ogra_: so it's "by design"
[09:56] <ogra_> yeah
[09:57] <Saviq> lool, +1
[09:57] <lool> Saviq: sadly, indicator-network needs someone from release team to ack
[09:57] <ogra_> and setting the property persistent would make your gvfs on the desktop freak out
[09:57] <ogra_> since there is an mtp device but no server attached
[09:57] <lool> Saviq: and we're saturday, so might take some time
[09:57] <Saviq> lool, but we can merge the changelog regardless, right?
[09:57] <lool> I think so
[09:57] <ogra_> (so gvfs goes into a loop of mount attempts spilling errors)
[09:57] <lool> Saviq: I've put a block hint in place so that we can upload all 3 and let them in -proposed
[09:58] <lool> so that we don't get half in unapproved half in archive
[09:58] <Saviq> lool, oh cool
[09:58] <Saviq> lool, and then just flip the switch to let through to saucy, got it
[09:58] <Saviq> lool, thanks!
[09:58] <lool> Saviq: right, so I can upload unity8 when it's there
[09:59] <Saviq> lool, granted, the deps should prevent going into an inconsistent state
[09:59] <Saviq> lool, actually there's one question you might be able to answer
[09:59] <lool> Saviq: the provides are there, but I didn't update deps for indicator-network
[10:00] <Saviq> lool, ah right
[10:00] <Saviq> lool, we had a situation last week when unity-notifcations Provides was already unity-notifications-impl-2 (in the upstream merger's local repo)
[10:00] <Saviq> lool, but unity8 Depends was still at unity-notifications-impl-1, which was available in saucy
[10:00] <Saviq> lool, and apt crapped out when trying to install that unity8 version
[10:01] <lool> which was the goal?
[10:01] <Saviq> lool, is it not smart enough to install a non-highest version to fulfil the deps?
[10:01] <lool> ah no
[10:01] <lool> it will select the highest version
[10:01] <lool> it's basically a complex scoring mechanism
[10:01] <lool> which I don't know all the details of
[10:01] <lool> but a higher version will get lots of point
[10:02] <Saviq> lool, mhm
[10:02] <lool> a downgrade wont happen unless your force it
[10:02] <Saviq> lool, yeah, but it wasn't about a downgrade
[10:02] <Saviq> lool, it was about installing (new package) a non-highest version
[10:02] <Saviq> which I was hoping would work
[10:02] <lool> that I would expect to work
[10:02] <lool> but then maybe not  :-)
[10:03] <lool> Saviq: but if you remember the specifics, I guess some APT maintainers could possibly look into it
[10:03] <Saviq> lool, fortunately we even have a log - 'cause it was on mediumtests
[10:03] <lool> Saviq: Ok, so we're waiting on a bunch of things right now
[10:04] <Saviq> lool, yup, all things to merge
[10:04] <lool> to sum up: a) upstream merger picks up your MP, merges it b) I press the cu2d buttons and get that uploaded c) release team reviews + approves new indicator-network d) we unblock all 3 e) we build animage
[10:04] <lool> ogra_: what did you think of latest image?
[10:05] <lool> ogra_: should I promote it?
[10:05] <lool> ogra_: we might get another SF one EOD
[10:05] <ogra_> lool, well, just had to reboot trying to send an SMS
[10:05] <lool> ogra_: but I'd rather we promote this one if you feel it's good enough
[10:05] <lool> ogra_: what happened?
[10:05] <ogra_> it hung
[10:05] <lool> unity8?
[10:05] <ogra_> not sure
[10:06] <lool> any crash files?
[10:06] <ogra_> i made a call, afterwards saved the contact ... (which used some http formatting for the plus sign in +49 ... which in turn couldnt send to that number full of special chars ...)
[10:07] <lool> Saviq: I dont think we can fix the current SF images much more over the week-end; the original plan was to fix a couple of critical issues and switch to Mir; the critical issues were input in the webbrowser (might be related to volume up / down or not), and input focus on snap decisions
[10:07] <ogra_> then i edited the contact to have a proper +49 ... got an error that contact saving failed and after that no input was possible anymore
[10:07] <lool> Saviq: I can't fix the input issues myself, but if they get fixed I can land the "switch the default to Mir" over the WE
[10:07] <lool> ogra_: fun
[10:07] <Saviq> lool, nah, let's get back to it on Monday
[10:07] <lool> ogra_: but is it a _regression_?  :-)
[10:08] <Saviq> lool, there's no one working on those
[10:08] <Saviq> lool, let's all have our WE now
[10:08] <Saviq> or after we fix SF
[10:08] <lool> ogra_: is this something you experienced successfully in the past?
[10:08] <lool> ogra_: basically, would this image be more or less substantially better than the previous stable one?
[10:08] <ogra_> lool, the mangled number definitely is ...
[10:09] <ogra_> lool, but i'm not sure thats a blocker
[10:09] <lool> I fear we're running out of runway
[10:09] <ogra_> right, lets promote it
[10:09] <ogra_> after reboot there dont seem any issues
[10:10]  * lool reads ~ogra/README.mark-current
[10:10] <ogra_> should i ?
[10:10] <lool> ogra_: so mark-current is for the cdimage part
[10:10] <ogra_> (if you feel safer with that)
[10:10] <lool> ogra_: and the second is for system-image?
[10:10] <ogra_> right, that needs to happen first
[10:10] <ogra_> yep
[10:10] <lool> ogra_: Actually, I like to do it because you're around  :-)
[10:10] <lool> ogra_: build is is 82?
[10:10] <ogra_> just call both commands in succession with the right numbers
[10:11] <ogra_> 82 for system image
[10:11] <lool> ah and for cdimage I need to use the ubuntu version?
[10:11] <lool> so 20131004.1?
[10:11] <ogra_> 20131004.1
[10:11] <ogra_> right
[10:12] <lool> the second one churns
[10:12] <lool> I guess deltas
[10:12] <lool> done
[10:12] <ogra_> yeah, the second one takes a bit
[10:13] <lool> ogra_, popey: 82 promoted!
[10:13] <ogra_> the first one just sets a link
[10:13] <ogra_> yay
[10:13] <lool> ogra_, popey: Bulding an 83 tonight with updated 83 and SF, but otherwise leaving it there
[10:13] <ogra_> popey, thats 82/20131004.1
[10:13] <popey> sweet!
[10:13] <lool> might want to promote 83
[10:13]  * popey mails
[10:13] <lool> if you guys feel like it
[10:13] <popey> ok, I'll be around
[10:13]  * ogra_ cant promise but will help if he is around
[10:14] <lool> it's mostly what was in 81, with no CPU hogging, so 82 + new unity8
[10:14] <lool> and indicator-network
[10:14] <lool> ogra_: yeah if you can't then so be it
[10:14] <ogra_> dont you need a FFe for that one ?
[10:14] <lool> we can always promote it monday
[10:14] <ogra_> indicator-network is a desktop package
[10:14] <lool> ogra_: it says ubuntu-desktop, but I don't actually see it pulled by ubuntu-desktop
[10:14] <lool> an dseeded-in-ubuntu also doesn't
[10:15] <ogra_> intresting
[10:15] <lool> ogra_: well, I don't understand why it's still in the desktop packageset
[10:15] <ogra_> i always thought we have it installed
[10:15] <ogra_> missing meta update ?
[10:15] <ogra_> or a dep ...
[10:16] <lool> Saviq: So I'll step away for a bit, possibly only back after lunch + some family activities outside, near 5pm UTC+2
[10:16] <Saviq> lool, yeah, enjoy
[10:16] <lool> Saviq: if upstream merger doesn't run or fails, would you merge by hand?
[10:16] <Saviq> lool, will do
[10:16] <lool> I might have commit access, not sure
[10:17] <lool> Saviq: thanks for the fix, will be back in a bit
[10:17] <Saviq> lool, I'll force-hand generic-land
[10:17] <Saviq> lool, he has access for sure :)
[10:17] <popey> ogra_: i dont see changes at http://people.canonical.com/~j-lallement/touch/changes/
[10:17] <cjwatson> Saviq: http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2012-01-29-apt-resolver-bugs.html has some random wittering about how to investigate apt resolver bugs, if it happens to be useful
[10:17] <Saviq> cjwatson, thanks - I'm not really sure it's a bug, and rather a feature ;)
[10:18] <Saviq> cjwatson, but will be a useful read anyway
[10:18] <cjwatson> well, how to investigate the algorithm anyway.  it's a useful though tricky thing to understand
[10:18] <lool> popey: http://people.canonical.com/~ogra/touch-image-stats/20131004.1.changes has some
[10:18] <popey> yeah, i have that
[10:19] <popey> i usually link to the pretty version jibel has
[10:19] <popey> nvm
[10:19] <lool> ah
[10:19] <popey> will link and say it's pending
[10:19] <popey> given we can guess the url ☻
[10:19] <lool> I guess it's running from jibel's desk!  :-)
[10:19] <lool> popey: ah you probably want the diff between stbale images
[10:19] <lool> I forgot where ogra has it
[10:24] <popey> lool: no, I deal with that
[10:24] <popey> lool: I manually merge the individual diffs
[10:27] <lool> ok
[10:31] <popey> mail sent
[10:34] <lool> popey: thanks!
[10:35] <Saviq_> ugh
[10:35] <Saviq_> ok, so upstream merger is broken - the old IP was hardcoded in the jobs ;(
[10:36] <lool> gosh, where is it hardcoded?
[10:37] <popey> I love it when we move stuff to a new IP. Great way to shake out these kinds of issues. #glasshalffull
[10:40] <Saviq_> popey, yeah, and finally *name it* somehow
[10:40] <popey> ☻
[10:41] <Saviq_> popey, and whoa! here's an idea - let's provide a DNS server behind the QA VPN!
[10:41] <popey> Steady on there! ☻
[10:41] <Saviq_> that would be like The Enterprise
[10:41]  * popey emails /etc/hosts files around to everyone
[10:41] <popey> ghetto dns
[10:41] <Saviq_> rotfl
[10:42] <Saviq_> bugs against ps-qa-tools?
[10:42] <popey> pass
[10:43] <lool> actually some other jenkins dep had the great idea to use the public facing jenkins.qa.ubuntu.com to get a stable name  :-)
[10:43] <lool> I don't remember which cron it was that got pasted here, but because it used jenkins.qa.ubuntu.com instead of 10.x.x.x it was immune to the change  :-)
[10:44] <lool> Saviq: where's this hardcoded IP you say?
[10:44] <Saviq_> https://bugs.launchpad.net/ps-qa-tools/+bug/1235621
[10:45] <Saviq_> lool, so, first of all the links to jobs from history don't work (that, hopefully, is a configuration issue - otherwise only new jobs will have correct jobs cross-links)
[10:45] <Saviq_> lool, but http://10.97.0.26:8080/job/generic-mediumtests-saucy/4632/console
[10:46] <Saviq_> downloads artifacts directly from the old IP
[10:47] <lool> indeed
[10:47] <jibel> popey, my DSL died after a storm and have limited connectivity. I'll relocate the job that publish changes during the week end
[10:48] <popey> jibel: ouch!
[10:48] <popey> jibel: thanks.
[10:49] <lool> Saviq: I've just checked and don't have permission to fix it
[10:49] <Saviq> lool, yeah, me neither
[10:49] <lool> mailing Francis + Larry
[10:49] <Saviq> fginther, https://bugs.launchpad.net/ps-qa-tools/+bug/1235621 https://bugs.launchpad.net/ps-qa-tools/+bug/1235622
[10:51] <lool> Saviq: ming merging unity8 by hand?
[10:51] <lool> Saviq: (I've mailed them now, listing bugs and Cc:ing you)
[10:51] <Saviq> lool, already there
[10:51] <Saviq> lool, everything's is merged by now
[10:51] <lool> let's see if cu2d is still working
[10:52] <Saviq> lool, it's not been moved (yet), so hopefully yeah
[10:52] <Saviq> lool, but it'd make sense to solve the above bugs for them *before* they move, yes
[10:52] <lool> A version (7.82+13.10.20131004.2-0ubuntu1) is available at the destination for that component but is not in trunk which is still at 7.82+13.10.20131004.1-0ubuntu1. Ignoring that component for source: unity8, branch: lp:unity8, series: saucy.
[10:53] <lool> guess we need to merge the changelog there too
[10:54] <lool> Saviq: https://code.launchpad.net/~lool/unity8/add-reverts-in-unity8-changelog/+merge/189463
[10:55] <lool> Saviq: could you hand merge this one if you're ok with it, and then I'll run cu2d again?
[10:56] <lool> off for lunch
[10:57] <Saviq> lool, going
[10:57] <Saviq> lool, it's going to be merged in 30s
[10:57] <Saviq> lool, if you can kick off cu2d again
[10:58] <Saviq> lool, ready
[11:02] <lool> ok
[11:03] <lool> running
[11:22]  * ogra_ notes that the session upstart goes wild after some time on 82
[11:24]  * ogra_ sees a load of 17.08
[11:27] <ogra_> (using Mir btw)
[11:27] <fginther> Saviq, the IP has been updated
[11:28] <Saviq> ogra_, oh, I wonder if it'd be bug #1235190
[11:29] <ogra_> Saviq, qwll, i suspect it is also  some issue with upstart
[11:30] <ogra_> i see init consuming a lot of CPU
[11:30] <Saviq> ogra_, although CPU was idle for us mostly - same for IO and RAM - everything looked fine resource-wise, only display slowed down to a crawl
[11:30] <Saviq> ogra_, so yeah - not the same - our issue was with idle CPU
[11:32] <ogra_> root@ubuntu-phablet:/# ls /var/crash/|wc -l
[11:32] <ogra_> 6
[11:32] <ogra_> bah
[11:32] <ogra_> i had cleared it for the last reboot
[11:33] <ogra_> its only up since a few minutes
[11:34] <ogra_> seems /usr/lib/arm-linux-gnueabihf/upstart-app-launch/zg-report-app is one of the crashers
[11:36] <ogra_> hwee
[11:36] <ogra_> whee even ...
[11:37] <ogra_> and the session upstart is leaking ram like crazy
[11:37] <ogra_> seems RES rises by 2M every second while the screen is on
[11:38] <ogra_> it is at 141M now
[11:38]  * ogra_ makes the image writable and installs last nights upstart upload
[11:39] <ogra_> i wonder if that fixes it
[11:41] <popey> i have one unity crash and one _usr_lib_arm-linux-gnueabihf_upstart-app-launch_zg-report-app.32011.crash
[11:41] <popey> but don't see the memory leak
[11:41] <ogra_> using Mir ?
[11:43] <lool> ogra_: it might be when dealing with crash files
[11:43] <lool> ogra_: there's a file watch on this
[11:43] <ogra_> lool, does upstart deal with them in the session ?
[11:43] <lool> hmm no, you're right
[11:43] <ogra_> i thought thats the system upstart
[11:43] <lool> ogra_: it could logging
[11:43] <lool> ogra_: ls -ltr .cache/upstart/ perhaps
[11:44] <ogra_> well, i installed the ubuntu6 package from the archive
[11:44] <ogra_> lets see how this behaves
[11:46] <ogra_> no wilddly growing files in the logdir
[11:47] <ogra_> the session init is at 27M already
[11:47] <ogra_> and pumped itself to 32M while i typed the above
[11:47] <ogra_> 39
[11:47] <ogra_> 41
[11:47] <ogra_> 44
[11:48] <ogra_> it only rises while the screen is on
[11:48] <ogra_> seems to stay where it is with the screen off
[11:48] <ogra_> 53M btw
[11:48] <lool> check initctl list as phablet?
[11:49] <ogra_> http://paste.ubuntu.com/6196152/
[11:50] <ogra_> nothing obvious
[11:50] <lool> gtg
[11:50] <lool> unity8 is building in cu2d
[11:50] <lool> didn't pick up bzr the first time, but did the second time
[11:50] <ogra_> ping once you build a new image
[11:52] <lool> ok
[11:54] <popey> ogra_: no, sf
[12:09] <fginther> Saviq, lool, the jenkins IP problem is resolved
[12:15] <ogra_> so after ~30min it starts swapping like crazy
[12:15] <ogra_> http://paste.ubuntu.com/6196223/
[12:15] <ogra_> which is what i saw initially as UI hangs
[12:16]  * ogra_ reboots into SF
[12:51] <ogra_> popey, bug 1235649
[12:52] <popey> how do I enable mir?
[12:52] <ogra_> touch /homa/phablet/.display-mir
[12:52] <ogra_> and reboot
[12:53] <popey> k
[12:53] <popey> apport as soon as I boot
[12:53] <ogra_> *home (indeed)
[12:59] <popey> confirmed
[12:59] <ogra_> thx
[14:53] <lool> fginther: awesome, thanks
[14:54] <lool> == Publishing unity8 ==
[14:56] <lool> in Unapproved
[14:57] <lool> in -proposed
[14:57] <lool> I'll lift the blocks in an hour or so, once it's all built
[15:19] <jdstrand> lool: you mentioned lifting blocks in an hour. is that why I can't upgrade to 82 right now?
[15:46] <lool> jdstrand: nope
[15:47] <lool> jdstrand: what's your issue upgrading?
[15:47] <lool> jdstrand: I'm just about to lift some block hints on 3 packages we want to let out of proposed together
[15:48] <lool> (lifted)
[15:53] <ogra_> lool, did you see the above bug ?
[15:53] <ogra_> pertty much a Mir blocker i think
[16:12] <lool> ogra_: yeah
[16:13] <lool> ogra_: it would also explain why it crashes after a while
[16:13] <ogra_> right
[16:13] <ogra_> the device seems to start swapping once i hit ~250M ... from then on i can only use the UI every few mins
[16:13] <lool> ogra_: I'll raise this to jodh
[16:13] <lool> but I guess only Monday
[16:14] <ogra_> what i find really odd is that this hasnt occured before to me ... and i actually ran Mir for a day or more beofre
[16:14] <lool> it's also weird that upstart would have loads of memory
[16:14] <ogra_> *before
[16:14] <lool> ogra_: did you see anything pile up in initctl list as ~phablet?
[16:14] <lool> like, many apps starting
[16:15] <lool> cause I mean upstart shouldn't have much tracking to do
[16:16] <ogra_> the amount of lines initrctl list returns doesnt change
[16:17] <ogra_> the amount of running apps neither
[16:17] <ogra_> it is somehow related to screen activity ...
[16:31] <lool> ogra_: I was actually thinking, you might be able to strace this upstart from the user session
[16:31] <lool> it's not great to see where memory goes, but you might be able to tell what it's doing
[16:31] <lool> like starting processes, opening fds, writing to files
[17:07] <lool> ok, pkgs are in release pocket now
[17:07] <lool> uh no
[17:09] <lool> looks like if I ever block them once, removing the block isn't enough, I need to unblock them explicitly
[17:13] <lool> ah no, britney stopped running
[18:11] <lool> popey, ogra_: No -proposed migration for now until britney/firewall are unstuck; will ping if there is an update
[18:14] <ogra_> k
[18:24] <popey> lool: ok
[19:36] <lool> ogra_, popey: Unstuck, building an image
[19:37] <popey> great
[20:01] <ogra_> ok
[20:41] <lool> popey, ogra_: Image was up; I can't install Clicks from the store anymore; could you do this with 82?  can't remember whether I tested it
[20:42] <lool> either it was already in #82, or it's an unity8 thing given the list in http://people.canonical.com/~ogra/touch-image-stats/20131005.changes
[20:43] <popey> lool: pretty sure I installed from store
[20:43] <popey> let me try now
[20:43] <lool> with #83, I press Install and nothing happens
[20:43] <popey> lool: yes, i have ureadit on my 82 image, which i installed from the store
[20:43] <lool> cool
[20:44] <popey> want me to try?
[20:44] <lool> popey: sure
[20:44] <popey> ok
[20:44] <popey> just tried again on 82 to make sure it's not a backend issue, and installed something fkine
[20:44] <lool> popey: important thing for me was confirm #82 wasn't broken in this respect
[20:44] <popey> *fine
[20:44]  * popey flashes
[20:45] <lool> if #83 works for you, then perhaps there's something wrong here I need to figure out
[20:45]  * popey flashes
[20:45] <lool> and it's bad for you too, then I guess I can open the unity8 bug early and we know we wont promote it
[20:45] <popey> ya
[20:45] <lool> (I actually upgraded, didn't flash)
[20:46] <lool> [unity-scope-click] - DEBUG: click-scope.vala:253: got details: Akari
[20:46] <lool> [unity-scope-click] - DEBUG: click-scope.vala:255: getting creds
[20:46] <lool> [unity-scope-click] - DEBUG: ubuntuone-credentials.vala:35: Using account id: 1
[20:46] <lool> that's where .cache/unity-scope-click.log stops
[20:46] <lool> it might be a server side issue too
[20:46] <lool> in which case you would see this with #82 too
[20:46] <popey> i happened to install that same app
[20:46] <popey> just now, on 82
[20:46] <lool> they were changing stuff recently to cope with authenticated downloads for free apps failing
[20:46] <lool> popey: and that worked?
[20:46] <popey> yes
[20:46] <lool> cool
[20:47] <popey> and the game runs
[20:47] <lool> :-)
[20:59] <popey> lool: installed fine on 83
[20:59] <lool> popey: apps?
[20:59] <popey> yes
[20:59] <lool> ok, in a way it's good news
[20:59] <popey> hmm
[21:00] <lool> in another, well
[21:00] <popey> well. they installed
[21:00] <lool> I suspect something related to the oauth stuff happening behind the scenes with my U1 account
[21:00] <popey> but i dont see them in the dash
[21:00] <lool> I also played for the first time with the download-manager settings in OS updates
[21:00] <lool> I told it to never automatically download
[21:00] <lool> but it should not affect downloads of click-scope
[21:00] <popey> but if i search, i find it and it runs
[21:00] <lool> popey: oh yeah, that's a known bug, you have to reboot to see them
[21:00] <popey> ah
[21:00] <lool> or search forthem
[21:01] <lool> this has been for weeks
[21:01] <popey> no, just locking is sufficient
[21:01] <popey> just locked / unlocked and both apps show up
[21:01] <lool> ah that's an improvement
[21:12] <lool> filed https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1235784 for the click thing
[21:12] <lool> if it's only me, then it shouldn't get in the way of promotion; it's probably unrelated to the recent upgrades, just a bad oauth state somewhere I'd guess
[21:12] <vila> lool, popey: just discovered the lock/unlock in 82, may have work previously I'm not sure, I can't reproduce reliably it may just be that some process needs time so lock/unlock late enough and it seems to reveal the apps ?
[21:12] <lool> anyway, tests will be running, we can assess promotion on Monday
[21:13] <lool> vila: what do you mean?
[21:13] <lool> vila: there's sometimes a window where the lock screen doesn't appear immediately; is that what you meant?
[21:14] <vila> lool: the lock/unlock trick to reveal click apps already installed
[21:14] <lool> oh ok
[21:14] <vila> lool: I was rebooting before more or less randomly to get them back, found them back after a lock/unlock, came here, saw popey mentioning it. Synchronicity ;)
[21:15] <lool> :-)
[21:15] <lool> Ok, going off, I don't really expect we can do much more this week-end anyway
[21:15] <popey> ok
[21:15] <lool> popey: Thanks a lot for the testing
[21:15] <popey> np
[21:15] <lool> popey: if you're playing with #83 and you find it's good, let me know and we can promote early on Monday with ogra's ack
[21:15] <lool> I'll keep an eye on the tests
[21:15] <popey> will do
[21:16] <lool> they just started