[03:16] <KombuchaKip> Anyone know how to get my music to resume playing instead of pausing when I lock my machine under Ubuntu Trusty? Rhythmbox just pauses for some reason.
[03:19] <sarnold> KombuchaKip: I think that's a logind byproduct; I think you can set permissions on audio devices in /dev/ to something your user account can write to..
[03:20] <KombuchaKip> sarnold: Thanks man.
[03:54] <maclin> pitti, hi，the language pack is still 0408 version. Will it be updated before released?
[05:16] <pitti> maclin: yes; the LP export finished yesterday evening; I kicked off the package build, and will test and upload it now
[05:16] <Mirv> maclin: I think the base packages will be updated (too) to the 0410 which is mentioned at https://translations.launchpad.net/ubuntu/trusty/+language-packs - which is needed because only the base packs apparently include help translations
[05:16] <Mirv> ah
[05:17] <Mirv> timing +1
[05:38] <maclin> pitti, thanks. we are waiting for that to test:)
[05:39] <pitti> maclin: would you be willing to test some locally built .debs, as a confirmation that they are good and what you expect?
[05:40] <pitti> I test the German and English ones
[05:41] <maclin> pitti, of course. Our QA team just want to confirm that. Where can we get the debs?
[05:41] <pitti> maclin: hang on (just scp'ing the built sources from the DC machine)
[05:43] <maclin> pitti, good, we are waiting for the Chinese ones:)
[05:49] <pitti> maclin: I put them on http://people.canonical.com/~pitti/tmp/langpack/
[05:51] <maclin> pitti, great, we will get and test, thanks:)
[06:37] <pitti> maclin: how does it look like?
[06:39] <pitti> maclin: they are waiting in https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 now; I accepted all others, as they generally look fine
[06:45] <JackYu> pitti, great, it seems good. maclin is out for a meeting:)
[06:49] <pitti> JackYu: thanks
[07:17] <seb128> good morning desktoper
[07:17] <seb128> brrrr it's cold today
[07:17] <pitti> bonjour seb128
[07:17] <seb128> pitti, salut, ça va ?
[07:17] <pitti> seb128: but still sunny
[07:17] <pitti> seb128: ça va bien, merci ! j'attends avec impatience le releas
[07:17] <pitti> e
[07:18] <seb128> yeah
[07:18] <pitti> seb128: I uploaded fresh langpacks this morning, FYI
[07:18] <seb128> moi aussi, mais j'aurais bien aimé pouvoir mettre à jour quelques paquets tjs
[07:18] <seb128> pitti, nice!
[07:19] <pitti> gedit is back to German for me now
[07:22] <pitti> seb128: Je crois tu peux encore le faire -- parles à infinity ?
[07:22] <pitti> "crois que"
[07:22] <seb128> pitti, oui, je prépare quelques changements là
[07:23] <seb128> but I can see busy SRU time until .1
[07:23] <seb128> so many details/annoyances we didn't get to
[07:23] <seb128> like my ipod showing with an usb stick icon
[07:23] <seb128> dvds still being listed in the UI after being ejected
[07:24] <seb128> it feels like we have been fire fighting until freeze and didn't have time for polish :/
[07:26] <pitti> oh, right, DVDs -- what was that again?
[07:27] <didrocks> an hardware technology
[07:27] <pitti> oh right, these stone disks with enchiseled bits, right?
[07:27] <didrocks> with real objects
[07:27] <seb128> the thing that came after floppies
[07:27] <seb128> I'm pretty sure we still have bugs with those btw
[07:27] <pitti> you bet
[07:27] <seb128> ;-)
[07:27] <seb128> oh can we release with bugs in floppy handling!?
[07:28] <pitti> I'm fairly sure I've seen a bug report about udisks not handling 45 rpm records right
[07:28] <seb128> hehe
[07:28] <seb128> joke aside, lot of polish I want to do for .1
[07:28] <pitti> *nod*
[07:28] <andyrock> seb128, https://bugs.launchpad.net/unity/+bug/1281058
[07:28] <ubot2> Launchpad bug 1281058 in unity (Ubuntu) "The system shutdowns when multiple accounts are open" [High,In progress]
[07:29] <andyrock> it's an oem-priority
[07:29] <andyrock> do I need to open another bug for the UIFe
[07:29] <andyrock> ?
[07:29] <pitti> please, no
[07:29] <seb128> andyrock, no
[07:29] <pitti> it's utterly confusing to track an issue in two dfiferent places
[07:29] <seb128> just retitle the existing one
[07:29] <pitti> seems my right hand is lagging today
[07:30] <seb128> andyrock, Trevinho: btw is somebody investigating the lockscreen giving input to what is behind it sometimes?
[07:30] <seb128> that seems a release blocker/security issue
[07:31] <pitti> ah yeah, the new lock screen is still rather buggy, too -- .1 material for sure
[07:31] <pitti> especially with user switching
[07:31] <pitti> and it still reveals the actual desktop for about a second or so
[07:31] <seb128> right
[07:31] <seb128> though some fixes landed this night
[07:31] <andyrock> well g-s used to do the same
[07:31] <didrocks> yeah, it's like, "it's there. Ahaha! ah no it's not :p"
[07:31] <seb128> I need to upgrade/restart my session
[07:33] <andyrock> so it's not a regression... and using the system-indicator to switch user should call PromptLock that skips fading
[07:34] <seb128> andyrock, you are speaking about the "show for a second", not about the "sometime input is on the win behind the lock" (which can be IRC, annoying when you type your password)
[07:39] <andyrock> sure
[07:40] <andyrock> last time I checked the code there was code to avoid it...
[07:40] <seb128> andyrock, Trevinho: could be https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 ?
[07:41] <andyrock> yep
[08:04] <Laney> hey
[08:05] <seb128> Laney, happy friday! how are you?
[08:06] <Laney> good thanks! happy friday to you too ;-)
[08:06] <Laney> how are you?
[08:06] <seb128> good!
[08:07] <Laney> i see sun and blue sky
[08:09] <Laney> Launchpad (136)
[08:09] <Laney> wtf
[08:09] <seb128> is that the queue?
[08:09] <Laney> bug mail overnight
[08:09] <seb128> oh
[08:09] <seb128> fun
[08:10] <seb128> my inbox was rather quiet this nigh
[08:10] <seb128> t
[08:10] <Laney> erm, weird
[08:10] <Laney> it's mainly translation import errors for cinder
[08:10] <Laney> why in the world did i get those?
[08:10] <Laney> that's an openstack thing
[08:11] <seb128> the bottom of the emails should say?
[08:11] <Laney> not for those, but it does say in the body
[08:11] <Laney> On 2013-10-30 16:41z (162 days 7 hours 48 minutes ago), you uploaded
[08:11] <Laney> ...
[08:11] <seb128> haha
[08:12] <seb128> andyrock, Trevinho: is anyone reviewing https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 ?
[08:14] <seb128> Laney, we are likely going to need an unity upload today btw
[08:14] <seb128> Laney, I hope ^ fixes the "input goes under the lock" issue didrocks&I saw yesterday
[08:16] <Laney> if we can fix that and ideally the grab thing it should go in
[08:16] <seb128> cool
[08:17] <Laney> having a test user in lightdm offends my eyes
[08:17]  * Laney deletes with fire
[08:23] <didrocks> Laney: you reenabled that plugin? :p
[08:23] <Laney> I have a precision blowtorch next to my ssd for such events
[08:26] <didrocks> heh
[08:32] <seb128> Laney, I guess it's too late/not realistic to want to land indicator-keyboard change to use an upstart job? (knowing it would require a one liner change to ubiquity as well)
[08:32] <Laney> probably
[08:32] <Laney> what does it fix?
[08:33] <seb128> nothing reported
[08:33] <seb128> it's just that the indicator would have its own log and be respawned if it hit a segfault
[08:33] <seb128> would also be consistent with other indicators
[08:34] <Laney> I think best not, the time for that kind of stuff has been and gone
[08:34] <seb128> k
[08:34] <Laney> also considering there's been little errors in these things before
[08:34] <seb128> maybe as an SRU (without the path change since ubiquity hardcode directories)
[08:40] <seb128> mvo, hey
[08:40] <seb128> mvo, did we say we should land https://code.launchpad.net/~brian-murray/aptdaemon/bug-1266844/+merge/207276 ? even if it's not a proper solution that's better than no change?
[08:41] <seb128> mvo, that's currently the most reported trusty issue
[08:41] <andyrock> seb128, approved
[08:41] <seb128> andyrock, thanks
[08:41] <andyrock> np
[08:41] <mvo> seb128: didn't I upload this yesterday?
[08:41] <andyrock> seb128, now i've an exam
[08:41] <andyrock> i'll be online
[08:41] <seb128> andyrock, good luch!
[08:41] <seb128> luck even
[08:42] <seb128> mvo, oh
[08:42] <seb128> autopkgtest for aptdaemon 1.1.1-1ubuntu4: FAIL (Jenkins: public, private)
[08:42] <andyrock> this afternoon to fix other bugs ;)
[08:42] <seb128> mvo, it's blocked in proposed
[08:42] <seb128> andyrock, k!
[08:42] <mvo> seb128: meh, can this be overriden? afaik its failing since the begining of time
[08:42] <seb128> hum
[08:42] <seb128> https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-aptdaemon/
[08:42] <seb128> yeah
[08:42] <seb128> I wonder how the previous version went through
[08:42] <seb128> I guess somebody overwrote it
[08:42] <seb128> Laney, ^
[08:43] <Laney> I don't see evidence of that
[08:43] <Laney> probably one of the bugs let it in
[08:43] <Laney> It started failing with the ubuntu3 upload
[08:44] <Laney> hang on, might be being misled
[08:44] <Laney> I don't think we have enough history there
[08:45] <Laney> anyway, it didn't fail since the beginning of time but got broken some point this cycle
[08:46] <seb128> mvo, is the test looking like something that can be easily fixed?
[08:47] <mvo> seb128: I check it now
[08:48] <Laney> On ci.debian.net the output includes the diff of dependency and base system changes since the last run
[08:48] <Laney> pretty useful http://ci.debian.net/data/unstable-amd64/packages/p/pango1.0/2014-03-23.log
[08:48] <seb128> nice
[08:48] <Laney> we should get that ;-)
[08:48] <Laney> let me skip this test if mvo is going to look at fixing it
[08:48] <Laney> thanks mvo!
[08:49] <seb128> Laney, mvo: thanks
[08:51] <mvo> Laney: is it possible to (re)test  1.1.1-1ubuntu2 ? I would not be suprised if it actually fails now too
[08:51] <Laney> Dunno about on jenkins, but you should be able to fetch it and do that locally
[08:52] <Laney> Jenkins doesn't seem to keep the first test that failed and the last one that passed so it's not very easy to compare what changed
[08:54] <mvo_> re
[08:54] <seb128> mvo_, wb!
[08:54] <mvo_> silly network
[09:20] <seb128> Laney, not sure if you saw my telepathy-indicator mention on #u-release
[09:20] <seb128> quite busy discussion
[09:20] <Laney> yeah, will look shortly
[09:20] <seb128> thanks
[09:20] <Laney> scripting fun
[09:21]  * larsu hears something about telepathy-indicator
[09:22] <seb128> larsu, trying to land your fix from yesterday evening
[09:22] <larsu> ah cool, thanks
[09:22] <larsu> I wonder what's going on in bug #1259564
[09:22] <ubot2> Launchpad bug 1259564 in indicator-messages (Ubuntu) "GPG_AGENT_INFO not being passed to thunderbird" [Undecided,Confirmed] https://launchpad.net/bugs/1259564
[09:23] <larsu> I guess GPG_AGENT_INFO isn't set in dbus' environment?
[09:23] <larsu> for some reason, indicator-messages was not ported to upstart
[09:23] <larsu> maybe that would help? (or is that moot now anyway?)
[09:23] <seb128> it was not?
[09:23] <seb128> we should maybe have landed those branches from tedg earlier in the cycle :/
[09:24] <seb128> it is, /usr/share/upstart/sessions/indicator-messages.conf
[09:24] <seb128> $ status indicator-messages
[09:24] <seb128> indicator-messages start/running, process 2600
[09:24] <seb128> larsu, use upstart here?
[09:25] <larsu> oh, when did that land?
[09:25] <larsu> I tried a couple of days ago and was sure it wasn't ported
[09:25] <larsu> maybe I was just confused
[09:26] <seb128> larsu, oh, sorry, too much going on, we landed that earlier this week :p
[09:27] <seb128> larsu, ogra needed it for the touch image
[09:27] <seb128> larsu, https://launchpad.net/ubuntu/+source/indicator-messages/13.10.1+14.04.20140408-0ubuntu1
[09:27] <larsu> thanks :)
[09:27] <seb128> larsu,
[09:27] <seb128> $ strings /proc/`pidof indicator-messages-service`/environ | grep GPG
[09:27] <seb128> GPG_AGENT_INFO=/tmp/gpg-n3dktm/S.gpg-agent:2448:1
[09:27] <seb128> larsu, bug fixed? :-)
[09:28] <larsu> seb128: I guess?! I'll mark it as fixed an ask to reopen if it still happens to people. Thanks!
[09:28] <seb128> it's buggy though
[09:28] <larsu> oh it is?
[09:28] <seb128> $ strings /proc/`pidof compiz`/environ | grep GPGGPG_AGENT_INFO=/run/user/1000/keyring-H21sVl/gpg:0:1
[09:29] <seb128> bah, fighting agents
[09:29] <seb128> larsu, not an issue from the indicator though
[09:29] <larsu> seb128: I don't see the problem?
[09:30] <larsu> oh, different agents
[09:30] <larsu> should I reassign to another component?
[09:31] <seb128> larsu, close the indicator-messages bug, saying that specific issue
[09:31] <seb128> is fixed
[09:32] <larsu> ok
[09:32] <seb128> larsu, the other issue seems to be https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1257706
[09:32] <ubot2> Launchpad bug 1257706 in gnupg2 (Ubuntu) "gpg-agent environment variables not correctly exported" [Undecided,Confirmed]
[09:32] <seb128> or similar
[09:33] <seb128> we have a few bugs about fighting agents I think :/
[09:33] <seb128> it's another of those "we should fix that for .1" issues
[09:33] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591
[09:33] <ubot2> Launchpad bug 1271591 in gnome-keyring (Ubuntu) "upstart job race prevents gnome-keyring from being ssh agent" [High,Triaged]
[09:34] <seb128> larsu, ^ use that one as reference if you want to point to another bug in your comment
[09:34] <larsu> seb128: too late :)
[09:34] <seb128> k, no worry
[09:34] <larsu> seb128: it's already linked to in a previous comment in the bug
[09:35] <seb128> k
[09:57] <mvo_> pitti: what was the best way again to run a package against adt?
[09:59] <pitti> mvo_: the official docs are in /usr/share/doc/autopkgtest/README.running-tests.gz; which package do you want to test?
[09:59] <pitti> mvo_: i. e. for most packages schroot is enough (and I suppose you have them already)
[09:59] <pitti> mvo_: for some which need network or kernel bits you need to run in an LXC container or even Qemu
[10:01] <mvo_> pitti: as close as possible to what jenkins is doing if possible, I don't really understand the failure for aptdaemon currently
[10:02] <mvo_> pitti: but thanks, I will play with it and see if lxc gives me a similar failure first
[10:02] <pitti> mvo_: I get the failures with simply running the tests on my workstation in trunk
[10:03] <pitti> without any adt-run stuff at all
[10:03] <mvo_> pitti: oh, exactly the same failures?
[10:03] <pitti> mvo_: perhaps not exactly (haven't compared bit by bit), but enough of them
[10:03] <mvo_> ok
[10:04] <pitti> mvo_: as for "exactly what jenkins is doing" -> prepare-testbed and run-adt-test as per http://packaging.ubuntu.com/html/auto-pkg-test.html
[10:04] <mvo_> thanks again
[10:05] <pitti> mvo_: I run "adt-run -o /tmp/out aptdaemon --- schroot trusty" here to compare with jenkins output
[10:05] <mvo_> pitti: please update to the current ubuntu-trusty bzr, I fixes some failures already
[10:05] <mvo_> (I think :)
[10:05] <pitti> ah
[10:06] <pitti> mvo_: seems 1.1.1-1ubuntu4 is already released in the branch, but not in trusty?
[10:07] <mvo_> pitti: trusty-proposed maybe?
[10:07] <pitti> mvo_: ah yes, held back by test failures
[10:07] <mvo_> pitti: I was using the packaging branch - should I use the bzr+ssh://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/ubuntu-trusty/ ?
[10:07] <mvo_> one?
[10:07] <pitti> so, running
[10:07] <pitti> adt-run -o /tmp/out aptdaemon -U --apt-pocket=proposed --- schroot trusty
[10:08] <pitti> mvo_: yes, that's the one I usually use as well -- it's what Vcs-Bzr: says
[10:08] <pitti> mvo_: oh, you don't use UNRELEASED?
[10:09] <mvo_> pitti: ok, sorry, let me fix that
[10:09] <pitti> or tags?
[10:09] <mvo_> pitti: it should be on unreleased, let me double check
[10:09] <pitti> mvo_: so, I'm not 100% sure that lp:~aptdaemon-developers/aptdaemon/ubuntu-trusty/ matches exactly what's in trusty-proposed, I just hope it does
[10:10] <pitti> changelog-wise it fits
[10:11]  * darkxst really wonders how release week will go with moving and house and probably no internet for a bit ;(
[10:11] <Laney> hopefully you have some ISO testers
[10:11] <mvo_> pitti: I commited my changes now to lp:~aptdaemon-developers/aptdaemon/ubuntu-trusty/
[10:11] <Laney> also luckily with LTSes you have a .1 release
[10:12] <mvo_> pitti: i.e. the ubuntu5 fixes
[10:12] <pitti> mvo_: ah, splendid, thanks
[10:12] <darkxst> we have lots of testers!
[10:21] <pitti> mvo_: hmm, seems the trusty-proposed version hangs in schroot, re-trying in lxc
[10:22] <mvo_> pitti: I have two test failure currently, its slowly improving :) lxc seems to be working for me
[10:22]  * pitti runs both in parallel
[10:22] <pitti> $ adt-run -o /tmp/out-trunk -B .// --- lxc -es adt-trusty
[10:22] <pitti> for your trunk branch; that'll build the branch first and use the built .debs
[10:28] <mpt> Weird, Software Updater’s “Technical Description” pane anti-aliases its text in a different way from everything else on the system
[10:28] <pitti> mvo_: sorry, I need to leave for the afternoon
[10:29] <Laney> I really hate software updater's progress bar when it's checking for updates
[10:31] <pitti> mvo_: so, prepare-testbed and run-adt-test are the ultimate "production" verification
[10:31] <ogra_> Laney, image based upgrades will fix that :)
[10:31] <seb128> Laney, why?
[10:32] <mpt> Laney, that has three factors: (1) It spends a long time checking for updates <https://wiki.ubuntu.com/SoftwareUpdates#Ideas>, (2) recursive references mean it can’t predict ahead of time how many sources will need checking, and (3) the Ambiance/Radiance indeterminate progress bar is poorly designed (hi Cimi:-)
[10:32] <seb128> ogra_, image based upgrades also have a download bar ;-)
[10:32] <darkxst> r0
[10:32] <seb128> ogra_, though the "update" is a spinner for "checking for updates"
[10:32] <ogra_> seb128, yeah, but a predefined set of files
[10:32] <Cimi> ciao mpt :P
[10:33] <Laney> mpt: I think it's mainly (3) that I've got an issue with
[10:33] <Laney> It moves too fast and doesn't move smoothly
[10:34] <mpt> Yes indeed
[10:34] <Laney> Just looks like it's jerking around
[10:34] <seb128> Laney, didrocks: can you please test https://launchpad.net/~ci-train-ppa-service/+archive/landing-011/ (lock screen fixes)
[10:34] <mpt> And it bounces at all, like the Windows one does, which can be misleading if you glance at it at the wrong time
[10:34] <mpt> (specifically if you glance at it when it happens to be against the left edge)
[10:37] <mvo_> pitti: thanks, I'm on it now
[10:37] <Laney> Interesting; that's provided by aptdaemon
[10:39] <darkxst> speaking of aptdaemon (well nearly) what happens when we need an appstream to make gnome-software work?
[10:39] <seb128> what do you mean?
[10:40] <seb128> what appstream exactly?
[10:40] <darkxst> so now all gnome apps have an appdata file
[10:40] <darkxst> but for gnome-software to work, these need to hosted by some server
[10:41] <darkxst> fedora has it, and I think openSuse
[10:41] <seb128> is GNOME having one?
[10:41] <seb128> hum, why is that let down to distros?
[10:41] <darkxst> GNOME is not a distro!
[10:41] <Laney> So it can be used for all apps I guess
[10:42] <Laney> like app-install-data or something, but hosted remotely?
[10:42] <seb128> why does it need a server? can't we have a package containing the db?
[10:42] <darkxst> seb128, that is half-way hack I guess
[10:42] <seb128> "hack", I don't agree
[10:43] <seb128> but yeah, I don't see Canonical working on a such server in the near futur
[10:43] <seb128> not sure, you guys could perhaps have a people page/team/community maintained version
[10:45] <darkxst> seb128, apart from phillw (who has been somewhat ejected from the community), we have no infrastructure resources
[10:46] <darkxst> (outside of what Canonical provides)
[10:47] <seb128> brb, session restart to test unity lockscreen fixes
[10:49] <Laney> seb128: what's it meant to fix? your bug from yesterday?
[10:50] <seb128> Laney, https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360
[10:50] <Laney> yeah
[10:50] <seb128> see the description
[10:50] <seb128> I couldn't reproduce that alt-tab problem
[10:50] <seb128> but I guessed the "type through lockscreen" didrocks and I saw could be the same issue
[10:51] <seb128> Laney, in any case just sanity check/test that you have no regression with lock screen
[10:51] <Laney> oh yeah I made that happen
[10:51] <seb128> the alt-tab thing?
[10:51] <Laney> yep
[10:51] <seb128> you saw the UI on top of lock?
[10:52] <Laney> just the alt tab switcher
[10:52] <seb128> k
[10:52] <Laney> now lock screen doesn't get input
[10:52] <seb128> be careful
[10:52] <seb128> the stuff behind might
[10:52] <Laney> and yep, input is going to windows underneath
[10:52] <seb128> like it could be IRC :p
[10:52] <Laney> laney@raleigh> more bar                                                                                                                    ~
[10:52] <Laney> foo
[10:52] <Laney> nah, no IRC on that machine
[10:52] <seb128> workaround to unlock is to use the session indicator
[10:52] <seb128> switch user
[10:52] <seb128> log back from lightdm
[10:52] <seb128> that unlocks the session
[10:52] <Laney> adding the PPA and restarting session
[10:52] <seb128> you are testing without that ppa right?
[10:52] <seb128> cool
[10:56] <Laney> seb128: seems to fix that issue indeed
[10:56] <seb128> Laney, seems to fix the one we were having as well
[10:56] <seb128> let me land that
[10:56] <Laney> nice
[10:56] <seb128> Laney, thanks for testing
[10:56] <Laney> I never had that one so can't confirm
[10:58] <seb128> well, improvement in any case
[10:58] <seb128> let's get that in
[10:59]  * darkxst wonders.... how many servers does canonical have? surely hosting an appstream instance wouldn't even put a dent in it!
[10:59] <Laney> you'd have to talk to the sysadmins
[10:59] <Laney> #canonical-sysadmin @ freenode
[11:00] <Laney> I doubt it's very likely though, most people (LoCos etc) seem to arrange their own sponsorship
[11:00] <seb128> the issue is not bandwith
[11:01] <seb128> it's admin work/security of the machine
[11:01] <seb128> e.g not sure what sort of permissions appstream needs, what security record it has, etc
[11:03] <darkxst> from the public side it would be a read-only stream of data
[11:03] <seb128> how/who would update the content?
[11:04] <darkxst> appdata files come from upstream
[11:04] <seb128> how do they get on the server?
[11:04] <darkxst> a script I guess!
[11:04] <seb128> you need a mechanism/a way to tell it what to import
[11:04] <seb128> the script would list all the upstream in the world with their urls?
[11:04] <seb128> or have an Ubuntu archive to parse
[11:04] <seb128> or?
[11:05] <darkxst> hypothetically the script would parse ubuntu packages for appdata
[11:05] <seb128> k
[11:05] <seb128> well I guess somebody needs to come with a detailed plan first of what would happen on the server
[11:06] <seb128> what would need to be installed
[11:06] <seb128> who would have access, etc
[11:06] <seb128> then you can try asking IS for hosting
[11:08] <darkxst> seb128, ok, I seem to be lacking time these days, but I will get one of my drones onto it!
[11:08] <seb128> ;-)
[11:17] <seb128> nice, today iso is 50M smaller
[11:17] <seb128> seems like to be the langpacks base refresh
[11:17] <seb128> well I guess it is, the manifest doesn't point to actual package dropped from the image
[12:05] <desrt> good morning ubuntistoj
[12:46] <seb128> desrt, hey
[12:47] <desrt> hihi
[12:47] <ochosi> hey seb128
[12:47] <seb128> ochosi, hey
[12:47] <ochosi> seb128: do you think you could review a very simple patch for indicator-bluetooth?
[12:48] <ochosi> or would i better talk to someone else about that
[12:48] <seb128> ochosi, just give the url, I'm sure larsu or charles or cyphermox can do that ;-)
[12:48] <ochosi> ok, well it's not ready yet :D
[12:48] <ochosi> but i basically need to get an alternative depend in for indicator-bluetooth
[12:48] <mvo_> seb128: tests pass !
[12:48] <ochosi> oterwise we pull the unity-stack just for that indicator...
[12:48] <seb128> mvo_, wooot
[12:49] <seb128> ochosi, oh, that I can ack
[13:06] <Laney> hmm
[13:06] <Laney> did someone say there was a click updates bug in u-s-s?
[13:06] <seb128> Laney, https://launchpad.net/bugs/1306569
[13:06] <ubot2> Launchpad bug 1306569 in ubuntu-system-settings (Ubuntu) "Can't update clicks from store with u-s-s #287 on mako" [High,Confirmed]
[13:06] <Laney> I was just fixing the tests (hopefully correctly...) and I think I saw a bug there that might make all click updates be ignored
[13:10] <seb128> Laney, \o/
[13:10] <seb128> Laney, it's weird, the service doesn't even seem activated when I use the panel here
[13:11] <Laney> I don't know how it works really
[13:12] <Laney> so I could be wrong, but the test that checks new updates are shown was failing
[13:12] <Laney> will test it in a bit
[13:16] <seb128> Laney, thanks
[13:16] <seb128> Laney, do you still have an ubuntu codesearch somewhere?
[13:22] <Laney> seb128: same place it always was - http://ubuntu-codesearch.surgut.co.uk/search?weighted=1&q=seb128
[13:24] <charles> ochosi: if it's a packaging patch to indicator-bluetooth, cyphermox or seb128 would be the ones to look at it
[13:24] <charles> ochosi: if it's code, me or cyphermox
[13:25] <Laney> It'll need to call whatever xfce program instead of the control-center
[13:25] <seb128> Laney, weird
[13:25] <Laney> (I guess)
[13:25] <seb128> Laney, http://ubuntu-codesearch.surgut.co.uk/search?weighted=1&q=indicator-keyboard-service
[13:25] <seb128> Laney, doesn't list http://paste.ubuntu.com/7234846/
[13:25] <seb128> Laney, well, ubiquity include the string and is not listed?
[13:25] <Laney> odd
[13:26] <seb128> bregma, hey
[13:27] <bregma> uh-oh, now what?
[13:27] <Laney> ubuntu@codesearch:/srv/mirror-unpacked/ubiquity_2.18.1$ grep -r indicator-keyboard-service *
[13:27] <Laney> bin/ubiquity-dm:                            'indicator-keyboard-service',
[13:27] <Laney> hmm!
[13:27] <seb128> bregma, I did a landing of https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 while you were sleeping, hope it's ok
[13:27] <seb128> Laney, hmm indeed!
[13:27] <bregma> seb128, as long as you do the required paperwork
[13:27] <seb128> bregma, it looks like it fixes the "can type through lockscreen" issue didrocks&I we having
[13:28] <seb128> bregma, what paperwork?
[13:28] <bregma> after final freeze, don't you need to SRU the fix?
[13:28] <andyrock> seb128, https://bugs.launchpad.net/unity/+bug/1306211
[13:28] <ubot2> Launchpad bug 1306211 in unity (Ubuntu) "Trying to lock screen in a guest session leads to an unusable session" [Undecided,New]
[13:28] <seb128> bregma, well, release team judged it important enough to include it as a freeze exception
[13:28] <andyrock> can you still reproduce it?
[13:29] <seb128> bregma, they are still landing some rc fixes today
[13:29] <andyrock> seb128, it works fine here
[13:29] <andyrock> actually there should be no "lock" button in guest session
[13:29] <seb128> andyrock, it took me 10 tries to get it again, and the issue stops if I touch the keyboard
[13:29] <bregma> seb128, I have no problem with that
[13:29] <seb128> bregma, great, was more a fyi anyway ;-)
[13:30] <andyrock> but what you mean for unsable
[13:30] <andyrock> ?
[13:30] <andyrock> lockscreen shows up?
[13:30] <andyrock> or the screen fails to turn on?
[13:30] <seb128> andyrock, no, it dime and wake up the screen in loop, making the session impossible to use
[13:30] <seb128> like screen goes dooown up doooown up dooown up
[13:30] <andyrock> ok
[13:31] <seb128> andyrock, the "lock" is in the "logout" unity dialog
[13:31] <seb128> another unity bug
[13:32] <andyrock> yeah that's another story ;)
[13:32] <seb128> that option shouldn't be listed when lockscreen is locked down
[13:33] <ochosi> charles: ok thanks!
[13:41] <Trevinho> seb128: oh thanks for the landing... Last night just after the final freeze, the fever took me, si I passed a pretty bad night /morning... :(
[13:44] <seb128> Trevinho, :-(, get better!
[13:45] <seb128> Trevinho, https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 might be the issue we were having yesterday
[13:47] <Trevinho> seb128: seb yes very likely.... It's actually nux fault, since when you delete a view that is grabbing, then you should remove the grab also ;\
[13:47] <Trevinho> But this is fine, as we make sure the view is ungrabbed anyway.
[13:48] <seb128> right
[13:48] <seb128> Trevinho, see, it was a real bug, and not me or my box being crazy ;-)
[13:49] <seb128> charles, xnox: https://code.launchpad.net/~seb128/indicator-power/ubiquity/+merge/215424
[13:49] <Trevinho> seb128: yes, in fact I also said that all the ones you report are real bugs :), but just that for some reason you always it them all! :)
[13:50] <charles> seb128, acked
[13:50] <Trevinho> pitti: with last landing and last indicator session, the screen on tty switch is basically shown immediately...
[13:51] <Trevinho> As before we had not a concept of prompt or fading lock. Which now we have
[13:52] <seb128> right
[13:52] <seb128> Trevinho, andyrock: what's the deal with power off, when is it supposed to happen?
[13:52] <seb128> if you lock and don't touch anything it starts diming off after some seconds
[13:52] <seb128> I guess that's wanted
[13:53] <seb128> if you (or your cat) mouve the cursor though, it never goes off again then
[13:53] <seb128> that's a bug?
[13:53] <Trevinho> pitti: btw in some cases I see login1 not to emit the lock signal to us... For example call multiple time the display manager lock. We get that signal only If the greeter wasn't there before
[13:53] <Trevinho> It looks light dm does something strange
[13:54] <Trevinho> seb128: it must go off after the defined desktop idle time
[13:54] <Trevinho> seb128: we use a shorter delay only once
[13:55] <andyrock> Trevinho, i think it makes sense to use a shorter timeout also the second time
[13:55] <andyrock> etc. etc.
[13:55] <andyrock> that's what seb128 is saying
[13:55] <andyrock> right?
[13:55] <seb128> Trevinho, andyrock: doesn't seem to work, let us try
[13:55] <seb128> andyrock, no
[13:56] <seb128> didrocks did "lock, move mouse, walk away" and went away for some hours yesterday
[13:56] <andyrock> seb128, oh so your screen does not dim anymore?
[13:56] <seb128> he uses a timeout of 30 min
[13:56] <seb128> the screen never stopped
[13:56] <Trevinho>  andyrock Not to go against the user preferences (that also might about never use Screensaver)... And say you only locked to hear the music
[13:56] <seb128> Trevinho, andyrock: we just tried with 1 min, doesn't work
[13:57] <seb128> doh
[13:57] <seb128> it's working :p
[13:57] <Trevinho> seb128: it works with 1 sec
[13:57] <seb128> spoke too soon
[13:57] <seb128> ok, maybe a bug fixed in yesterday update
[13:57] <seb128> or maybe another corner case or something
[13:57] <Trevinho> seb128: this wasn't Murphy... :-D
[13:57] <seb128> lol
[13:58] <Trevinho> seb128: we always does it when we get the presence status dorm uss power
[14:02] <Trevinho> From*
[14:04] <seb128> Laney, let me know how the click upgrade stuff goes, I did some pinging of the u1 guys about the issue earlier, I want to unping them if we fix it
[14:12] <xnox> seb128: something weird happens to my sound indicator under ubiquity
[14:12] <seb128> xnox, oh, what?
[14:14] <xnox> seb128: https://plus.google.com/photos/109160032876474505377/albums/6001038263425551073/6001038268744851618?authkey=CKXGwua3-JS1HA&pid=6001038268744851618&oid=109160032876474505377
[14:14] <xnox> seb128: btw it's very painful to share a single photo from G+ without posting it on the feed!
[14:15] <xnox> seb128: i'm dist-upgrading now, and will try without power-indicator to see if there is some weird interaction between them / width limit
[14:15] <xnox> cause, well, Gtk+ =))))
[14:16] <seb128> xnox, urg, looks like a missing icon for mute in the theme? weird
[14:16] <seb128> cool phone case btw ;-)
[14:17] <seb128> xnox, indicator-power seems happy at least ;-)
[14:17] <Laney> are you in bed?
[14:21] <xnox> Laney: haha.
[14:21] <xnox> Laney: i was trying to get the lighting on the screen right for the picture. Got to figure out how to do screenshots properly from cmdline / externally triggered.
[14:22] <xnox> seb128: missing icon sounds interesting. I'll test in the VM properly in a sec.
[14:36] <seb128> Laney, your branch fixes the clicks
[14:37] <Laney> huh, how about that
[14:38]  * seb128 line up a landing
[14:38] <Laney> I'd like gatox to review the changes before they actually go in
[14:38] <Laney> but you can get it underway
[14:39] <gatox> Laney, ack
[14:39] <Laney> ty
[14:39] <seb128> Laney, ah, I was just querying him to ask for that, didn't notice he was there ;-)
[14:56] <xnox> seb128: it's all good, once i booted into proper live cd image, instead of trying to hack things up locally.
[14:56] <Laney> updates panel is buggy if you refuse the update then go back in
[14:56] <xnox> seb128: so go ahead with releasing indicator-power.
[14:56] <Laney> I have a blank panel now
[15:00] <seb128> xnox, great
[15:00] <seb128> Laney, yeah, saw that
[15:00] <seb128> Laney, there is one issue with your update, it restores the bug "tests fail if updates are available"
[15:02] <Laney> it didn't happen because updates were never available?
[15:04] <seb128> ?
[15:05] <seb128> oh, right
[15:05] <seb128> I think it might be the fix for that issue that causes the problem
[15:07] <seb128> Laney, the change was http://bazaar.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/revision/647
[15:07] <seb128> Laney, which was in reaction to https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/+merge/208567/comments/499988
[15:08] <Laney> sec
[15:13] <Laney> seb128: ok, fixed
[15:13] <Laney> the issue is evident in that diff
[15:13] <Laney>         os.environ["IGNORE_UPDATES"] = "True"
[15:13] <Laney>     return value == "IGNORE_UPDATES";
[15:17] <Laney> This means it doesn't have any autopilot tests for when there are updates
[15:18] <Laney> the interaction of the different bugs here is quite funny
[15:26] <seb128> Laney, that IGNORE_UPDATES is a bit weird, wouldn't it make sense to have it a bool as well?
[15:27] <Laney> the other one isn't a bool
[15:27] <Laney> it's a string which says "True"
[15:27] <Laney> it is all weird, didn't want to get too deep
[15:27] <Laney> I'd have just done the normal check for it being set to anything nonempty
[15:27] <seb128> k, makes sense
[15:28] <seb128> well at least it fixes the case
[15:28] <seb128> I'm going to put a silo with the fixes lined up
[15:28] <seb128> gatox, can you review the change, it's small ;-)
[15:28] <seb128> gatox, I'm waiting on the review to land the fix
[15:28] <gatox> seb128, ok, on it now
[15:28] <seb128> gatox, thanks
[15:29] <Laney> the other env var is inverted with respect to this one as well
[15:29] <Laney> so double weird
[15:29] <seb128> yeah, let's clean that later
[15:29] <Laney> it could do with a round of fixes
[15:29] <seb128> indeed
[15:37] <gatox> seb128, Laney need info: https://code.launchpad.net/~laney/ubuntu-system-settings/fix-tests/+merge/215417
[15:38] <gatox> Laney, seb128 about those envs, it's that way because the api to read that, it only returns strings
[15:39] <seb128> is that a qt api?
[15:39] <gatox> seb128, yes, QProcessEnvironment
[15:39] <seb128> k
[15:40] <Laney> of course it does, that's what env vars are
[15:40] <gatox> right
[15:40] <seb128> you can use 0/1 strings though ;-)
[15:41] <seb128> or 0 !0
[15:42] <seb128> Laney, saw gatox's review comment?
[15:42] <Laney> yes
[15:42] <seb128> cool
[15:46] <andyrock> seb128, do you know where are located the xml files for the default rotating wallpapers?
[15:46] <seb128> andyrock, /usr/share/gnome-background-properties/
[15:47] <andyrock> thx
[15:47] <seb128> yw!
[15:48] <seb128> you are adding support for those to the lock screen?
[15:48] <gatox> Laney, ping me when you answer the question or if you do any change, so i review it right away
[15:48] <Laney> I did answer
[15:49] <Laney> basically to say that I don't understand it
[15:49] <Laney> so if you have a better fix then please do it :-)
[15:49] <andyrock> seb128, mmm we can but there was a bug I want try to reproduce
[15:49] <gatox> Laney, my suggestion is just to revert the changes in update_manager.cpp
[15:49] <andyrock> https://bugs.launchpad.net/unity/+bug/1301842
[15:49] <ubot2> Launchpad bug 1301842 in Unity "lockscreen re-locks after unlocking if wallpaper chaged in the backgroud" [Undecided,New]
[15:50] <Laney> gatox: not if you want the tests to work
[15:50] <Laney> try it
[15:50] <andyrock> seb128, i think it's just a duplicate
[15:50] <seb128> andyrock, k, I was going to say that it doesn't seem to highest priority thing to look at
[15:50] <seb128> andyrock,  please look at bugs before adding support for rotating images ;-)
[15:50] <andyrock> seb128, i was looking at bugs ;)
[15:50] <seb128> great
[15:50] <andyrock> just want to change the duration
[15:50] <seb128> cool
[15:50] <andyrock> so i'll not lose 5 minutes of my life
[15:50] <andyrock> :D
[15:51] <seb128> andyrock, you can also do a "sleep 5; gsettings set ...."
[15:51] <seb128> easier way to change the bg
[15:52] <seb128> andyrock, gsettings set org.gnome.desktop.background picture-uri 'file:///dir/image'
[15:53] <andyrock> cool
[15:56] <seb128> andyrock, can't confirm that one
[15:56] <seb128> gatox, so, do you have a suggested change or should we just land that version (we can tweak/improve later)
[15:56] <Laney> I bet the wallpaper is a red herring there
[15:56] <Laney> i.e. Trevinho is correct
[15:57] <gatox> seb128, running the tests here and checking the thing with update_manager.cpp, just a sec
[15:57] <seb128> k
[15:58] <seb128> Laney, andyrock: yeah, likely just the timeout thing
[16:04] <andyrock> seb128, yeah i marked it as a duplicate
[16:06] <gatox> seb128, Laney i just tested it here, reverting the changes in update_manager.cpp, and it works, and the tests are ok too... the other changes are correct
[16:07] <gatox> was that failing for you?
[16:07] <Trevinho> attente: unity side for https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291461 is done, but is it missing indicator-keyboard?
[16:07] <ubot2> Launchpad bug 1291461 in Unity "Lockscreen: keyboard layout switching shortcuts not working" [Low,Triaged]
[16:08] <Trevinho> attente: as that guy complains something,,,
[16:09] <Laney> gatox: http://paste.ubuntu.com/7235553/
[16:10] <Laney> bzr merge . -r 679..678
[16:10] <Laney> to revert that change
[16:15] <gatox> Laney, i was running autopilot tests... i see, that's because the test is actually wrong, if you want i can fix that and propose a branch
[16:15] <Laney> gatox: yes, the c tests
[16:16] <Laney> please do fix it and push a branch, don't propose it
[16:16] <Laney> I'll pull it into that one
[16:16] <gatox> Laney, ack
[16:23] <Trevinho> Lol, this story is too nice https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303698 :)
[16:23] <ubot2> Launchpad bug 1303698 in unity (Ubuntu) "curiosity killed the trusty tahr" [Undecided,New]
[16:28] <gatox> Laney, there: lp:~diegosarmentero/ubuntu-system-settings/fix-update-not-required-test
[16:30] <Laney> ty
[16:33] <Laney> seb128: I pushed it again, gogogo
[16:33] <seb128> Laney, \o/
[16:34] <Laney> gatox: can you approve the mp?
[16:34] <gatox> Laney, sure
[16:34] <Laney> mergi
[16:34] <Laney> merci
[16:35] <gatox> Laney, seb128 approved
[16:35] <seb128> gatox, thanks
[16:36] <xnox> seb128: Laney: is there some sort of keyboard indicators fixes in the works?
[16:36] <xnox> i'm looking into https://bugs.launchpad.net/ubuntu/trusty/+source/ubiquity/+bug/1301720
[16:36] <ubot2> Launchpad bug 1301720 in ubiquity (Ubuntu Trusty) "[Text Entry] Missing English input in Simplified and Traditional Chinese default enviroment" [High,Triaged]
[16:37] <xnox> and i don't see how ubiquity did anything wrong, since e.g. lightdm login screen has "english" keyboard layout / indicator.
[16:37] <xnox> yet upon login, there is no keyboard indicator and in the keyboard layout panel in the control-center there is no layouts setup what's so ever.
[16:38] <xnox> this is with just ubuntu desktop, executed in chinese locale, not kylin.
[16:38] <seb128> xnox, not sure it's a bug?
[16:38] <seb128> the indicator mixes layout and input methods
[16:38] <xnox> but i will go and test kylin.
[16:39] <xnox> seb128: and in chinese i should have a way to switch to english input method, no?
[16:39] <seb128> so you might have a chinese pinyin input on an english layout regrouped under 1 icon
[16:39] <xnox> i'll test out precise, to see what hapens there.
[16:39] <seb128> check with attente next week
[16:39] <seb128> he's in eow at this time
[16:39] <seb128> xnox, not worth testing kylin, well at least they use a different stack (fcitx)
[16:40] <xnox> seb128: right, i get a weird mini-overlay-popup and i can switch between english and chinese thing. So i think it's not a bug.
[16:43] <seb128> Laney, u-s-s building in https://launchpad.net/~ci-train-ppa-service/+archive/landing-009/
[16:43] <Laney> cool
[16:53] <xnox> i shall not deal with fr locale bugs ever again, i have no idea how to type on the console in that locale
[16:54] <Laney> ZUT ALORS!
[16:56]  * xnox merde...
[16:58] <seb128> ok, have a good w.e everyone!
[16:58] <Laney> you too!
[17:03] <Laney> me too now, see you on monday
[22:02] <xclaesse> what was the trick again to see gnome-online-accounts in the control center?
[22:03] <darkxst> xclaesse, XDG_CURRENT_DESKTOP=GNOME gnome-control-center