[05:35] <pitti> Good morning
[05:41] <Mirv> pitti: morning. exclusion of .la files from dh_install in indicator-datetime http://pastebin.ubuntu.com/6057779/ (while seemingly keeping .a)
[05:41] <pitti> Mirv: that's adding .a files, not keeping them
[05:42] <pitti> Mirv: and as indicator-datetime doesn't have a -dev package or anything like that, it should be verified that it doesn't build *.a files
[05:42] <pitti> (probably it doesn't and the previous removal was just a copy&paste leftover)
[05:43] <pitti> Mirv: is the result of that in some PPA?
[05:43] <Mirv> pitti: yes, depending on perspective. it was not keeping both, now it's keeping .a, but... it seems the packages don't really have any .a files so it was apparently not needed
[05:43] <pitti> or a test build?
[05:43] <Mirv> pitti: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+sourcepub/3459916/+listing-archive-extra
[05:43] <Mirv> pitti: these have always been successfully built and autopilot tested
[05:43] <Mirv> if they've gotten into phase that packaging changes need acking
[05:44] <pitti> Mirv: checked that the debs don't have .a, so +1 from me
[05:44] <Mirv> pitti: thanks
[05:54] <jibel> Good morning
[07:04] <sil2100> Morning!
[07:05] <Mirv> morning sil2100
[07:05] <jibel> sil2100, Good morning
[07:13] <sil2100> jibel: how was the yesterday run of the stacks? The 18 UTC tick?
[07:14] <jibel> sil2100, daily-release tests are not going well. I investigated SDK tests yesterday evening and AP just wait forever in the middle of the run after a crash during a test. But I haven't found why it is not proceeding with the rest of the testsuite.
[07:15] <sil2100> jibel: ok, so that's reproducible then - so it's like the one time I noticed it
[07:16] <sil2100> jibel: you think it can be directly releated to how the tests are written, or maybe something gets stuck (like dbus) on the test machines?
[07:16] <Mirv> jibel: I filed a bug about the SDK failing tests today, ie. the apps tests, I believe they're related to yesterday's commits but maybe you're talking about something else?
[07:16] <Mirv> or precisely that?
[07:16] <sil2100> Mirv: ^ as you see, yesterday it was a terrible day for testing things...
[07:17] <Mirv> sil2100: well it's been terrible for some time with the unity tests taking eternally (well, 7200 seconds to be exact) because they hung
[07:17] <sil2100> Mirv: not sure if we're talking about the same thing, but yesterday both AP machines were hanging up on the SDK tests, after a failed test they were standing and doing nothing
[07:18] <sil2100> If the same happens for other stacks, I would guess it's the machine's fault
[07:18] <Mirv> sil2100: yeah right so it's different, there's another problem today but it's upstream problem
[07:18] <Mirv> some stacks are going just fine now
[07:19] <Mirv> I released indicators in the morning as well
[07:20] <jibel> there is a file conflict in webapps, but that's a different problem
[07:20] <jibel> /var/log/upstart/otto-setup.log: dpkg: error processing /var/cache/apt/archives/unity-webapps-amazon_2.4.16daily13.06.20-0ubuntu1_all.deb (--unpack):
[07:20] <jibel> /var/log/upstart/otto-setup.log:  trying to overwrite '/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json', which is also in package unity-webapps-common 2.4.16+13.10.20130829.2-0ubuntu2
[07:25] <jibel> sil2100, Mirv SDK is blocked again, same test than yesterday evening
[07:25] <jibel> http://paste.ubuntu.com/6057961/
[07:26] <Mirv> jibel: right, so it's really hanging there. can I stop those jobs so that other stacks can continue?
[07:26] <jibel> pitti, access to ftpmaster is open again, I re-ran update-manager, it picked the right version and it's back to green
[07:27] <pitti> jibel: splendid, that was fast
[07:27] <jibel> Mirv, I'm stopping them, I'd like to archive the run
[07:28] <Mirv> jibel: thanks
[07:29] <sil2100> Damn...
[07:29] <jibel> Mirv, done, unity8 is running now
[07:30] <sil2100> Mirv, jibel: is this happening only for SDK? You think it might be caused by some invalid AP test?
[07:31] <Mirv> sil2100: well it happens in webbrowser app test so it should happen elsewhere.. unless of course the recent UI Toolkit change is what makes it act like so
[07:32] <sil2100> Mirv: I think I saw the Apps stack yesterday go through correctly, only with a normal test failure, so maybe indeed something in SDK? Could you file a bug?
[07:33] <jibel> sil2100, only for SDK apparently, but the same test on the apps stack fails with "error: [Errno 98] Address already in use"  so we cannot say
[07:34] <Mirv> sil2100: I should probably ask if you've checked the stack status page before going to jenkins? ;)
[07:36] <Mirv> sil2100: but we all fail updating the stack status anyway, we should fix that at some point so it's actually up-to-date during each tick
[07:37] <Mirv> I try to but what I for example don't do every time is try to validate the previous claims in there
[07:41] <sil2100> Mirv: I didn't go to jenkins yet, as I don't want to 'interfere' with your tick ;)
[07:41] <sil2100> Mirv: I was just asking about the overall status considering yesterdays apocalypse and overall maddness
[07:41] <sil2100> With people screaming running around
[07:41] <sil2100> ...wait, that was actually just me
[07:44] <Mirv> sil2100: haha :)
[07:44] <Mirv> sil2100: it's "ok" now with these isolated problems, while other stacks are running and publishing... for now
[07:56] <sil2100> Mirv: the problem was that seb wanted the new SDK stack released badly ;)
[07:56] <sil2100> Mirv: while we were unable to do that yesterday evening, and even now as well - but maybe it's a good thing, since if there's something broken then bleh
[07:58] <sil2100> Mirv: I also hope unity can be released finally - yesterday we had one tick where unity passed the check job, but on one machine only
[07:59] <sil2100> I also didn't know if the test run wasn't somehow affected, so I didn't publish - but there are some changes pilled up that would be nice to release
[07:59] <Laney> morning!
[07:59] <pitti> hey Laney, how are you?
[08:00] <pitti> does anyone have a bluetooth keyboard and/or mouse here?
[08:09] <Laney> hey pitti
[08:11] <seb128> good morning desktopers?
[08:11] <seb128> !
[08:12] <jibel> Good morning seb128
[08:12] <seb128> hey jibel Laney, how are you?
[08:13] <jibel> seb128, quite fine and you?
[08:13] <seb128> I'm good thanks
[08:15] <pitti> bonjour seb128
[08:15] <Laney> pretty good
[08:15] <seb128> pitti, salut, ça va bien ?
[08:15] <pitti> seb128: oui, et toi ?
[08:17] <seb128> pitti, très bien merci
[08:21] <Mirv> pitti: I've one BT mouse although I use a logitech usb receiver mouse instead
[08:21] <Mirv> if I click Bluetooth 'on' in saucy g-c-c, it just switches back to off for me, though
[08:22] <pitti> Mirv: ah, thanks; the Logitech ones have their own proprietary protocol, so that doesn't help in that case
[08:25] <mlankhorst> does unity receive updates in the lts point releases?
[08:32] <seb128> sil2100, Mirv: hey, what's the status of the sdk stack?
[08:33] <Mirv> seb128: tests failing when running apps, bug filed https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1220056 (and given to SDK team directly)
[08:33] <ubot2`> Launchpad bug 1220056 in Ubuntu UI Toolkit "Multiple failing apps autopilot tests with the new ubuntu-ui-toolkit build" [Critical,New]
[08:33] <Mirv> seb128: probably related to the optionselector changes yesterday
[08:33] <seb128> Mirv, do you know what change is causing that and is somebody working on that?
[08:33] <jibel> sil2100, unity tests are stuck in a loop http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1508/label=autopilot-intel/console
[08:33] <Mirv> mlankhorst: not specifically for point releases, but generally yes 12.04 had one in the spring
[08:33] <sil2100> jibel: unity as well?!
[08:34] <sil2100> Mirv: ^
[08:34] <jibel> sil2100, yet another issue
[08:34] <Mirv> jibel: sil2100: yes that I think I even e-mailed about as well, bug filed
[08:34] <mlankhorst> Mirv: yeah it's going to need one for saucy
[08:34] <Mirv> that has been since Friday
[08:34] <Mirv> bug #1219636
[08:34] <ubot2`> Launchpad bug 1219636 in Unity "unity autopilot tests fails to move mouse, leading to infinite test run" [Critical,New] https://launchpad.net/bugs/1219636
[08:34] <mlankhorst> Mirv: it needs a backport of pointer barriers, with runtime switching between old api and new saucy api
[08:35] <sil2100> Mirv, jibel: let's stop this run maybe
[08:35] <Mirv> sil2100: I've stopped it for now in the earlier runs
[08:35] <Mirv> so go ahead
[08:35] <Mirv> it does abort after two hours automatically, but it's too long
[08:36] <Mirv> sil2100: that bug is as a blocker on the stack status for unity
[08:37] <jibel> sil2100, I stopped it
[08:37] <sil2100> Mirv: hm, yesterday it didn't happen actually, at least at the afternoon ticks
[08:37] <sil2100> jibel: thanks
[08:37] <seb128> Mirv, do you know what change is causing that and is somebody working on that?
[08:38] <jibel> Mirv, there is no video because recordmydesktop encodes the video when the test finishes, not on the fly
[08:39] <jibel> (was reading your comment on the report)
[08:42] <seb128> sil2100, Mirv: who did you guys ping about the sdk stack issues?
[08:42]  * seb128 trying to get a reply, we need that stack to land
[08:44] <Mirv> sil2100: the commits were yesterday evening
[08:44] <Mirv> seb128: bzoltan directly, he said to be looking
[08:45] <seb128> Mirv, thanks
[08:49] <chrisccoulson> hi seb128!
[08:50] <seb128> chrisccoulson, hey, how are you?
[08:50] <chrisccoulson> seb128, yeah, not too bad thanks. still busy :)
[08:50] <chrisccoulson> how are you?
[08:50] <seb128> chrisccoulson, I'm good thanks, really busy as well
[08:50] <seb128> rrreeeeaallly busy ;-)
[08:51] <chrisccoulson> heh :)
[08:56] <seb128> sil2100, hey, there?
[08:56] <sil2100> seb128: hi, yes
[08:56] <seb128> sil2100, can you help pinging SDK people?
[08:56] <seb128> I'm not having luck getting replies for Mirv
[08:56] <seb128> from
[08:57] <sil2100> seb128: will do! But it seems Zoltan is informed
[08:57] <seb128> sil2100, Zoltan asked if you guys pinged the gallery app people about the gallery tests
[08:57] <seb128> sil2100, right and he said the owner of the apps that have failed tests should be pinged
[08:57] <sil2100> seb128: yes ;) It's all taking place on ubuntu-touch, but heh... it seems we have some more AP issues
[08:58] <sil2100> seb128: and we might need someone from QA on this case as well, as the mediumtests are failing on jenkins while being fine locally (and on the machine)
[08:59] <seb128> QA being jibel?
[08:59] <Mirv> seb128: it seemed like the apps weren't failing tests with the previous version of ui-toolkit, so it did not immediately seem like needed to ping the apps people
[08:59] <seb128> or one of the US guys?
[08:59] <jibel> sil2100, apps stack is affected by a similar issue than SDK but on a different test
[09:00] <seb128> Mirv, zoltan suggests that the default person to ping about app tests failing at app people ;-)
[09:00] <jibel> sil2100, http://paste.ubuntu.com/6058195/
[09:00] <sil2100> jibel: that hang you mean?
[09:00] <jibel> sil2100, yes
[09:01] <Mirv> seb128: yes, that makes sense in general
[09:01] <sil2100> seb128: it's a webbrowser issue, so let me ping oSoMoN maybe as well, but this is getting a bit confusing
[09:01] <seb128> sil2100, Mirv: ok, whatever seems right but please get the sdk stack to land today
[09:02] <sil2100> seb128: roger!
[09:02] <seb128> sil2100, thanks ;-)
[09:02] <Mirv> my biggest confusion is that sdk ran the apps tests successfully early yesterday
[09:02] <Mirv> seb128: sure, one way or another...
[09:02] <jibel> Mirv, could you point to a run that succeeded yesterday?
[09:04] <Mirv> jibel: aha.. green light, but skipped. what on earth has been going on with those tests.
[09:04] <Mirv> the config has been unchanged itself, now it started running those tests and failing
[09:05] <sil2100> I'm... I'm a bit confused right now in overall
[09:11] <Mirv> the pieces start to drop in places I think now
[09:11] <Mirv> just too many pieces and uncontrolled API changes
[09:15] <Mirv> sil2100: what's up with those medium tests, then, any idea?
[09:25] <sil2100> Mirv: I have no idea ;/ Last time it was a dep-problem, but now it's a mystery for me, I'm also unable to get much info from the logs there sadly as it's another, different architecture
[09:25] <Mirv> ok, SDK team seems to be about to revert the change instead, for now... unless they change their mind and all apps get updated instead. let's see.
[09:25] <sil2100> Ok
[09:25] <Mirv> that would be the fastest way anyway, revert
[09:25] <jibel> sil2100, Mirv I'll abort apps tests. No need to wait for the timeout as next tick is in 35 minutes
[09:25] <sil2100> Mirv: wait, to make things clear... will it also fix gallery-app? So that the mediumtests issue won't have to be fixed?
[09:26] <sil2100> jibel: ACK...
[09:26] <Mirv> jibel: ok
[09:26] <sil2100> Damn, so much broken, broken everywhere
[09:26] <sil2100> I see broken stacks
[09:26] <Mirv> sil2100: I don't know, I think gallery-app still needs something since it wasn't broken yesterday but on Friday
[09:27] <sil2100> Right
[09:27] <Mirv> sil2100: we'd have Unity 'green' (yellow) again but it's still with only one autopilot machine. I don't know if we could trust nvidia machine enough?
[09:27] <Mirv> we've been running with only a single machine before, though, but it's unfortunate intel doesn't succeed there
[09:28] <Mirv> the problem is I've no idea how long it'll take for the intel specific problem to get fixed
[09:28] <sil2100> Mirv: I had exactly the same problem yesterday, only nvidia was green IIRC
[09:28] <Mirv> sil2100: yeah, it's because the intel one gets aborted after 2 hours, as discussed earlier
[09:28] <sil2100> Mirv: let's do it like this, let's see if indeed all tests were run, check more or less the failures and publish if it's not terrible
[09:29] <sil2100> I just worry about the hang-up issue
[09:29] <Mirv> sil2100: shall we ignore the fact that webapps is also failing and technically unity depends on it..
[09:29] <sil2100> That we almost always ignore ;p
[09:30] <Mirv> the nvidia is here http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1508/label=qa-nvidia-gtx660/
[09:30] <sil2100> https://bugs.launchpad.net/unity/+bug/1219636 <- I just hope this is not a real regression, but actually there's not much going on on unity!
[09:30] <ubot2`> Launchpad bug 1219636 in Unity "unity autopilot tests fails to move mouse, leading to infinite test run" [Critical,New]
[09:31] <Mirv> sil2100: it does not look worse than on last week when a successful release was made and intel was still running http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1397/label=qa-nvidia-gtx660/#showFailuresLink
[09:31] <sil2100> Indeed
[09:32] <jibel> sil2100, on this case it is possible that the test tries to access a launcher that is not visible and enters the infinite loop tryig to reach it
[09:32] <Mirv> then we'd need three acks http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity_7.1.0+13.10.20130903.1-0ubuntu1.diff + http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scope-mediascanner_0.1+13.10.20130903.1-0ubuntu1.diff (just typo fix) + http://10.97.0.1:8080/view/cu2d/view/He
[09:32]  * sil2100 smiles to seb128 
[09:32] <Mirv> seb128: ^
[09:33] <sil2100> jibel: that would make sense, and I guess it wouldn't mean it's broken for everyday users
[09:34] <jibel> sil2100, correct, if this theory is right, we'll just have to check what the unwanted additional launchers are.
[09:34] <seb128> Mirv, third link got cut by irc line limit
[09:35] <sil2100> seb128: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity_7.1.0+13.10.20130903.1-0ubuntu1.diff
[09:35] <sil2100> seb128: that's the last one ;)
[09:35] <Mirv> seb128: nope the last one was http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-lens-applications_7.1.0+13.10.20130903.1-0ubuntu1.diff
[09:35] <sil2100> Wait, no, scratch that
[09:35] <seb128> right, unity was the first
[09:36] <seb128> sil2100, Mirv: +1
[09:36] <sil2100> Mirv: how dare you paste links in different order than it was on jenkins!
[09:37]  * Mirv published
[09:37] <sil2100> \o/
[09:37] <Mirv> sil2100: :)
[09:37] <sil2100> Finally!
[09:37] <Mirv> SDK probably will get the revert, my main worry is that gallery-app
[09:38] <seb128> what with the gallery-app?
[09:38] <sil2100> Mirv: I think we need someone from the QA team that knows his way around those parts, Francis would be the closest bet
[09:38] <sil2100> But he starts in around 3 hours
[09:38] <Mirv> seb128: this since Friday, and it'd still block SDK https://bugs.launchpad.net/gallery-app/+bug/1218953
[09:38] <ubot2`> Launchpad bug 1218953 in gallery-app "Failing autopilot test: gallery_app.tests.test_photos_view.TestPhotosView.test_select_button_cancel(with mouse)" [Critical,New]
[09:39] <sil2100> Mirv: we can, of course, merge the fix in manually, but I guess it would be best to fix the issue completely
[09:41] <darkxst> hi seb128
[09:42] <seb128> darkxst, hey
[09:42] <seb128> Mirv, that's not in the sdk failing tests today: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1506/label=autopilot-intel/testReport/ ?
[09:42] <seb128> Mirv, oh, I guess it's the app stack?
[09:43] <darkxst> seb128, can you merge 1219188 so it lands after beta freeze finishes?
[09:44] <seb128> darkxst, I can try to have a look, but I've an endless todolist and those diffs don't seem trivial to review ... you maybe have a better chance trying to grab the day patch pilot
[09:44] <darkxst> seb128, ubuntu doesnt use that panel though ;)
[09:44] <seb128> darkxst, that doesn't mean we should upload stuff without review
[09:45] <darkxst> nah didnt mean that, just you dont have to worry about regresssions ;)
[09:45] <darkxst> I will ping patch pilot
[09:45] <seb128> thanks
[09:46] <seb128> darkxst, https://www.google.com/calendar/embed?src=6k1e5rq45m1bdqq0n1ge3oqaok@group.calendar.google.com
[09:46] <Mirv> seb128: apps tests are (for a good reason) ran before sdk is allowed to pass
[09:46] <seb128> Mirv, SHRUG
[09:46] <seb128> Mirv, gallery has like 130 tests failing?
[09:47] <Mirv> seb128: no, those are for the whole stack and more related to this latest SDK change that is now being reverted
[09:47] <seb128> ok
[09:47] <Mirv> seb128: after the revert we should hopefully be again at this one failing test http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1470/
[09:48] <seb128> let's see what's the status once that revert is in
[09:48] <Mirv> and then gallery-app would hopefully get in
[09:48] <Mirv> the fix for that one test
[10:07] <sil2100> Mirv: we should be safe with the SDK stack and the gallery-app test
[10:07] <sil2100> Mirv: as we're not running the failing gallery-app test for the SDK stack, so even if the branch doesn't get merged, it's still ok for SDK to release
[10:24] <seb128> sil2100, Mirv: the ui toolkit revert is in, how do we kick retries?
[10:25] <seb128> sil2100, Mirv: wait
[10:26] <seb128> sil2100, Mirv: they screwed the revert, see -touch
[10:29] <sil2100> huh
[10:42] <Sweetshark> seb128: https://bugs.freedesktop.org/show_bug.cgi?id=68210 and https://bugs.freedesktop.org/show_bug.cgi?id=67602 hit us by not debian as we are using mergedlibs and they are not.
[10:42] <ubot2`> Freedesktop bug 68210 in Writer "Cannot import or read imported tiff images" [Major,New]
[10:43] <ubot2`> Freedesktop bug 67602 in filters and storage "Unable to open .eps files: "Graphics filter not found"" [Critical,New]
[10:44] <seb128> Sweetshark, hey, ok ... can I help there?
[10:44] <Sweetshark> there is likely more trouble hidden there. A quickfix would be to disable mergedlibs as it is obviously currently broken. The downside of that is it would a/ increase package size b/ slowdown startup (esp. on ARM).
[10:45] <Mirv> hmm
[10:48] <seb128> Sweetshark, what is "mergedlibs"?
[10:48] <Sweetshark> seb128: so hmm, I guess we should still do that -- the alternative is to fix that upstream, but I find it hard to judge how much effort it is to fix that properly upstream and if we get that in in time.
[10:48] <seb128> Sweetshark, and why did we enable it and not debian (and when)?
[10:50] <Sweetshark> seb128: mergedlibs puts all the libraries that are used on startup in one big lib instead of a bazillion small ones. Its just one ./configure switch. The advantage is -- as said above: quicker startup because of less dynamic linking work and LTO and a smaller total pkg (also presumably because of LTO).
[10:52] <Sweetshark> OTOH most devs never use mergedlibs as linking half of LO in one lib is severely prolonging your edit-compile-link-test cycles.
[10:53] <Sweetshark> seb128: We had mergedlibs in 4.0 and 3.6 and it worked fine there, but as it looks now I would rather disable that.
[10:53] <Sweetshark> seb128: fwiw SUSE and gentoo also ship with mergedlibs, while redhat and debian do not.
[10:53] <seb128> Sweetshark, did we measure the impact it has on performances when we did it?
[10:53] <seb128> Sweetshark, I guess Suse cares about having it working then?
[10:54] <Sweetshark> seb128: they might just disable it too ...
[10:55] <Sweetshark> seb128: (temporarily, which doesnt help us because we have a hard deadline)
[10:58] <Sweetshark> seb128: when I enabled it I timed it on armhf, but only with the complete distro update: That was LibreOffice 3.5 on precise vs. LibreOffice 3.6 on quantal. IIRC it roughly halfed the first startup from 6sec to 3sec, but that might not have been mergedlibs alone, but pther precise->quantal improvements in addition ...
[11:00] <Sweetshark> seb128: correction -- the change was between LO3.6 on quantal and LO4.0 on raring -- so raring was the first release with mergedlibs
[11:02] <seb128> Sweetshark, seems like an optimization worth having... would it be hard to fix the mergedlibs?
[11:05] <Sweetshark> seb128: so fixing the issues I see right now might be fixable in reasonable time (although its painful to debug and work with such a huge lib) -- just finding out what went wrong was hopefully already half the work. My concern is rather other cornercases that are broken and e.g. not yet reported ...
[11:05] <seb128> Sweetshark, are they broken in raring as well?
[11:06] <Sweetshark> seb128: I guess not. I should have decent visibility of "is broken on Ubuntu, but not on Debian" bugs for Raring -- it has been out long enough.
[11:07] <seb128> ok
[11:07] <seb128> Sweetshark, well, your call, if you think the non mergedlibs codepath is better tested upstream and the way forward let's go for that
[11:08] <seb128> Sweetshark, it could be useful to do an email to ubuntu-desktop or devel list summarizing the situation
[11:12] <Sweetshark> seb128: 'your call', thats mean. Lemme try fixing this in this week, and if it doesnt work out go back to nonmerged as a fallback (that would be changing one character in the rules file after all). In this week I can also watch closely for other suspicous symptoms to crop up.
[11:12] <Sweetshark> does that works out with the release schedule? me checks ...
[11:13] <seb128> Sweetshark, https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[11:14] <Sweetshark> it would mean we have the bug still in beta1 -- but thats what betas are for, right? at least we see if there are other horrorstories from this.
[11:16] <Laney> there is no ubuntu desktop beta 1 :-)
[11:17] <Sweetshark> Laney: you can change the names, but I guess people will stick to the customs for a long time ;)
[11:42] <sil2100> Mirv, jibel: I'll cancel the SDK tests, they're hung again
[11:43] <sil2100> jibel: how can I safely abort this? Can I simply kill the jenkins job?
[11:43] <sil2100> jibel: will that do the trick?
[11:43] <Mirv> sil2100: I just canceled them too
[11:44] <Mirv> sil2100: sorry, I was just about to say "canceled the hung autopilot jobs for you", but then you were here :)
[11:44] <sil2100> Mirv: let's rebuild SDK, since the revert landed
[11:44] <sil2100> ;)
[11:44] <Mirv> sil2100: the red 'x' at http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/ + http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/
[11:44] <Mirv> sil2100: yes, fire it up
[11:45] <sil2100> Mirv: I wanted to make sure that doesn't break anything, since yesterday I was doing aborts and the AP machines were dying
[11:45] <sil2100> Not sure if related, so I asked
[11:45] <Mirv> sil2100: ok. that's the way I've done those without AP machines dying.
[11:47] <jibel> sil2100, you can safely cancel the job but sometimes it doesn't completely stop the container and next jost will fail becuase the container is already up.
[11:48] <Mirv> jibel: yep, that's what I've noticed
[11:49] <jibel> That's because jenkins sends a SIGTERM to the process tree as user jenkins but process is running as root
[11:50] <jibel> I wrote a script to kill any process created from the jenkins script. I should probably deploy it there
[12:19] <sil2100> seb128: I guess the settings stack changes are covered by the touch FFe, right?
[12:19] <sil2100> So I can safely publish that probably?
[12:21] <seb128> sil2100, yes
[12:37] <sil2100> jibel: eh, apps are stuck now...
[12:38] <sil2100> jibel, Mirv: I aborted the apps check, it hung on webbrowser again
[12:38] <seb128> :-(
[12:38] <seb128> sil2100, when did those hangs start?
[12:39] <jibel> sil2100, same pb than previous run
[12:39] <Mirv> sil2100: :(
[12:39] <sil2100> seb128: they didn't happen last week ;/ All started like yesterday
[12:39] <seb128> sil2100, Mirv: hum, sdk still red... is that the same issue?
[12:39] <sil2100> jibel: indeed ;/
[12:39] <seb128> jibel, what's the issue? do we have a clue what is to blame?
[12:40] <sil2100> seb128: eh, it's red because the containers are busy
[12:40] <sil2100> jibel: ^
[12:40] <seb128> busy?
[12:40] <seb128> shouldn't that make them wait?
[12:40] <sil2100> jibel: SDK check can't run because of the containers - the thing you said earlier
[12:41] <sil2100> seb128: it's a problem that sometimes happens when we abort the AP test machines, the containers don't stop completely and are unavailable
[12:41] <sil2100> jibel has some fix for that but it wasn't deployed yet
[12:41] <seb128> hum, k
[12:41] <sil2100> jibel: ^
[12:41] <seb128> this week is quite a fail one so far
[12:41] <sil2100> seb128: it seems all has really REALLY bad luck now
[12:41] <jibel> seb128, it started somewhere between Sep 2, 2013 1:01:30 PM and Sep 2, 2013 10:14:51 PM
[12:42] <seb128> jibel, do you think it's likely a distro change? we are in beta1 freeze, we didn't get that many stuff landing...
[12:44] <sil2100> jibel: can you unblock the containers? What should I do in such a case when you're not around? Should I simply stop the containers or something more?
[12:45] <jibel> seb128, yeah, I've no idea what is causing this hang yet. There is no evidence on the test machine, autopilot is running, and found nothing special in the logs
[12:45] <seb128> jibel, :-(
[12:45] <jibel> seb128, strace shows that AP is looping on a select, which actually means nothing
[12:45] <sil2100> jibel: maybe we should have the autopilot development guys check it out?
[12:46] <jibel> sil2100, yup
[12:48] <jibel> sil2100, the containers are unblocked, you can also run: sudo lxc-stop -n $(lxc-ls|tail -1)  directly on the machines, that will stop the run and create all the artifacts
[12:48] <sil2100> jibel: thanks! Ok, so just stopping is enough, yay
[12:48] <sil2100> Re running SDK
[12:56] <Sweetshark> seb128: you got mail
[12:57] <jibel> seb128, sil2100 http://paste.ubuntu.com/6058785/ this is the list of packages that differ between the last successful run of apps and the first run that completely failed
[12:57] <seb128> Sweetshark, k
[12:58] <seb128> jibel, so could be an ui toolkit issue...
[12:58] <Mirv> sil2100: https://code.launchpad.net/~schwann/gallery-app/gallery-atest-toolbar-opened/+merge/183195 got approve from jenkins!
[12:59] <Mirv> top-approving it so it can land
[13:00] <seb128> sil2100, Mirv: sdk still red :/
[13:01] <Mirv> seb128: it's actually success, but with a warning about removed tests
[13:01] <seb128> Mirv, yeah, I was wondering since intel/nvidia are green
[13:01] <Mirv> seb128: so sil2100 can probably just publish it after double checking that it's correct that some tests were now disabled
[13:01] <seb128> \o/
[13:06] <sil2100> ;/
[13:06] <sil2100> \;
[13:06] <sil2100> Checking
[13:13] <sil2100> Ok, I can't find anything strange
[13:14] <sil2100> It's all a bit suspicious, but I think it's not suspicious enough not to release those stacks
[13:16] <seb128> sil2100, do it! ;-)
[13:16] <seb128> sil2100, if there are issues we can blame it on jibel and the unstable QA config ;-)
[13:16]  * seb128 hides from jibel
[13:17] <sil2100> ;D
[13:17] <sil2100> Ok, working on getting everything out
[13:17] <seb128> \o/
[13:18] <jibel> seb128, you'd rather blame the app team that removes tests to make them pass ;)
[13:18] <seb128> speaking of removing test
[13:19] <seb128> jibel, chrisccoulson: the firefox tests seems like they never managed to go green, we keep overruling them, should we just drop them?
[13:19] <jibel> seb128, IIRC gnome-session failed to start so tests do not even run, but someone more knowledgeable than me must have a look
[13:19] <sil2100> Published, yay
[13:20] <seb128> sil2100, \o/
[13:21] <jibel> seb128, there has been a lot of work to have them green in raring, it'd be a pity to remove them
[13:21] <seb128> jibel, well, reality is that they seem to be always red and creating issues, so they are creating work rather than being useful ... though I agree than having them working would be nice
[13:21] <seb128> chrisccoulson, ^
[13:22] <jibel> seb128, I can setup a testing environment and give access to any resource we have to help fixing them
[13:22] <chrisccoulson> seb128, unfortunately, the tests leave no clue in the logs of why gnome-session doesn't start, and i can't reproduce it here
[13:23] <Laney> stgraber managed to reproduce it while we were at debconf
[13:23] <Laney> I think we were using the prepare-testbed stuff
[13:24] <stgraber> yeah, was easily reproducable when using the kvm based autopkgtest stuff as described on developer.u.c
[13:24] <stgraber> was also reproducable on a standard saucy machine as long as it's not using an nvidia driver
[13:40] <sil2100> fginther: hello!
[13:41] <sil2100> fginther: about the removal of those hooks... I have also been wondering about removing the phablet ppa and the sdk ppa - but I wanted to consult it with you first
[13:42] <sil2100> fginther: since I guess even if this might provide some override behavior, I guess we don't want to be testing/building things when using non-daily-build/non-distro versions
[13:42] <sil2100> fginther: so, you think we can remove those two as well?
[13:46] <fginther> sil2100, are you just referring to removal of the hooks, or the ppas as well?
[13:48] <sil2100> fginther: for now maybe just the hooks, since PPAs can still be used for local testing
[13:49] <sil2100> But I guess for mediumtests and daily-release, those PPAs might only cause trouble
[13:49] <sil2100> As we might be testing and building against something that's not going to be released
[13:49] <fginther> sil2100, yes, I think that's reasonable
[13:50] <sil2100> fginther: ok, I'll prepare a branch for your review in a moment
[13:50] <fginther> sil2100, cool, thanks
[13:50] <sil2100> fginther: btw.... ;) Are you busy busy?
[13:50] <fginther> sil2100, I'm less busy this week
[13:50] <fginther> sil2100, do you have a major project for me :-)
[13:51] <sil2100> fginther: since we have that branch in gallery-app that just fails building, it's failing on mediumtests - the author says he cannot reproduce it on the machines (phones) and locally
[13:51] <sil2100> fginther: sadly, no major project ;p Just the standard hacking
[13:51] <sil2100> fginther: https://code.launchpad.net/~schwann/gallery-app/gallery-atest-toolbar-opened/+merge/183195
[13:51] <sil2100> fginther: at first it was a dep problem, we fixed it, but then it's hm, strange
[13:52] <sil2100> fginther: we don't know how the mediumtests are working and where to get specific info, but for instance CI approved it and then it failed to merge
[13:52] <sil2100> I re-approved, but I guess it won't help much
[13:52] <fginther> hmm
[13:52] <sil2100> There's not much change in the code, so this is a good question mark
[13:53] <fginther> om26er, can you help take a look at this gallery-app test? ^^
[13:53] <sil2100> fginther: let's move to -touch, and poke gusch and om26er there
[13:53] <fginther> ack
[13:53] <om26er> fginther, sil2100 sure
[13:53] <sil2100> Thanks guys
[13:54] <asac> fginther: hey :)
[13:54] <fginther> asac, morning
[13:54] <asac> hi ... -> touch :)
[14:27] <cyphermox> sil2100: did cordova get sorted out after all?
[14:33] <sil2100> cyphermox: the issue that Robert pointed out in the e-mail seems fixed, but it's not out yet because of webapps problems
[14:36] <sil2100> cyphermox: let me find the bug
[14:36] <cyphermox> ack
[14:42] <sil2100> cyphermox: actually, the bug was not really accurate, so I made a new one, since I guess the previous issue got fixed: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1220277
[14:42] <ubot2`> Launchpad bug 1220277 in webapps-applications (Ubuntu) "unity-webapps-amazon overwriting file from unity-webapps-common" [Undecided,New]
[14:55] <Laney> grr
[14:56] <Laney> come on SetTime, you know you want to work
[14:59] <czajkowski> Laney: no it doesn't really it wants to drive you around the bend!
[15:04] <sil2100> fginther: what do you think? https://code.launchpad.net/~sil2100/cupstream2distro-config/hook_cleanups/+merge/183686
[15:10] <Laney> czajkowski: Might have been me that was defective. :P
[15:10]  * Laney tests
[15:11] <Laney> Yes, indeed it was. ¬_¬
[15:12] <Laney> One part gave milliseconds while the other wanted microseconds
[15:12] <Laney> Turns out they don't like it very much when you mix those up
[15:19] <fginther> sil2100, I'll review in a moment
[15:29] <seb128> hey everyone, it's meeting time
[15:30] <seb128> qengho, mlankhorst, Sweetshark, Laney, tkamppeter, larsu: hey, it's meeting time
[15:31] <larsu> seb128: as usual, I'm still in the indicator call :) I have my notes ready though!
[15:31] <seb128> I hope everyone is fine!
[15:31] <seb128> larsu, no problem, there is time before your turn
[15:31] <qengho> Yo.
[15:31] <seb128> qengho, hey
[15:31] <qengho> * Trying to tighten the loop of chromium releases.
[15:31] <qengho>   - I'm taking over the webapps patches. Previous maintainer is too busy.
[15:31] <qengho>   - I am trying to automate the webapps testing. This is still a mystery to me.
[15:31] <qengho>   - On new release, I'm finishing any release I start, instead of restarting if a new upstream release appears.  Today's or tomorow's release will be 29.0.1547.62 (28 Sept) instead of 29.0.1547.65 (yesterday).
[15:31] <qengho> * Trying to make chromium the best choice for security-conscious users.
[15:31] <qengho>   - Applied contributed DuckDuckGo patch.
[15:31] <qengho>   - Thinking about warning of weak levels of security. Perfect Forward Secrecy and poor SSL should be different to the user.
[15:31] <qengho>   - Improving apparmor profile. I hope to flip policy from "complain" to "enforce".
[15:32] <qengho>   - Firefox dropped Third-party-cookies Off, but still on in Cr for Saucy. Not sure about it yet.
[15:32] <seb128> qengho, thanks
[15:33] <seb128> qengho, what's the status of the saucy build?
[15:33] <seb128> qengho, it's failing to build for 3 weeks now
[15:33] <qengho> seb128: This new release fixes it.
[15:33] <seb128> qengho, we should aim at fixing build issues without locking that with updates that "are coming soon" and takes weeks to come...
[15:33] <seb128> qengho, you say that for 2 weeks...
[15:34] <qengho> seb128: I agree. This is the last time you'll hear it.
[15:34] <seb128> qengho, thanks
[15:35] <seb128> mlankhorst, hey
[15:36] <seb128> no mlankhorst?
[15:36] <seb128> Sweetshark, hey
[15:39] <seb128> hum
[15:39] <seb128> yet another of those weeks...
[15:39] <seb128> Sweetshark, mlankhorst: please try to be around for the meetings
[15:39] <seb128> Laney, hey
[15:40]  * Laney stays quiet :P
[15:40] <Laney> • vUDS
[15:40] <Laney> • GStreamer touch packaging work and fixes; discussions with internal upstreams
[15:40] <Laney> • Package + upload GStreamer 1.1.3 to Saucy before FF
[15:40] <Laney> • Now need to file FFe for 1.1.4 and upload that
[15:40] <Laney> • system-settings
[15:40] <Laney> ∘ Get time-date using NTP
[15:40] <Laney> ∘ Get time-date manual setting working (MP coming up in a minute) with custom date/time picker to unblock and possibly finish this panel(?)
[15:40] <Laney> ∘ UI for selecting security-privacy unlock method
[15:40] <Laney> ∘ Unify the sleep timeout panel with battery
[15:40] <Laney> ∘ Add accountsservice custom properties for deciding whether to display messages or statistics on the welcome screen
[15:40] <Laney> • Release engineering for Beta 1, out tomorrow.
[15:40] <Laney> • FF happened: reviewed some exceptions.
[15:40] <Laney> FIN
[15:41] <seb128> Laney, thanks
[15:41] <Laney> np!
[15:41] <seb128> Laney, your review is next on my todo
[15:41] <Laney> yeah I'll do some of yours this afternoon
[15:41] <Laney> wish we had more people doing them
[15:41] <seb128> Laney, it would be nice if you could ack https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1219777
[15:41] <ubot2`> Launchpad bug 1219777 in shotwell (Ubuntu) "[FFe] update to 0.15" [Wishlist,In progress]
[15:42] <seb128> Laney, with the track history of the yorba guys I don't think it needs lot of thinking, but I'm happy to provide details if you need them
[15:42] <seb128> Laney, thanks
[15:42] <seb128> @re: review, acks
[15:42] <meetingology> seb128: Error: "re:" is not a valid command.
[15:42] <seb128> I hope kenvandine can help again once he's over the content-hub rus
[15:42] <seb128> h
[15:42] <seb128> didrocks as well once he's back
[15:43] <seb128> Laney, thanks
[15:43] <seb128> tkamppeter, hey
[15:43] <tkamppeter>  - pyppd: Fixed bugs leading to bogus index entries (letting many printer
[15:43] <tkamppeter>    models/PPDs appearing duplicate) in PPD archives. Reduces output of
[15:43] <tkamppeter>    "lpinfo -m" from ~14000 lines to ~10000 lines.
[15:43] <tkamppeter>  - Ghostscript 9.10
[15:43] <tkamppeter>  -  Release of cups-filters 1.0.37 and 1.0.38
[15:43] <tkamppeter>  - Bugs
[15:43] <tkamppeter>  - GSoC
[15:45] <seb128> tkamppeter, thanks
[15:45] <seb128> larsu, hey, done with the indicators meeting?
[15:46] <larsu> seb128: yes :)
[15:46] <larsu> - fixed a couple of minor bugs in the messaging menu, involving indicator-messages, unity8, and qmenumodel
[15:46] <larsu> - helped to port the messaging menu in unity8 to unitymenumodel (i.e., fixing bugs and adding features to unitymenumodel)
[15:46] <larsu> - gsettings-qt: keys can now be reset (settings.schema.reset()) and it is printing a warning if a key cannot be written
[15:46] <larsu> - getting pinged about unity8 icons more and more, so I added ubuntu-mobile as the default icon theme and I'm working on getting all the warnings about icons down

