[06:12] <pitti> Good morning
[06:14] <larsu> morning pitti! Wie geht's?
[06:15] <pitti> larsu: prima, danke! und Dir?
[06:15] <larsu> auch. Nur müde
[06:15] <pitti> larsu: war zur Abwechslung mal ein Wochenende zuhause, sehr entspannt
[06:15] <larsu> ha schön!
[06:15] <pitti> larsu: nicht jeder Hacker steht um 7 auf...
[06:16] <larsu> pitti: stimmt, aber manche anscheinend schon ;)
[07:45] <seb128> good morning desktopers
[08:02] <mlankhorst> morning
[08:07] <seb128> hey mlankhorst
[08:09] <mlankhorst> what's up?
[08:12] <seb128> it's monday!
[08:13] <mlankhorst> indeed it is!
[08:36] <seb128> xnox, pitti, hey, what's the status of https://code.launchpad.net/~xnox/system-service/python3/+merge/192805 , seems like it was mostly approved and the review comment got addressed since? should that land? (and what about https://code.launchpad.net/~xnox/system-service/pac-support/+merge/243904 then?)
[08:36] <pitti> bonjour seb128, hey mlankhorst
[08:37] <seb128> pitti, hey, wie gehts? had a good w.e?
[08:38] <pitti> seb128: yeah, at home for a change -- very relaxing! :-) and your's? enjoyed valentine's day?
[08:39] <pitti> seb128: py3 merge> ah, I didn't see the followup comment
[08:39] <seb128> pitti, indeed I did! we had a nice w.e, went to saw a choir on friday, to the theatre on saturday and relaxed/enjoyed the sunny weather yesterday
[08:40] <seb128> to see*
[08:41] <Noskcaj> thanks for the sponsoring seb128
[08:41] <seb128> Noskcaj, hey, yw!
[08:42] <Noskcaj> Is there any reason we don't have yelp 3.14 yet? Did it break something?
[08:43] <happyaron> can someone sponsor this? https://code.launchpad.net/~nobuto/ubuntu/vivid/unzip/fallback-encoding/+merge/249644
[08:43] <happyaron> or should I subscribe sponsors team?
[08:48] <seb128> happyaron, it's already in the sponsoring queue
[08:49] <seb128> happyaron, I'm unsure about the change, why isn't that done upstream and/or in Debian?
[08:50] <happyaron> seb128: upstream want's universe solution instead of locale hack, for Debian I'd like to wait until freeze is over
[08:50] <seb128> why?
[08:51] <happyaron> for which?
[08:51] <seb128> things can be forwarded to the BTS/discussed during the freeze
[08:51] <seb128> Debian
[08:51] <happyaron> yes, but not done yet
[08:51] <seb128> right, it should ;-)
[08:51] <seb128> comment on the mp saying we at least need a bug report explaining the issue
[08:51] <seb128> so we have references on why we carry the change
[08:52] <happyaron> ok
[09:03] <willcooke> o/
[09:05] <Laney> morning!
[09:06] <happyaron> seb128: bug 1422290
[09:06] <happyaron> morning, :)
[09:07] <seb128> happyaron, thanks
[09:07] <seb128> hey willcooke, Laney, how is u.k this morning?
[09:07] <Laney> very wet
[09:07] <seb128> of course ;-)
[09:09] <Laney> seb128: good weekend?
[09:13] <seb128> excellent, thanks!
[09:13] <willcooke> :)
[09:13] <seb128> went to see a choir and to the theatre, enjoyed a sunny sunday as well
[09:17] <seb128> Laney, what about you? good w.e?
[09:20] <Laney> yep, had friends over for dinner on saturday & went climbing / played games yesterday
[09:20] <Laney> relaxing!
[09:27] <seb128> nice
[09:27] <seb128> Laney, pitti, can one of you sponsor http://paste.ubuntu.com/10253033/ for me?
[09:28] <seb128> I never receive an update on the Debian rt to replace my key, I wonder if they did it without getting back to me or if that's still waiting?
[09:29] <pitti> seb128: can do, yes
[09:29] <seb128> pitti, danke
[09:29] <Laney> ah, faster than me
[09:29] <pitti> seb128: hm, when I got my key replaced I did get a notification
[09:30] <Laney> I'm being killed by fstrim atm
[09:31] <pitti> seb128: ah, svn head has another change, I'll merge
[09:31] <seb128> ups
[09:31] <seb128> pitti, sorry about that
[09:31] <pitti> no worries
[09:31] <seb128> pitti, my most recent email on the rt to change key was gunnar asking if you could send again your email but inlined, did you do that?
[09:32] <seb128> inline-signed rather
[09:32] <pitti> yes, I thought I did
[09:32] <seb128> hum, k
[09:32] <pitti> seb128: I take the liberty to drop the wrong commas from the manpage
[09:32] <seb128> pitti, wfm :-)
[09:33] <pitti> seb128: given Debian's freeze, is that something you want to see in unstable now, i. e. do you want to send an unblock request?
[09:33] <pitti> seb128: or sohuld I upload it to exp, or only an svn snapshot to vivid?
[09:35] <seb128> pitti, no need to be in unstable no, it's just in the ubuntu sponsoring queue and I wanted to get it out of it
[09:35] <seb128> so exp sync or I can upload to vivid if you want
[09:35] <seb128> then we can sync on the next debian upload
[09:36] <pitti> seb128: I'd upload it as 0.7.6-2svn1
[09:36] <pitti> seb128: svn commit running for 2 mins now (alioth is clogged..)
[09:36] <seb128> pitti, feel free, or let me know if you want me to do that
[09:39] <pitti> seb128: I'll do it, after svn commit ever finishes..
[09:40] <seb128> pitti, danke, I nudged on the debian rt to know if I need to do anything for the key replacement still
[09:43] <Laney> pitti: let me know if/when you have time to debug suspend - I've tried pm-suspend 20 times or so without failure now so seems this method is working properly
[09:47] <pitti> Laney: ah, interesting; do you have anything in /var/cache/pm-utils?
[09:47] <pitti> like a last_known_working.quirkdb
[09:50] <Laney> pitti: nothing there, empty directory
[09:50] <Laney> I have a pm-suspend.log if that's interesting to you?
[09:51] <pitti> Laney: possibly; but I suppose one needs to enable debugging for it to actually say which quirks it does
[09:51] <Laney> is PM_DEBUG=true pm-suspend enough?
[09:51] <pitti> Laney: could be (I don't remember any more, sorry)
[09:52] <Laney> nod, let's see
[09:52] <pitti> /usr/share/doc/pm-utils/README.debugging:  PM_DEBUG="true" to have the script log each action as it performs it.
[09:52] <pitti> sounds good :)
[09:52] <Laney> one second
[09:52] <pitti> Laney: so you just did "sudo pm-suspend" 20 times?
[09:53] <pitti> Laney: i. e. without all the indicator/desktop integration/screen lock/etc. overhead?
[09:58] <Laney> pitti: indeed; I think those call suspend via logind now?
[09:58] <Laney> http://paste.ubuntu.com/10253345/ <- don't see any quirks there
[09:59] <pitti> Laney: right; could you do the same loop with just "echo mem | sudo tee /sys/power/state"?
[10:00] <Laney> ack
[10:00] <Laney> is this poking the kernel to suspend directly?
[10:04] <pitti> Laney: yes
[10:04] <pitti> Laney: that's essentially what pm-utils and logind do
[10:04] <pitti> but without the desktop overhead
[10:04] <pitti> Laney: I'm interested in whether any of the other pm-utils hooks make a difference here, as it's not the quirks
[10:04] <Laney> pitti: ok, 20 times it worked
[10:04] <pitti> seb128: libnotify uploaded
[10:04] <seb128> pitti, danke!
[10:05] <flexiondotorg_> Morning
[10:05] <flexiondotorg_> I noticed that gsettings is misbehaving, to some extent in 15.04.
[10:06] <flexiondotorg_> This is confirmed by the MATE maintainers in Fedora rawhide also.
[10:06] <flexiondotorg_> rawhide is glib2 2.43.4 and vivid is glib2 2.43.3
[10:07] <flexiondotorg_> Editing some gsettings key/value pairs in dconf-editor doesn't make the change immediately. Requires a log in/out for changes to be active.
[10:08] <flexiondotorg_> In MATE, some control center applets don't make a change until a log in/out. Such as Appearance and Sound themes, where changes are not applied directly.
[10:09] <seb128> flexiondotorg_, thanks, that's likely buggy code impacted by a glib change
[10:09] <flexiondotorg_> seb128, One sec...
[10:10] <seb128> flexiondotorg_, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
[10:10] <flexiondotorg_> seb128, I thought this commit looked "interesting" - https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
[10:10] <seb128> indeed
[10:10] <flexiondotorg_> 😁
[10:10] <flexiondotorg_> Yes. I was reading the commit log last night.
[10:10] <seb128> flexiondotorg_, typically your fix looks like https://git.gnome.org/browse/nautilus/commit/?id=c84f4e0039353e3846afda132a53d96fcadc0715
[10:10] <seb128> you need to connect first and then read the value
[10:11] <seb128> some code does it the other way around
[10:11] <flexiondotorg_> seb128, So, this is not a regression is glib2?
[10:11] <seb128> no
[10:12] <flexiondotorg_> seb128, This is a change to enforce the intended use?
[10:12] <seb128> it unfortunately making code that seemed to work stop working though
[10:12] <flexiondotorg_> seb128, Thanks. Useful feedback.
[10:12] <seb128> but the code was wrong before, it just happened to work
[10:12] <seb128> yw
[10:12] <flexiondotorg_> I'll progress this upstream.
[10:12] <flexiondotorg_> MATE upstream that is.
[10:12] <seb128> the goal was not to enforce the intended use just for the sake of doing that
[10:13] <seb128> but rather to fix a performance issue, explained in the glib commit you pointed
[10:13] <seb128> the side effect is that it does less work than before and make incorrect code stop working
[10:15] <seb128> pitti, debian rt guys said you didn't send the inline-signed email, fwded you their reply
[10:15] <seb128> in fact replying and Ccing you if you prefer?
[10:15] <seb128> so maybe you can resend it, in case it got lost?
[10:18] <pitti> seb128: ack
[10:20] <pitti> seb128: sent again (gosh, complicated!)
[10:23] <seb128> pitti, danke!
[10:29] <marga> xnox, your latest gnome-keyring upload is giving me pain again.
[10:30] <marga> xnox, do I need to change the upstart override that I had created before? (/etc/xdg/gnome-keyring.override containing manual)
[10:30] <xnox> marga: go on.
[10:31] <xnox> marga: yes.
[10:31] <marga> xnox,  how do I stop gnome-keyring from getting the ssh sock?
[10:31] <xnox> marga: instructions in the bug report. To kill gnome-keyring ssh agent, you can - GUI Open Startup Applications untick gnome-keyring-ssh
[10:32] <marga> heh, I want this globally, GUI is not a good solution...
[10:32] <xnox> marga: or use any of the xdg paths to override gnome-keyring-ssh (like in 12.04 and before)
[10:32] <xnox> which are in /etc
[10:32] <xnox> marga: or the name of the ovveride is now gnome-keyring-ssh.override
[10:32] <xnox> (upstart jobs')
[10:32] <marga> Ah
[10:33] <marga> So, instead of /etc/xdg/upstart/gnome-keyring.override containing manual, it should be /etc/xdg/upstart/gnome-keyring-ssh.override containing manual?
[10:33] <xnox> marga: you probably want to override gnome-keyring-gpg agent as well. Then one can use GPG subkeys on e.g. yubikey u2f neo ;-)
[10:33] <xnox> marga: yes.
[10:33] <marga> I only care about ssh
[10:33] <marga> Ok, thanks.
[10:35] <xnox> marga: instead of upstartish override, the desktopish override is supported as well now. `find /usr/share -name gnome-keyring-ssh.desktop`, cp that to /etc/xdg/autostart/gnome-keyring-ssh.desktop, echo X-GNOME-Autostart-enabled=false >> /etc/xdg/autostart/gnome-keyring-ssh.desktop .....
[10:36] <xnox> marga: that would be very forward looking, e.g. if we switch to systemd for user sessions in 16.04 the xdg/autostart override method will persist.
[10:36] <marga> ok
[10:36] <marga> I'll look into that then, thanks
[10:37] <marga> In the past, we used to actually remove that file from /etc/xdg/autostart
[10:37] <xnox> marga: that's the "system-wide" way to disable xdg-autostart files (and is the same action that startup applications thing does, but on user-level, into ~/.config/autostart)
[10:38] <xnox> marga: good point.
[10:39] <xnox> marga: in the upstart job, i didn't check for presence of the /etc/xdg/autostart/gnome-keyring-ssh.desktop, but rather for the "X-GNOME-Autostart-enabled=false" inside it.
[10:40] <marga> Right, I understand but it's a bit cumbersome that this keeps changing...
[10:40] <xnox> marga: another sru, but now to be compatible with good old ways to kill gnome-keyring-ssh?
[10:40] <marga> Anyway, I'll fix it, it's not such a big deal.
[10:40] <xnox> such that removal of /etc/xdg/autostart/gnome-keyring-ssh.desktop works once again ?! =)))))
[10:40] <xnox> marga: if only you would have told me that months ago =)
[10:40] <marga> heh :)
[10:41] <marga> You think it will work like that for systemd?
[10:41] <marga> Instead of removing files from /etc/xdg/autostart, we will modify them to say Autostart-enabled=false?
[10:41] <marga> (I have no idea how systemd works :)
[10:42] <xnox> yes. X-GNOME-Autostart-enabled=false is the best one - it will work for systemd, upstart, gnome-desktop, and all the other alternatives (e.g. forked mints, cinnamons, etc)
[10:42] <marga> ok, thanks again.
[10:43] <xnox> marga: systemd --user is not that capable at the moment, the plan will be similar to how systemd support init.d scripts. There will be a binary that will parse .desktop files in autostart paths, and generate systemd units to run.
[10:43] <xnox> there is code on github to do that already, which was part of demos that my current manager did back in the moblin/meego days
[11:54] <Laney> pitti: suspended 20 times using the logind dbus call...
[11:54] <Laney> ...maybe it's fixed
[11:54] <pitti> Laney: hm, my gut feeling is rather that the bits around it (screen saver, etc.) change this
[11:55] <pitti> Laney: unless it was fixed in the kernel itself; I kinda hoped it would turn up with the mem > /sys/power/state test
[11:55] <larsu> pitti: still not seeing any entries in the journal unless I'm root (or in the systemd-journal group). Is there a bug tracking tha issue?
[11:55] <larsu> *that
[11:55] <Laney> last thing is to try with an actual lid close
[11:56] <pitti> larsu: debian bug 771980
[11:56] <larsu> pitti: thanks1
[11:56] <pitti> larsu: it's fixed in upstream master (i. e. 219), but as that probably won't get released this week, I'll add a little hack to it (easier than backporting the large patches for generic ACL support in tmpfiles)
[11:57] <larsu> pitti: it's not urgent. I just wanted to know the status. I'm fine with adding myself to systemd-journal for now
[12:00] <Laney> hmm
[12:00] <Laney> now I'm in some differently borked state where lid suspend doesn't suspend at all (screen stays on)
[12:01] <Laney> ...and after I say that, it works again /o\
[12:06] <pitti> some inhibitor? (systemd-inhibit)
[12:07] <Laney> Just looks like normal stuff
[12:07] <Laney> maybe there's a timeout or so preventing you suspending again too fast
[12:08] <Laney> or one of these inhibitors does that
[12:08] <Laney> anyway I've lid closed 15 times now without error
[12:08] <davmor2> Laney: that or it just hates you ;)
[12:08] <Laney> of course the system knows I'm trying to reproduce a bug and I'm not putting the laptop in my bag for a few hours, so it would work. :)
[12:09] <Laney> davmor2: I feel like a QA engineer atm ;-)
[12:10] <davmor2> Laney: Welcome to our world of machines hating you :)
[12:16] <mitya57> #endmeeting
[12:17]  * Laney peers at mitya57 
[12:18] <Laney> are we still meeting?
[12:18] <mitya57> I just thought that having "Desktop Weekly Meeting 2015-02-10 | Current topic: endmeeting" in topic is not sane
[12:18] <Laney> haha
[12:18] <Laney> willcooke: care to #endmeeting ?
[12:20] <willcooke> #endmeeting
[12:20] <meetingology> Meeting ended Mon Feb 16 12:20:17 2015 UTC.
[12:20] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2015/ubuntu-desktop.2015-02-10-15.32.moin.txt
[12:20] <willcooke> oops
[12:23] <larsu> Laney: we decided not to take gtk 3.16, right? Can you please downgrade the one in the destkop ppa?
[12:23] <Laney> larsu: I deleted it from there
[12:23]  * larsu is confused
[12:23] <larsu> Laney: thanks anyway
[12:23] <Laney> you'll have to manually downgrade though, apt won't do that for you
[12:23] <larsu> I thought I did... but got 3.16 again in the last upgrade
[12:24]  * larsu could have checked...
[12:24] <Laney> apt-cache policy libgtk-3-0 ?
[12:25] <larsu> ya, that shows 3.16
[12:25] <Laney> it should show you where it comes from
[12:26] <Laney> in the "Version table:"
[12:26] <larsu> right, /var/lib/dpkg/status
[12:26] <larsu> so ...  local?
[12:26] <Laney> so apt doesn't know about any sources which have it any more ...
[12:27] <Laney> try to downgrade it and see if Candidate: is still 3.15 after that
[12:29] <larsu> ugh, wants to uninstall all the things
[12:30] <larsu> I guess in addition to -dbg, -dev, -common, -bin I also need to downgrade gail?
[12:30] <Laney> ya you probably have to add libgtk-3-bin libgtk-3-common (at least) too
[12:30] <larsu> still not enough
[12:31] <Laney> add the name of one of the packages it wants to remove (possibly repeatedly) and you'll get to the problem after a few iterations
[12:31] <larsu> all of them?
[12:31] <larsu> it's ~80 packages
[12:31] <Laney> (that, or use aptitude and say 'no' until it gives you just the downgrades)
[12:31] <Laney> just one should be enough
[12:32] <larsu> Laney: ah thanks (was missing gir)
[12:32] <larsu> neat trick
[12:33] <Laney> it's "please keep this installed"
[12:34] <Laney> then apt says "umm, I can't, because of this"
[12:34] <larsu> right
[12:34] <larsu> makes sense
[13:02] <seb128> hum, new qt landed
[13:02] <seb128> Laney, you still plan to restore a working storage? I didn't look at what Mirv uploaded yet but I think it's incomplete
[13:02] <Laney> bleh
[13:03] <Laney> I think he was going to turn off the page
[13:11] <Laney> let me look, might be best to copy in the function or some of it for now :/
[13:14] <flexiondotorg_> seb128, Regarding https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
[13:15] <flexiondotorg_> I see alot of python2 applications using Gio.Settings that are going to be affected.
[13:16] <larsu> flexiondotorg_: and all of them have a bug that is very easy to fix
[13:20] <flexiondotorg_> larsu, I would say they all have a regression that is fixable.
[13:20] <flexiondotorg_> An easy fix, man hundreds of times, is not so easy though.
[13:20] <flexiondotorg_> *many
[13:21] <larsu> hundreds of times?
[13:22] <larsu> can you point me too all of those apps?
[13:23] <flexiondotorg_> No, not all. I haven't review everything available. I'm just trying to access the scope of the issue.
[13:23] <larsu> how can you know that it's 100s of apps then?
[13:24] <larsu> and like I said, those apps have a legitimate bug which is now surfacing because of the gsettings change
[13:24] <flexiondotorg_> Because of cultural practices.
[13:24] <larsu> cultural practices?
[13:25] <flexiondotorg_> larsu, I am not disagreeing. I understand that previously stuff worked even though it was incorrectly implemented.
[13:58] <Mirv> Laney: the page is off now in the archive version, but with your wip branch integrated so that the storage line is there with the free space shown
[14:01] <Mirv> I've fake-synced to trunk so that train continues to work, but I've not pushed the actual changes (= your work-in-progress branch with my fixes, added with commenting out the three lines so that storage.qml is not loaded)
[14:17] <flexiondotorg_> larsu, dconf-editor is affected for example.
[14:22] <larsu> flexiondotorg_: how so? dconf-editor.vala never listens to change signals and nothing else uses the GSettings API
[14:24] <flexiondotorg_> larsu, Right, understood. So if I am tweaking settings with dconf-editor it is the application that is at fault if those changes are not reflected directly?
[14:27] <larsu> flexiondotorg_: yes. The application needs to connect to the change signal before reading the first value
[14:28] <flexiondotorg_> larsu, Yes, understood.
[14:30] <desrt> bonan lundon, ubuntanoj
[14:32] <mitya57> desrt: labas pirmadienis
[14:32]  * desrt ne parolas litovan lingvon
[14:33] <desrt> sed, saluton!
[14:39] <pitti> desrt: Hej, kiel vi fartas ?
[14:40] <desrt> pitti: bone.  preskaŭ sane, denove :)  kaj vi?
[14:40] <pitti> desrt: very well, thanks! survived the flu?
[14:40] <desrt> yup... lingering annoying dry cough, though
[14:41] <desrt> and never really had 'the flu' proper, i think
[14:44] <desrt> it's also starting to get warmer again... up to -18°
[15:17] <willcooke> desrt, anyone ->  Can someone provide me with the minimum working metacity config.
[15:17] <willcooke> What are the absolute min. packages I have to install to get it to work
[15:17] <willcooke> On the phone it's just giving me a grey screen and no applications are visible
[15:18] <willcooke> mlankhorst has been playing as well, and we think we're missing a couple of packages
[15:19] <desrt> willcooke: you'd probably want something like gnome-panel in there...
[15:19] <desrt> if you're looking for minimalism, maybe xfce is a better bet?
[15:19] <desrt> at least it's theoretically maintained
[15:43] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1422404
[15:43] <seb128> just as a fyi
[15:44] <Laney> hehe
[15:44] <Laney> do you want to learn how to fix those? ;-)
[15:44] <seb128> no, thanks ;-)
[15:44] <seb128> well, I know how to fix those
[15:44] <seb128> can have a look to this one tomorrow if you want
[15:45] <Laney> nah
[15:45] <Laney> I already submitted a bug upstream, just need to add another case to it
[15:47] <seb128> k
[15:48] <Laney> I found another one
[15:48] <Laney> right click a directory -> properties -> permissions -> change permissions...
[15:48] <Laney> BAH!
[15:49] <seb128> oh, yeah, indeed
[15:49] <Laney> I didn't grep for GTK_DIALOG_USE_HEADER_BAR when doing the patching before
[15:49] <Laney> that's one other way to make them
[15:49] <Laney> gtk_dialog_new_with_buttons
[15:50] <ochosi> by the way, we discovered a teeny-weeny problem with the no-headerbar patch in evince under xubuntu (patch attached): https://launchpad.net/bugs/1422354
[15:59] <larsu> ochosi: just remove the call altogether
[15:59] <larsu> default is to not hide the titlebar when maximized
[15:59] <larsu> and please submit upstream
[16:05] <ochosi> larsu: ok, will do!
[16:06] <ochosi> oh, you have push-rights to evince upstream..? :)
[16:07] <larsu> yes, but one of the maintainers will have to give the ok
[16:07] <ochosi> sure
[16:07] <ochosi> was just (positively) surprised is all
[16:07] <larsu> ochosi: gnome commit rights are all-or-nothing
[16:08] <larsu> and then people behave by not stepping on other maintainer's toes
[16:08] <larsu> (mostly)
[16:08]  * Laney coughs
[16:08] <larsu> Laney: that paren was for me :)
[16:08] <Laney> :D
[16:10] <mitya57> Guys look what I have: http://people.ubuntu.com/~mitya57/csd-window-buttons.png
[16:11] <mitya57> (that is thanks to recent gtk commit that added separate css classes for each decoration button)
[16:11] <larsu> mitya57: you'ee welcome
[16:11] <larsu> mitya57: thanks for making this btw
[16:11] <Laney> nice!
[16:12]  * larsu will gladly review patches to ubuntu-themes
[16:12] <Laney> does it just use the same icons as ssd buttons?
[16:12] <Laney> can we get that commit into gtk-3-14? ;-)
[16:12] <larsu> Laney: it just sets some classes. Backport should be trivial
[16:12] <Laney> indeed
[16:12] <larsu> I hesitate to put it upstream though
[16:13] <mitya57> Laney: yes, I can upload gtk with that cherry-picked right now
[16:13] <Laney> already is no?
[16:13] <Laney> mitya57: I mean upstream
[16:13] <Laney> at least first
[16:13] <larsu> Laney: upstream 314
[16:13] <Laney> how come?
[16:13] <ochosi> larsu: upstreamed: https://bugzilla.gnome.org/show_bug.cgi?id=744601
[16:14] <mitya57> It uses the same icons, I had to make a symlink assets-csd -> ../metacity-1/
[16:14] <mitya57> Now I need to figure out how to remove the space between icons
[16:16] <larsu> ochosi: cool thanks! Ping me if this doesn't get an answer in a couple of days
[16:16] <larsu> Laney: was the "how come?" for me?
[16:17] <Laney> yep
[16:17] <ochosi> larsu: okeydokey, will do! and thanks for pointing me upstream, it's good practice and i guess i should do that more often...
[16:17] <larsu> Laney: because adding style classes is kind of like adding API, and I generally dislike doing that on stable series
[16:17] <larsu> ochosi: indeed ;)
[16:18] <larsu> Laney: would it help us that much to have it upstream? It's just one more _git patch, right?
[16:18]  * larsu can ask to get it into 3.14 if Laney really wants it
[16:19] <Laney> It's okay, if that's the policy then you're right
[16:19] <Laney> I just like to avoid one more patch if possible :)
[16:19] <larsu> in fairness, gtk has been really bad about that in the past
[16:19] <larsu> I'm trying to make it better though
[16:19] <larsu> Laney: understandable
[19:15] <Noskcaj> Laney, Are you going to upload evolution 3.12.10 before FF?
[19:17] <seb128> Noskcaj, that update is a simple stable one, feature freeze has nothing to do with those
[19:18] <Noskcaj> ok
[19:23] <Noskcaj> seb128, Do we want libgweather 3.15.90? Adds one symbol and updates the docs and translations
[19:24] <seb128> Noskcaj, no idea, I personnal don't want it, but feel free to update/find a sponsor if you think it's worth it
[19:25] <Noskcaj> I'd like to get the fixed docs included, so i'll put in in the sponsor queue
[19:25] <Noskcaj> Are there any 3.15 components we want?
[19:26] <Noskcaj> e.g. gitg 3.15.1 is needed to get a lib update so kde's kate works properly
[19:54] <willcooke> hey robert_ancell
[19:55] <robert_ancell> willcooke, hello
[19:55] <willcooke> how goes Tuesday?
[19:55] <robert_ancell> It's fulfilling all my Tuesday expectations at the moment.
[19:56] <willcooke> :D
[20:26] <willcooke> http://s2.quickmeme.com/img/4c/4c75cbec1123992e21f971d451fbc67bd8ca94891a41db540b9e205efdc4d6d0.jpg
[20:26] <willcooke> I don't need no stinking Window Manager!
[20:27] <willcooke> I'll make my own out of xdotool and bash script
[20:27] <willcooke> \o/
[20:27] <willcooke> Full screen Xmir apps
[20:29] <willcooke> hrm.  Staged -> WIndowed = seg fault.
[20:29] <willcooke> Not so clever after all
[20:33] <willcooke> right enough for today I think
[20:33] <willcooke> g/night
[20:34] <robert_ancell> If I had a dollar for every time I've heard that - " I don't need no stinking Window Manager! I'll make my own..."
[20:39] <cyphermox> hehe
[22:49] <robert_ancell> TheMuso, does /usr/lib/at-spi2-core/at-spi-bus-launcher expect gnome-settings-daemon / unity-settings-daemon to exist / be ready?
[23:08] <TheMuso> robert_ancell: I don't know.