[00:20] <darkxst> robert_ancell, hey, if you have a chance could you take a look at my latest g-s-d/g-c-c MP's that should unblock gnome-desktop transition
[00:47] <robert_ancell> darkxst, I reviewed all the ones I saw - which ones are outstanding?
[00:48] <darkxst> robert_ancell, I filed 2 this morning
[00:48] <robert_ancell> darkxst, got the links?
[00:48] <darkxst> https://code.launchpad.net/~darkxst/ubuntu/utopic/gnome-settings-daemon/lp1372346-nodatetime/+merge/236639
[00:48] <darkxst> https://code.launchpad.net/~darkxst/ubuntu/utopic/gnome-control-center/lp1372346-noautotz
[00:57] <darkxst> robert_ancell, also bug 1376069, you missed that when you patched it for unity-control-center?
[00:57] <robert_ancell> ah, good catch
[01:43] <robert_ancell> darkxst, so, does the datetime plugin build now?
[02:01] <darkxst> robert_ancell, no, I disabled it from building
[02:04] <darkxst> it was new code, so couldnt just revert it back to geoclue
[02:04] <darkxst> its only really used for the automatic timezone stuff anyway (atleast in 3.12)
[04:39] <pitti> Good morning
[06:19] <pitti> darkxst, Laney: hmm, https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.12.2-1ubuntu1 is stuck on depwait on geoclue-2.0
[06:19] <pitti> that's in universe
[07:10] <willcooke> morning all
[07:20] <larsu> hi willcooke!
[07:20] <willcooke> o/
[07:29] <pitti> hey willcooke, hey larsu
[07:29] <pitti> oh, is didrocks already on holidays in Japan?
[07:29] <willcooke> pitti, yup
[07:30] <willcooke> oh, pitti - I was talking with jpds about this yesterday:  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=33461
[07:31] <willcooke> pitti, are you going to be in DC?  Can we have a chat about it?
[07:31] <pitti> willcooke: yes and yes :)
[07:35] <darkxst> pitti, hey
[07:35] <larsu> hi pitti :)
[07:35] <darkxst> fix for that is in unapproved
[07:36] <willcooke> thx pitti
[07:36] <seb128> good morning desktopers
[07:36] <willcooke> hey seb128
[07:36] <pitti> bonjour seb128
[07:37] <pitti> seb128: http://ddebs.ubuntu.com/ubuntu-rtm/ FYI :)
[07:37] <seb128> pitti, thanks, Laney pointed that out yesterday
[07:41] <darkxst> pitti or seb128, can you bump g-s-d and g-c-c from unapproved?
[07:41] <seb128> bump?
[07:41] <pitti> darkxst: oh nice, thanks for fixing the geoclue issue
[07:42] <pitti> darkxst: so supposedly in V we want to drop geoclue and promote geoclue-2.0?
[07:43] <pitti> darkxst: formally I'm not allowed to accept the packages, but these are quite obvious, I'll do it
[07:44] <darkxst> pitti, that would be nice, but geoclue-2.0 drops the plugins and perhaps a few other bits.
[07:46] <seb128> pitti, you can wait some 15min for Laney to be on otherwise
[07:47] <darkxst> gnome-shell-pomodoro also need a no change rebuild
[07:48] <pitti> darkxst: for libgnome-desktop?
[07:49] <darkxst> pitti, yes
[07:49] <darkxst> its a gnome-shell extensions, but it actually has  a program that links against libgnome-desktop as well
[07:49] <pitti> darkxst: according to http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt quite a few more
[07:49] <pitti> like mailnag
[07:51] <pitti> darkxst: anyway, I'll upload these two
[07:51] <darkxst> pitti, mailnag is a python script
[07:51] <darkxst> ?
[07:52] <darkxst> quite a few of the things are blocked by g-s-d/u-s-d not being installable though
[07:52] <pitti> oh hmm, then it's uninstallable because of something else in between
[07:52] <pitti> yeah, let's wait for these two then
[07:53] <pitti> (pomodoro still building locally)
[07:53] <darkxst> Also I don't know why cinnamon deps on gnome-settings-daemon, when it has its own cinnamon-settings-daemon
[07:58] <seb128> they don't?
[07:59] <seb128> or likely a bug
[08:00] <darkxst> seb128, cinnamon package has a build-dep on gnome-settings-daemon
[08:00] <seb128> it might need the schemas for something?
[08:03] <Laney> hallo
[08:03] <larsu> hi Laney!
[08:03] <darkxst> seb128, its actually a binary-dep gnome-settings-daemon (>= 2.91.5.1), so they would not even get the schemas
[08:04] <darkxst> probably just left over from old packaging
[08:04] <seb128> remember, that package comes from Debian which doesn't split the schemas
[08:04] <darkxst> hey Laney
[08:04] <Laney> hey larsu ;-)
[08:04] <seb128> Laney, good morning, how are you?
[08:05] <Laney> gsd sure would get the schemas transitively, or else that would be pretty broken
[08:05] <Laney> seb128: good, although we didn't do very well at the pub quiz yesterday >:(
[08:05] <Laney> you?
[08:06] <Laney> darkxst: thanks for the fixes
[08:07] <seb128> I'm good thanks
[08:27] <darkxst> Laney, np
[08:31] <Laney> erm
[09:12] <Laney> looks like gnome-desktop3 just went in
[09:12] <seb128> nice
[09:12] <willcooke> \o/
[09:14] <larsu> neat
[09:39] <darkxst> great! thanks for the help pushing it through ;)
[09:49] <darkxst> Laney, pitti, seb128 ^
[09:49] <Laney> yw, thanks for the work too
[09:49] <Laney> enjoy the shiny(ish)
[09:50] <pitti> darkxst: thanks for your work!
[10:33] <Laney> Someone remind me how key grabbing is supposed to work for media keys in u-s-d?
[10:34] <Laney> I'm trying to debug my non-working keys and I see that we don't start the legacy keygrabber there
[10:34] <Laney> if I make it start then the keys work
[10:35] <Laney> I don't know why it worked before because this code path was the same in trusty
[10:44] <Laney> oh
[10:44] <Laney> it moved to Unity didn't it
[10:46] <darkxst> Laney, yes Unity grew its on keygrabber, however I though the legacy keygrabber was being kept in u-s-d?
[10:47] <Laney> not for Ubuntu sessions
[10:47] <darkxst> no for 'legacy' sessions like flashback
[10:47] <Laney> indeed
[10:48] <Laney> but my problem is in a unity session
[10:48] <Laney> so not the legacy code
[10:48] <darkxst> Laney, oh, no idea then, I thought you run some non-unity DE?
[10:48] <Laney> different machine
[10:48] <Laney> desktop is unity
[10:49] <Laney> darkxst: is it u-s-d -> WM keygrabber over dbus?
[10:51] <Laney> looks like it
[10:52] <darkxst> Laney, I am not sure how unity does it, but in GNOME, I think its the other way around
[10:54] <Laney> there's methods on org.gnome.Shell on the session bus to grab and ungrab
[11:03] <darkxst> Laney, yes, but I think the WM takes the grab before g-s-d knows about it
[11:05] <darkxst> though its been a while since I looked at that code
[11:08] <pitti> Sweetsha1k: "Jenkins Fixed - utopic-adt-libreoffice 301" -- wohoo!!
[11:08] <pitti> first time ever
[11:09] <pitti> (in utopic)
[11:09] <Laney> bad news, now you have to keep it passing :p
[11:10] <pitti> good news, now we automatically hold back new uploads that break LO!
[11:10] <pitti> Laney: *tsk*, you have a *lot* to learn about selling stuff :)
[11:11] <Sweetsha1k> pitti: \o/
[11:11] <Laney> :)
[11:11] <Laney> Trevinho: yo, how can I get unity to print out its LOG_DEBUG messages?
[11:12] <Sweetshark> the bad news are only half as bad once you take into account the good news.
[11:14] <Sweetshark> and hey: enabling mergedlibs completely b0rked LibreOffice base, but autopkgtests completed just fine still :/
[11:15] <Sweetshark> hohum, although this solves only half the problem as I assume its easier to make LibreOffice FTBFS with an update, than to break the deployed binaries.
[11:16] <Sweetshark> but yeah, good stuff.
[12:01] <Laney> aaaaaaaaaha
[12:02] <Laney> u-c-c bug, looking like
[12:02] <seb128> the keybinding one?
[12:03] <Laney> ya
[12:03] <seb128> it writes a buggy config?
[12:03] <Laney> possibly
[12:04] <seb128> it works if you use g-c-c?
[12:04] <seb128> or how did you get to the conclusion that it's u-c-c?
[12:05] <Laney> I can fix it up in gsettings to work
[12:17] <Laney> but...
[12:17] <Laney> gcc writes the same thing
[12:17]  * Laney checks if shell works
[12:18] <seb128> could be the compiz/unity parser being overstrict on the syntax?
[12:18] <seb128> what's the difference between the non working and your hand fixed version?
[12:50] <Trevinho> Laney: UNITY_LOG_SEVERITY="<root>error;unity.your.component=debug"
[12:50] <Trevinho> Laney: or just set everything to debug, but it's probably a mess with that
[12:50] <Trevinho> so better to set a proper filter
[13:55] <Laney> darkxst: I think you want to take https://git.gnome.org/browse/gnome-shell/commit?h=gnome-3-12&id=db497a2ecfccc8ad9284353826f32fc75ca78ecd into shell
[13:55] <Laney> media keys are broken now because you have the gsd half
[13:59] <dgadomski> hello everyone
[14:00] <dgadomski> Trevinho: regarding bug 1125442: what is the policy for adding config options? can I just add it to metadata/core.xml.in or should I do it via ubuntu-specific patch in debian/patches?
[14:00] <Trevinho> dgadomski: hi
[14:01] <Trevinho> dgadomski: no, just change the files... No patches needed
[14:02] <dgadomski> Trevinho: tks, I will make a merge request after testing this a bit
[14:02] <Laney> darkxst: oh, lolz, you already revert that
[14:04] <Trevinho> dgadomski: nice
[14:59] <Laney> okay now I'm inside compiz ...
[15:06] <seb128> Laney, nice!
[15:06] <Laney> NO
[15:16] <Trevinho> :)
[15:17] <seb128> Laney, I wonder if we should restore the gtk line wrapping hack before release, we said we might if there was still issues and we still have some
[15:17] <seb128> larsu, ^
[15:17] <larsu> do we still have issues?
[15:18] <seb128> we do
[15:18] <larsu> you mean the label < 640px thing, right?
[15:18] <larsu> seb128: a lot?
[15:18] <seb128> yes
[15:18] <seb128> not sure "a lot" I can see at least 3 cases regularly on my desktop with my limited use of UIs
[15:18] <seb128> 1-
[15:19] <Laney> can we patch them?
[15:19] <seb128> 1. go in nautilus in a folder with image, select a bunch, do right click -> properties
[15:19] <seb128> 2. gedit, open a new instance type something, open a tab, type something, try to close gedit
[15:19] <seb128> 3. the polkit dialogs
[15:20] <seb128> e.g trying to unlock the user settings panel
[15:20] <larsu> I'm guessing most of these will be fixed upstream already
[15:20] <larsu> so it doesn't make much sense for us to pull in all those patches
[15:20] <larsu> I sy let's put the gtk hack in and remove it right at the start of next cycle
[15:21] <seb128> Laney, we always can, but I assume that since it didn't happen until now it's not going to be done by magical way before freeze
[15:21]  * larsu prefers happy users in stable releases, and this is something we can easily spot
[15:21] <seb128> larsu, +1
[15:21] <Laney> who said magical?
[15:21] <Laney> but what evs, I don't mind
[15:21] <seb128> well, it didn't happen in a whole cycle, why would that change now?
[15:21] <larsu> I don't mind == +1, right?
[15:22] <Laney> ?!?!?!?!
[15:22] <larsu> :P
[15:22] <Laney> because we might decide to do the work?
[15:22] <seb128> if that was annoying people enough for them to do the work that would have happened
[15:22] <Laney> and I don't understand why having a fix upstream means we would be less likely to have a fix
[15:22] <seb128> I fixed a bunch
[15:22] <Laney> these arguments are weird to me
[15:23] <seb128> but it's just not high priority enough to spend day on those
[15:23] <seb128> days
[15:23] <seb128> Laney, well, my argument is that clearly it's not an itch people are wanting the scratch
[15:23] <seb128> so sure I could start assigning bugs and we can force some action to happen
[15:24] <seb128> but I don't think it's high enough importance to do that
[15:24] <larsu> Laney: we've fixed quite a few of those upstream. It's just that there are a lot of them (I hadn't seen any of the ones seb pointed to)
[15:24] <seb128> so I suggest we do the easy thing and put the workaround back and let people focus on their work
[15:24] <seb128> larsu, can you confirm those I described?
[15:26] <larsu> seb128: all except (3), because I don't know how to summon one of those
[15:26] <Laney> pkexec ls
[15:26] <seb128> larsu, as I wrote, go to settings->user and click "unlock"
[15:26] <larsu> seb128: yes.
[15:26] <seb128> k
[15:26] <larsu> I'm fine with fixing those before release, but I'm afraid there might be more of them
[15:28] <seb128> yeah, that was my issue as well
[15:28] <seb128> we clearly have such bugs
[15:28] <seb128> like I just listed a few ones that annoyed me
[15:28] <seb128> but I'm sure there are more
[15:28] <seb128> and since we didn't have action on those it's clearly something we didn't actively look at resolving
[15:31] <seb128> ok, another one
[15:31] <Laney> Actually I would support doing it before release if we actually fix ones we find
[15:32] <seb128> - software-properties, do a change, close it, the dialog to tell you to refresh the apt database
[15:32] <Laney> Refusing to fix easily resolvable bugs makes me kind of sad
[15:32] <seb128> Laney, I can't justify fixing those being higher priority that e.g touch rtm work
[15:32] <seb128> but if we have people who have nothing to do that is higher priority and want to do that, sure
[15:33] <larsu> seb128: let's start by making bugs to track that we need to do this?
[15:33] <larsu> that's better than just adding the workround
[15:33] <seb128> you want me to open bugs about each case and tag them?
[15:35] <seb128> Laney, well, it's not "refusing to fix bugs", it's just that adding back the hack to gtk doesn't create any issue and bring us to the same user visible state with less work
[15:35] <seb128> we are going to get those fixes over time with updates and sync from Debian
[15:35] <seb128> then we can drop the workaround and we overall spend less time on the issue to get at the same result
[15:36] <seb128> being proactive in backporting individual fixes to utopic doesn't give us any advantage
[16:51]  * willcooke going for some food
[18:12]  * willcooke -> EOD - g'night
[21:08] <robert_ancell> mterry, Do you happen to know what might be being updated for a user every 300s on the phone? bug 1376357
[21:10] <willcooke> qengho, still about?
[21:10] <qengho> willcooke: yep1
[21:10] <qengho> Only 1700 here.
[21:11] <willcooke> I know you like to start at like 0400 :)
[21:11] <qengho> Some days. Not today.
[21:11] <qengho> What's up?
[21:11] <willcooke> could you do me a favour and check and reply to my email before EOD
[21:11] <willcooke> I need your blessing before tomorrow my time
[21:12] <willcooke> sure it's already on your list, but just want to make sure that tomorrow is smooth :)
[21:13] <willcooke> also want to make sure you can access the gdoc
[21:13] <qengho> willcooke: looks good to me.
[21:13] <willcooke> qengho, sweet!  thanks man!
[21:13]  * willcooke goes back to work on more important things
[21:13] <willcooke> http://www.harbourbrewing.com/product/-india-pale-ale.php
[21:19] <willcooke> g'night