[15:47] <seb128> larsu, danke
[15:47] <larsu> :)
[15:48] <seb128> ok, my turn
[15:48] <seb128> = System settings:
[15:48] <seb128> * battery:
[15:48] <seb128> - fixed a segfault bug
[15:48] <seb128> - reported some upower upstream wishlist/bugs
[15:49] <seb128> * storage: some leak fixes, added initial support for click
[15:49] <seb128> * reset: initial backend, reset unity launcher key and initial support for accountsservice reset
[15:49] <seb128> * use better icon
[15:49] <seb128> * reviews for others
[15:49] <seb128> * tested the content picked work
[15:49] <seb128> = some updates bug/fixes before FF
[15:49] <seb128> = some sponsoring for UbuntuKylin
[15:49] <seb128> = looked at getting gnome-control-center and webkit out of the touch image (still some work to do there for webkitgtk)
[15:49] <seb128> = lot of discussions around missing backends, system settings blocker
[15:49] <seb128> on my next items list:
[15:49] <seb128> - get the click support in system-settings done
[15:49] <seb128> - shotwell update (I'm testing it atm)
[15:50] <seb128> - upload old nautilus as nautilus34 (I'm pondering making it default for Ubuntu)
[15:50] <seb128> Laney, ^ do I need a FF to upload that as a new source?
[15:50] <seb128> (of course we need one if we consider using it in Ubuntu as default)
[15:51] <jbicha> seb128: have you tried nemo which is already in Ubuntu?
[15:51] <Laney> Yeah, I think we ask for those
[15:51] <Laney> I think that would be a large decision though
[15:51] <Laney> should have had a vUDS session
[15:51] <seb128> jbicha, no, but I'm not really interested in taking on a new codebase
[15:52] <seb128> we know old nautilus and have it in a LTS
[15:52] <seb128> taking a new fork would require reviewing the diff and stabilizing things
[15:52] <jbicha> well nemo is a fork of nautilus 3.4
[15:52] <seb128> right, "fork", dunno how much they change
[15:52] <seb128> and they track record in writing solid code
[15:52] <seb128> their
[15:53] <seb128> I'm going to give a try to it, but nautilus3.4 seems a safer bit
[15:53] <mlankhorst> seb128: pong, looking at lts-saucy -> precise backports, more kernel stuff, mesa 9.2 in archive :D
[15:53] <seb128> Laney, I though we stopped doing "default applications" UDS sessions after the rhythmbox/banshee fiascos ;-)
[15:55] <Laney> This is a bit different to that
[15:55] <Laney> It's going to an old version of some software we already have
[15:55] <Laney> We'd need to think about how that is going to be maintained
[15:56] <seb128> Laney, I don't feel like it's a topic we can have a productive live discussion on...
[15:56] <Sweetshark> oh are we discussing kicking LO from the default again?
[15:56] <Laney> what the future looks like etc
[15:56] <Laney> also we have to remove LO, indeed, thanks for bring that up Sweetshark
[15:56] <seb128> ;-)
[15:56] <Laney> :P
[15:56] <seb128> Laney, well, I'm going to try nemo and get old nautilus in the archive if nemo has issues
[15:56] <mlankhorst> yeah def not default application, kick to universe
[15:57] <seb128> I've enough of our users complaining about how much new nautilus sucks
[15:57] <seb128> and about how much we are idiots for doing that update
[15:57] <jbicha> seb128: you can't do like the GNOME developers and ignore them? ;)
[15:58] <seb128> jbicha, yeah, I could, but I'm especially trying to avoid that :p
[15:58] <Sweetshark> seb128: is the meeting already over, or shall I dump my blurb in still?
[15:58] <seb128> Sweetshark, please dump your blurb (and be in time next week ;-)
[15:58] <Sweetshark> - LibreOffice on Ubuntu is hit by a (or more) 4.0->4.1 regression: https://bugs.freedesktop.org/show_bug.cgi?id=68210 https://bugs.freedesktop.org/show_bug.cgi?id=67602
[15:58] <Sweetshark> - doesnt hit Debian, Fedora because they dont use mergedlibs (but hits e.g. SUSE, gentoo)
[15:58] <ubot2`> Freedesktop bug 68210 in Writer "Cannot import or read imported tiff images" [Major,New]
[15:58] <Sweetshark> - quickfix would be disabling mergedlibs, but that would: - grow the package size - slowdown first start (assumed to be twice as slow on ARM then)
[15:58] <ubot2`> Freedesktop bug 67602 in filters and storage "Unable to open .eps files: "Graphics filter not found"" [Critical,New]
[15:58] <Sweetshark> - so: trying to fix the root cause.
[15:58] <Sweetshark> - in other news: the SUSE LibreOffice team moves to Collabora https://people.gnome.org/~michael/blog/2013-09-03-collabora.html - quite a bit of smoothing the waves needed for that upstream, now back to business as ususal
[15:58] <Sweetshark> EOF
[15:58] <Sweetshark> seb128: ay
[15:59] <seb128> Sweetshark, thanks
[15:59] <jbicha> nautilus is tricky because there are quite a few improvements in 3.6/3.8
[15:59]  * Sweetshark is off for TDF advisory board call ...
[15:59] <jbicha> some people would be really disappointed to go back to nautilus34...although if it's easy to install it might be ok
[15:59] <seb128> jbicha, well, most users hate the keyboard navigation and there is a lot of useful dropped as well (split view for example)
[16:00] <seb128> jbicha, feedback we get through bug reports is that most users don't see real improvements in the new version
[16:00] <seb128> jbicha, it has some nice UI tweaks, that we can do on the old codebase
[16:00] <jbicha> I wouldn't say "most users", some users don't like some features being dropped
[16:00] <seb128> well, features dropped is fine, sometimes
[16:00] <Laney> If we listened to 'most users' we wouldn't have switched to Unity
[16:01] <seb128> but new nautilus is just not working if you are a keyboard user for example
[16:01] <jbicha> I believe there are as many new features as dropped features so some users wouldn't like to see the new features reverted
[16:01] <seb128> well, for one I hate the new nautilus and can't use it
[16:01] <Laney> Non-geeks I know IRL haven't said anything to me about it
[16:01] <seb128> keyboard navigation is just buggy
[16:01] <jbicha> nautilus works fine for this keyboard user
[16:01] <seb128> no it doesn't
[16:02] <seb128> jbicha, Laney: read bug #1164016 if you are interested in some constructive user comments
[16:02] <ubot2`> Launchpad bug 1164016 in nautilus (Ubuntu) "restore type-ahead find" [Medium,Triaged] https://launchpad.net/bugs/1164016
[16:02] <seb128> Laney, well, our design team says user feedback says the new menus are a disaster at least
[16:02] <seb128> that's why they made us start reverting those changes in other apps
[16:03] <seb128> anyway, I'm going to take that as a list discussion
[16:03] <jbicha> I think the new search is an improvement but I agree that nautilus's menu reorganization is confusing (although usually the GNOME3 style menus are an improvement)
[16:04] <seb128> jbicha, I had a few case of users that though new evince didn't have menus anymore this cycle
[16:04] <Laney> I think the cog menus are weird in Unity, granted, but I thought we were/would work towards a general solution for those
[16:04] <seb128> (the default geometry puts the cog menu out of the toolbar in a dropdown hidden menu)
[16:04] <seb128> Laney, well, the issue is that we don't have the resources atm to fix nautilus
[16:05] <seb128> Laney, so it's either we keep what we have or we keep what we have in the lts and is known to not have those issues
[16:05] <seb128> Laney, I expect that after that LTS we are likely to take on a new qml/converged file manager anyway
[16:05] <seb128> it wouldn't be the end of the world to have another LTS on 3.4, precise's users seem happy enough
[16:06] <seb128> let's have that discussion on the list, I'm going to try nemo and come with an argumented email to discuss it (and get design to wave in if they can)
[16:06] <seb128> thanks everyone
[16:07] <Laney> ok, thanks
[16:07] <seb128> sil2100, hey, sorry for overruning the first half of the meeting, your turn!
[16:07]  * kenvandine waves
[16:07] <sil2100> Ok, thanks!
[16:07] <sil2100> Hello everyone!
[16:07] <sil2100> kenvandine, cyphermox, Mirv!
[16:07] <sil2100> I don't see robru around...
[16:08] <sil2100> kenvandine, cyphermox, Mirv: all of you present ;) ?
[16:08]  * kenvandine is hear
[16:08] <kenvandine> here even
[16:09] <sil2100> How about Mirv and cyphermox?
[16:09] <sil2100> I guess they might have missed the meeting reminder or are super busy, so maybe let's start without them - kenvandine!
[16:10] <sil2100> kenvandine: could you update us on things you were doing last week and this week?
[16:10] <sil2100> :)
[16:11] <kenvandine> content-hub...
[16:11] <kenvandine> i did unclog the signon* stuff
[16:11] <kenvandine> to release
[16:11] <sil2100> So, mostly content-hub things?
[16:11] <kenvandine> but otherwise just content-hub
[16:11] <sil2100> Well, most of the crucial things landed before the deadline, so I guess it's all cool - thanks kenvandine!
[16:12] <sil2100> Mirv, cyphermox: still not around?
[16:12] <sil2100> So, maybe some update from my side in the meantime:
[16:12] <cyphermox> what?
[16:12] <sil2100> cyphermox: meeting! Weekly meeting time!
[16:12] <cyphermox> I'm around
[16:13] <sil2100> cyphermox: good to know (now) ;) Could you update us on your doings for the last 2 weeks? (as we skipped last weeks meeting)
[16:14] <sil2100> Just a brief update is enough
[16:15] <sil2100> cyphermox: ?
[16:16] <sil2100> Ok, I guess we'll get back to cyphermox later
[16:16] <sil2100> As for me - last week, besides UDS related responsibilities, discussions and hosting, we landed almost everything that had to be in before FF
[16:17] <sil2100> Also, Mir with the two key features were released without any problems before feature freeze, so we now just work on tweaking everything so that it's ready for 'default' in 13.1
[16:17] <sil2100> 13.10
[16:18] <sil2100> We're after FF now, so please proceed carefully with publishing stuff, we still need to decide on which stacks to put into forced manual publishing
[16:18] <sil2100> This week we're having some problems with the AP testing for daily-release, but I guess we'll have that resolved soon
[16:18] <Laney> are you switching to bugfix 13.10 branches?
[16:19] <sil2100> Laney: we won't be switching branches yet, we might discuss that next week, but for now we only plan on forcing manual publishing on certain stacks
[16:19] <sil2100> Which have more components that are not under the touch FFe
[16:20] <sil2100> I'll be also prioritizing the Qt appmenu work this week as well, so that we can get Qt 5.1. moving
[16:20] <sil2100> kenvandine, cyphermox, Mirv: ok, let's just run through the spreadsheet quickly
[16:20] <sil2100> kenvandine: WebCred: Fix autopilot tests keyring issue - is that done now?
[16:21] <sil2100> Since I see it's been around for quite a while, you remember what's the status?
[16:21] <kenvandine> sil2100, no... i was never able to get back to that
[16:21] <sil2100> Ok
[16:21] <kenvandine> was waiting for otto
[16:21] <kenvandine> but then i was on other things
[16:21] <sil2100> Let's get back to that once things are less crazy
[16:22] <sil2100> The next two we skip, as there is no one to comment
[16:22] <sil2100> The XIM SRU issue is still not ready, infinity asked to take care of that once he has a free cycle
[16:23] <sil2100> But the SRU team is aware, it's rather high priority since some people need this fix in
[16:23] <sil2100> libcolumbus should be unblocked, hm, will check that later
[16:24] <sil2100> lp:unity-voice - I had a chat with pete-woods and he said that it's all fixed
[16:24] <sil2100> So I'll check that too
[16:24] <sil2100> mediascanner into main - we don't prioritize that anymore, so I guess we might remove that task
[16:25] <sil2100> Ok, I think it doesn't make sense to browse all of them when not having people around ;)
[16:25] <sil2100> Let's wrap this up then
[16:25] <sil2100> kenvandine: thanks for attending ;) o/
[16:26] <kenvandine> :)
[16:26] <sil2100> I'll send an update to Didier in a moment and then archive the tasks
[16:26] <kenvandine> quiet week i guess
[16:28] <seb128> kenvandine, if the week is quiet, please trying help on system settings review, we are struggling with those with only Laney and me helping there
[16:28] <sil2100> seb128: what help do you need?
[16:28] <kenvandine> i'll try... i mostly meant not many people around for the meeting
[16:28] <seb128> sil2100, upstream code reviews on merge requests
[16:28] <sil2100> I might find some free cycles, but I'm not sure if a non-core-dev can help much
[16:28] <seb128> kenvandine, oh ok, that sort of "quiet" ;-)
[16:28] <kenvandine> seb128, i'm now on to the sept milestone for content-hub
[16:28] <kenvandine> :)
[16:29] <kenvandine> we achieved the august goal :-p
[16:29] <seb128> kenvandine, we can't stop settings work though :/
[16:29] <seb128> kenvandine, did you guy app activation working?
[16:29] <sil2100> seb128: then is it possible for me to help?
[16:29] <seb128> sil2100, how much do you know qt/qml, do you feel like doing settings work and code reviews? (e.g do you want to be involved in coding on those)
[16:30] <seb128> sil2100, if you say know it's fine, I think you already have enough to do dealing with stack and packaging
[16:31] <sil2100> seb128: I have quite some Qt experience from the past, although not much QML - for sure enough to do code reviews
[16:31] <sil2100> seb128: I would gladly help code-wise, but I think I need to first keep my promise and finish appmenu QPA code-wise
[16:32] <seb128> sil2100, right, we are not blocked on anything, it would just be good to increase our poll of reviewers in the project
[16:32] <seb128> sil2100, so if you feel like joining later/reviewing that would be good
[16:34] <seb128> Laney, can I nitpick on your security panel branch? ;-)
[16:34] <Laney> do it
[16:35] <Laney> I'd do the same :P
[16:35] <seb128> hehe
[16:35] <seb128> "description>If swipe, unlock by swiping the screen (no security). If passcode, use a 4-digit number to unlock. If password," ...
[16:35] <seb128> Laney, can you put the options in ""
[16:35] <Laney> haha
[16:35] <seb128> or ''
[16:36] <Laney> I thought that while I was pushing it
[16:36] <seb128> ;-)
[16:36] <kenvandine> seb128, we have it partially working in a branch
[16:36] <Laney> then I was like "oh whatever, I've already typed bzr push, he won't notice/care" ;-)
[16:37] <Laney> pushed
[16:37] <seb128> Laney, lol, thanks ;-)
[16:41] <seb128> Laney,                 return i18n.tr("Switch to Swipe")
[16:42] <seb128> Laney, do we uppercase because it's an option name? I'm still unsure that's right
[16:42] <Laney> I asked mpt about that earlier and he said it was right
[16:43] <seb128> Laney, mpt: what's the rational?
[16:43] <seb128> we probably got it wrong in other places...
[16:45] <mpt> Laney, oh, sorry, I thought you were referring to a different string before. I guess dialog titles should be consistent with sheet titles. I don't know why sheet titles use sentence case on the phone. I shall find out.
[16:46] <seb128> Laney, do you also get those "<Unknown File>:" printed on stderr
[16:47] <Laney> yes
[16:47] <Laney> I have no idea what that is
[16:47] <fginther> sil2100,  FYI, a fix is needed for https://code.launchpad.net/~sil2100/cupstream2distro-config/hook_cleanups/+merge/183686
[16:53] <sil2100> fginther: thanks for the review!
[16:55] <sil2100> fginther: updated and pushed, could you take a look?
[16:55] <sil2100> Laney: ping
[16:57] <sil2100> Laney: I checked the update_excuses and saw that there's a "Not touching package due to block request by laney" for unity-lens-applications, why is that?
[16:58] <sil2100> Laney: we need the new version to release the new libcolumbus, which is blocked on the new unity-lens-applications
[16:58] <Laney> sil2100: beta 1 freeze
[16:58] <sil2100> Ah, hm, ok
[16:58] <sil2100> Right
[16:59] <Laney> sil2100: Will be removing it tomorrow once it's clear all the images are final
[16:59] <Laney> but I can look at letting your update through early if you need it
[17:00] <sil2100> Laney: no need, it's not urgent, has just some smaller bugfixes in it - I just had it in my TODO since last week and been wondering what was going on
[17:00] <sil2100> Since I got it in for the first time on the 28th
[17:00] <sil2100> And it didn't unblock anything ;p
[17:00] <sil2100> Been wondering why
[17:01] <Laney> 28 is in
[17:01] <Laney> 28.1
[17:01] <Laney> but I guess you are after the configure.ac changes
[17:01] <Laney> why can't you do transitions in -proposed?
[17:01] <sil2100> Ah, right, see 28.1 in, there was another one in the meantime - yes, the other one I want
[17:02] <sil2100> Laney: what do you mean by 'transitions'?
[17:02] <Laney> nm, I just looked and it's not what I thought
[17:20] <seb128> Laney, sil2100, Mirv: oh btw, I'm taking a day off tomorrow, forgot to mention it
[17:20] <seb128> I might be around a bit in the morning/end of afternoon
[17:20] <seb128> but basically I need to take holidays, I almost didn't take any this year, and weather is going to be nice
[17:21] <seb128> so mostly going to take a day to hang around and do some errands
[17:25] <tjaalton> how to figure out why gnome-screensaver doesn't kick in?
[17:25] <sil2100> seb128: oh noes!
[17:26] <sil2100> seb128: WE'RE DOOMED
[17:26] <sil2100> seb128: ;)
[17:26] <seb128> lol
[17:26] <seb128> tjaalton, on idle or...?
[17:26] <sil2100> seb128: but seriously, ok, thanks for giving the info! Have a nice day, don't work ;)
[17:26] <tjaalton> seb128: right
[17:26] <seb128> sil2100, thanks!
[17:26] <seb128> tjaalton, is the daemon running?
[17:27] <tjaalton> seb128: yes, running in on debug mode doesn't show anything happening after timeout
[17:27] <tjaalton> *it on
[17:27] <tjaalton> no video player running
[17:27] <tjaalton> just rb playing a radio stream
[17:28] <seb128> tjaalton,
[17:28] <seb128> $ gdbus call --system -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.ListInhibitors
[17:29] <seb128> tjaalton, gsettings get org.gnome.desktop.lockdown disable-lock-screen
[17:29] <tjaalton> "false"
[17:29] <seb128> tjaalton, gsettings get org.gnome.desktop.screensaver lock-delay
[17:29] <tjaalton> uint32 0
[17:29] <seb128> tjaalton, gsettings get org.gnome.desktop.screensaver lock-enabled
[17:29] <seb128> tjaalton, oh
[17:30] <tjaalton> "false"
[17:30] <seb128> tjaalton, that's why
[17:30] <tjaalton> i don't use lock
[17:30] <seb128> you have locking disabled...
[17:30] <seb128> oh
[17:30] <tjaalton> it should still blank the monitor
[17:30] <seb128> what do you call "screensaver" then?
[17:30] <tjaalton> the feature where it turns the screen off when I'm not around
[17:30] <tjaalton> to save power
[17:31] <tjaalton> ([('sleep', 'root', 'inhibited', 'delay', uint32 0, uint32 1625), ('handle-lid-switch', 'tjaalton', 'Lid is handled by gnome-settings-daemon power', 'block', 1000, 3108), ('handle-lid-switch', 'aino', 'Lid is handled by gnome-settings-daemon power', 'block', 1001, 10002)],)
[17:31] <tjaalton> two users logged in
[17:32] <seb128> tjaalton, could be one of the settings in org.gnome.settings-daemon.plugins.power
[17:32] <seb128> org.gnome.settings-daemon.plugins.power idle-dim-ac
[17:32] <seb128> org.gnome.settings-daemon.plugins.power idle-dim-battery
[17:34] <Mirv> sil2100: sorry! I usually have my alarm clock set on Tuesdays but it was not today
[17:35] <sil2100> Mirv: no worries! Shouldn't you be sleeping already ;p?
[17:35] <Mirv> sil2100: so, with FF pressures done, mostly Qt 5.1.1 now. some pending stuff elsewhere and I'm still not sure about the tests enabling part, but otherwise. Qt 5.1.1 FFe now approved!
[17:36] <sil2100> \o/ Rock on!
[17:36] <Mirv> sil2100: in around 25mins, yes, but I just realized that yes it's Tuesday and then "oh no" :)
[17:36] <sil2100> ;)
[17:37] <sil2100> It almost like me last Monday, when I woke up at 11 and went 'oh nooo I'm laate!'
[17:37] <Mirv> right :)
[17:39] <sil2100> seb128: can I get a quick packaging change ACK? :)
[17:39] <seb128> sil2100, sure
[17:40] <sil2100> seb128: http://10.97.0.1:8080/view/cu2d/view/Head/view/Services/job/cu2d-services-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_location-service_0.0.1+13.10.20130903-0ubuntu1.diff <-
[17:40] <Mirv> I updated the sheet earlier today so it's ready for archive. not much documented in the heat of UDS+FF but some like the qtpim update that was done a couple of hours before FF (it's not included in the FFe)
[17:40] <seb128> sil2100, +1
[17:40] <sil2100> Mirv: I'll be archiving it before EOD today, thanks!
[17:41] <Mirv> sil2100: thanks! one more mental note that occured to me completely separately, do we need platform-api build forcing together with mir to migrate mir from proposed pocket?
[17:41] <Mirv> (that can be pondered tomorrow)
[17:42] <sil2100> Mirv: hm, let's discuss that tomorrow maybe
[17:44] <tjaalton> seb128: and now it works
[17:44] <seb128> tjaalton, weird, what did you change?
[17:44] <tjaalton> dunno, ran a lock screen once
[17:44] <tjaalton> via a hotkey
[17:54] <sil2100> seb128: are you still around for one last packaging ACK?
[17:54] <fginther> sil2100, approved
[17:54] <sil2100> fginther: thanks :)
[17:54] <sil2100> seb128: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_powerd_0.13+13.10.20130903-0ubuntu1.diff <- so I can release platform \o/
[17:54] <sil2100> (it's a main package)
[17:57] <sil2100> ogra_: or maybe if you're still around, could you check and give me a +1 for this powerd change ? ^
[17:58] <sil2100> mterry: hi! Or maybe you, Michael? ;) ^
[17:59] <sil2100> Laney: could you take a look? ^
[19:19] <jibel> chrisccoulson, hey, I investigated this firefox autopkgtest crash again, but found nothing interesting, nothing else than gnome-session crashing on qemu without 3D accel. I reproduced it locally, with and without the wrapper of firefox testsuite, and by forcing or not the fallback session
[19:19] <jibel> and the test session or another
[19:19] <jibel> chrisccoulson, I'll continue tomorrow