[04:33] <pitti> Good morning
[07:20] <willcooke> morning folks
[07:20] <willcooke> hey TheMuso
[07:21] <TheMuso> Hey willcooke.
[07:50] <seb128> good morning desktopers
[07:56] <willcooke> morning seb128
[07:56] <willcooke> seb128, would you have time to help me with the what's new in 14.10 list today?
[07:56] <willcooke> or tomorrow is fine
[07:56] <willcooke> or just a short list via email
[07:56] <willcooke> whatevs
[07:56] <willcooke> I just don't want to be scratching around at the last minute on Monday night :)
[07:57] <willcooke> I found the blueprints for 14.10 - but not a whole lot to go on there
[07:57] <seb128> willcooke, hey, I just replied to your email
[07:57] <willcooke> oh
[07:57] <willcooke> wow
[07:57] <willcooke> thanks
[07:57] <seb128> willcooke, you are not going to like the reply much though
[07:57] <willcooke> ha
[07:57] <seb128> reality is that we don't have much that changed enough to be marketing material
[07:57] <willcooke> nah - that reply is good
[07:58] <willcooke> that's what I thought would be the caase
[07:58] <willcooke> *case
[07:58] <seb128> we basically iterated over what we have, some updates, bugfixing, polish
[07:58] <willcooke> so now it's confirmed I can get on with it
[07:58] <seb128> lot of touch work
[07:58] <willcooke> yeah
[07:58] <seb128> we did some updates like gtk, some GNOME components/apps
[07:58] <seb128> but nothing of that is significant enough/user visible enough for a marketing page
[07:59] <seb128> "continuing improving hidpi support" could be one item
[08:06] <Laney> hey
[08:07] <seb128> Laney, good morning, wie gehts?
[08:08] <larsu_> hi Laney!
[08:08] <larsu_> oh, I'm named weirdly
[08:08] <Laney> keep it, it makes you look important
[08:09] <Laney> it's going well thanks, had a board games night last night
[08:09] <Laney> we didn't defeat wu feng, BUT!
[08:09] <Laney> realised that every time we played that game we've played this one rule wrong which makes it way harder than it should be
[08:09] <Laney> so next time he's going down
[08:10] <willcooke> thx seb
[08:11] <Laney> what's up larsu et seb128 et willcooke?
[08:11] <willcooke> it's all going on today
[08:11] <seb128> Laney, what game is that?
[08:11] <Laney> it's called Ghost Stories
[08:11] <Laney> and it's by a french guy!
[08:11] <seb128> haha
[08:12] <seb128> http://www.amazon.com/Asmodee-5511826-Ghost-Stories/dp/B001J77UUQ
[08:13] <Laney> that's it
[08:13] <seb128> it has good reviews
[08:13] <larsu> Laney: not much, feeling unimportant now that you mentioned it
[08:13] <larsu> Laney: I'm off for a short vacation at the baltic sea after today
[08:13] <Laney> yeah it's a fun game
[08:14] <Laney> larsu: why unimportant? :(
[08:14] <Laney> I saw there's a public holiday in .de tomorrow
[08:14] <Laney> Tag der Deutschen Einheit!
[08:15] <seb128> not important because he lost the tail after his nick?
[08:15] <larsu> Laney: "keep it, it makes you look important"
[08:15] <larsu> Laney: yep, gives us a nice long weekend :)
[08:15] <Laney> ah, forgot about that already :p
[08:15] <Laney> you're always important to me ♥
[08:15] <seb128> oh, speaking about long w.e
[08:15] <larsu> Laney:  :)
[08:15]  * seb128 needs to put a vac day on monday
[08:15] <Laney> ;)
[08:15] <seb128> lol
[08:16]  * willcooke prepares his REJECT button
[08:16] <Laney> hmm
[08:16]  * seb128 walks out and let Laney and larsu together
[08:16] <Laney> I've got some bug in the last day
[08:16] <Laney> where my background doesn't load properly like 50% of the time
[08:16] <Laney> http://people.canonical.com/~laney/weird-things/what.png
[08:16] <larsu> I love that url...
[08:16] <Laney> also do I normally have those icons?
[08:17] <larsu> Laney: there's supposed to be a bg image?
[08:17] <seb128> hum
[08:17] <Laney> yes
[08:17] <Laney> I don't even know what that gradient is
[08:17] <larsu> Laney: text shadow on the icons is wrong
[08:17] <seb128> it's like nautilus was failing to read its config
[08:17] <larsu> ya
[08:17] <Laney> happens loads
[08:17] <larsu> Laney: you can set a gradient in bg settings
[08:17] <seb128> do yo have anything wrong in the logs?
[08:17] <larsu> Laney: in GNOME...
[08:17] <Laney> I was ignoring it yesterday because I was logging in all the time to fix that unity bug
[08:17] <seb128> larsu, in unity as well
[08:18] <larsu> seb128: ah, in the combo box
[08:18]  * larsu didn't see that at first
[08:20] <seb128> well, wrong bg + icons displayed when they should ... looks like to me that nautilus is not reading the correct gsettings config or something
[08:20] <Laney> running nautilus doesn't bring it back
[08:20] <seb128> well
[08:20] <seb128> oh
[08:20] <seb128> OH
[08:21] <larsu> is the file in org.gnome.desktop.background.picture-uri correct?
[08:21] <seb128> what is handling your desktop?
[08:21] <seb128> click on one of those icons
[08:21] <seb128> and do help->about
[08:21] <seb128> I bet it's one of the nautilus fork you installed
[08:21] <seb128> like the cinnamon one
[08:21] <seb128> or nemo
[08:21] <Laney> oh
[08:21] <Laney> does that happen?
[08:21] <seb128> yes
[08:21] <Laney> wtf
[08:21] <seb128> and the first to start wins the desktop
[08:21] <Laney> WTF!
[08:21] <Laney> I did install the MATE one
[08:22] <seb128> there you go
[08:22] <Laney> yeah that's totally running
[08:22] <Laney> this seems a bit shitty (how surprising)
[08:22] <seb128> and it's starting before nautilus half of the time
[08:22] <larsu> sigh
[08:23] <Laney> how do these things get started again?
[08:23] <seb128> /etc/xdf/autostart
[08:23] <seb128> xdg even
[08:23] <Laney> okay, I'll file a bug on caja to fix its file
[08:24] <seb128> to be OnlyShowIn?
[08:24] <Laney> yep
[08:24] <seb128> right, makes sense
[08:24] <larsu> caja is their name for the nautilus fork?
[08:25] <Laney> it is
[08:25] <seb128> yet another nautilus fork :/
[08:25] <seb128> couldn't those guys work together on e.g nemo?
[08:25] <larsu> the old "can't we work together" argument never worked
[08:26] <larsu> seb128: when are we switching? :P
[08:26] <seb128> larsu, to which one? ;-)
[08:26] <seb128> we should try one every cycle!
[08:27] <Laney> midnight commander
[08:27] <larsu> seb128: lol!
[08:27] <larsu> Laney: ts ts
[08:27] <seb128> larsu, hum, theme weirdness that might be new to your recent changes/landing
[08:28] <seb128> larsu, in gedit, the "search" box (the one you get with ctrl-f) has its borders transparents, I don't think it did before
[08:29] <seb128> which is not specific to o-s for once
[08:31] <larsu> uh oh
[08:32] <larsu> seb128: white bg for me - I guess it's supposed to be @theme_bg?
[08:32] <seb128> shrug
[08:32] <seb128> I wonder why it's buggy for me :-(
[08:32] <seb128> I don't know, it used to be white for me as well
[08:32] <larsu> AH!
[08:32] <larsu> it's transparent for me as well
[08:33] <larsu> I wonder what changed that...
[08:34] <seb128> you just said it was white?
[08:34] <larsu> yes, because the text view is white as well
[08:34] <larsu> putting some text there showed me it's actually transparent
[08:44] <seb128> larsu, oh, I saw it easy because I oped a new document at the first line was selected/with a grey bg for me
[08:44] <seb128> I've also the 80 columns margin displayed
[08:45] <larsu> seb128: this is what I'm using for testing now :)
[08:45] <seb128> :-)
[08:46] <larsu> oh, that was easy
[08:48] <larsu> seb128: @theme_base_color is not defined in our themes (it's just called @base_color)
[08:48] <seb128> but some software use that name?
[08:48] <larsu> seb128: got copied in with the latest gedit-specific tweaks in apps/gedit.css
[08:48] <larsu> I'll MR after some more testing
[08:49] <larsu> ah, there's more @theme_*
[08:49] <seb128> larsu, danke
[08:52] <seb128> larsu, can you look at https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1376432 as well?
[08:53] <larsu> ya
[08:53] <seb128> danke
[08:57] <larsu> seb128: https://code.launchpad.net/~larsu/ubuntu-themes/fix-gedit/+merge/236830
[08:58] <seb128> larsu, wfm, but if apps/other themes use e.g @theme_base_color, would it make sense to define that variable in our theme?
[08:59] <larsu> seb128: we've always called it @base_color in our theme. Not sure if we'd break anything if we went with Adwaita's definitions now
[08:59] <seb128> larsu, can't we add an alias?
[08:59] <seb128> just @theme_base_color pointing to @base_color
[08:59] <seb128> so both would work?
[08:59] <larsu> I'd rather not, there's quite a few of those
[08:59] <larsu> see colors.css
[08:59] <seb128> k
[08:59] <seb128> wfm in any case, thanks
[08:59] <larsu> sorry, gtk-main.css
[09:00] <larsu> seb128: in general we discourage applications from reusing variables from the theme
[09:00] <larsu> instead, they should just give their widgets the right classes
[09:00] <larsu> i.e, ".background" in this case
[09:01] <seb128> k
[09:25] <seb128> bah, GNOME bugzilla is slooow
[09:25] <larsu> ya :/
[09:26] <Laney> hosted by RH not Canonical ;-)
[09:53] <seb128> pitti, hey
[09:55] <seb128> pitti, https://launchpad.net/ubuntu/+source/language-pack-touch-fr doesn't include indicator-sound.mo anymore, do you know why?
[09:57] <pitti> hey seb128
[10:00] <pitti> seb128: there's indeed no trace of it, but it didn't disappear in the last upload
[10:01] <pitti> http://launchpadlibrarian.net/185102146/language-pack-touch-fr_1%3A14.10%2B20140909_1%3A14.10%2B20140916.diff.gz
[10:01] <pitti> it disappeared here
[10:01] <seb128> pitti, it's in the current rtm image
[10:01] <pitti> yes
[10:01] <seb128> pitti, said differently "please don't copy those updates to rtm" :-)
[10:01] <pitti> no, I stopped doing that, we now build RTM specifig langpacks
[10:01] <pitti> there should be an update todya
[10:02] <Laney> I wonder if that glib ever went in
[10:02] <seb128> Laney, speaking of glib, should be sync the stable version from Debian?
[10:02] <seb128> Laney, https://launchpad.net/ubuntu-rtm/+source/glib2.0 looks like it didn't :/
[10:03] <Laney> yeah I was waiting because desrt said he was going to do a new stable without property deprecation warnings and removing the mutex abort
[10:03] <Laney> but that didn't come yet so maybe we should take this one
[10:03] <seb128> Laney, https://git.gnome.org/browse/glib/commit/?h=glib-2-42&id=b12bd1c3dcfbb398d2462dcf584a1f6d5173ca9a
[10:03] <seb128> we can at least backport that one if we want
[10:04] <Laney> there should be a release
[10:04] <seb128> k
[10:04] <Laney> let's see what he says later, can decide then
[10:04] <seb128> the mutex things is going to be removed?
[10:04] <Laney> just the abort I think
[10:04] <seb128> or asked differently, do we need to backport https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606
[10:04] <Laney> the glib fix would have the same effect
[10:04] <seb128> desrt, ^
[10:04] <seb128> k
[10:05] <seb128> if we are sure we are getting the glib change let's not backport the gtk one then
[10:05] <Laney> that gtk one is kind of a hack/workaround
[10:06] <seb128> right, but that's better than nothing
[10:06] <seb128> well if glib stop aborting even better
[10:07] <Laney> yes
[10:07] <pitti> seb128: so, I have not the slightest idea; the logs are already gone as we had two more updates after that
[10:09] <pitti> seb128: the next automatic update will fix it again
[10:09] <pitti> (I restored the files)
[10:09] <seb128> pitti, danke
[10:23] <Laney> so good having media keys back
[10:23] <Laney> I was actually getting used to scroll wheeling on the indicator
[10:24] <Laney> we didn't fix the direction of scroll wheel scrolling in u-c-c -> sound?
[10:24] <seb128> larsu looked at it but couldn't reproduce
[10:25] <seb128> seems to depend of the type of pointing device in use
[10:25] <Laney> didn't the indicator have it before?
[10:25] <Laney> because that's right for me now
[10:26] <seb128> yeah, not sure what's the difference :/
[10:26] <seb128> it's buggy on most u-c-c sliders for me
[10:26] <seb128> like the keyboard repetitions, a11y, etc as well
[10:27] <larsu> seb128, Laney: gtk slider scroll direction is different from all sound sliders
[10:27] <Laney> same
[10:27] <larsu> afaik
[10:27] <Laney> you mean u-c-c overrides it to be the other way?
[10:27] <larsu> only for the sound slider, yes
[10:27] <Laney> well, seb128 just pointed out that other panels have this too
[10:28] <Laney> it's backwards for the touchpad on my laptop as well
[10:28]  * larsu is confused
[10:28] <Laney> two finger scrolling
[10:29] <larsu> indeed, two finger scrolling is the opposite direction
[10:30] <larsu> Laney: xev shows me that different buttons get activated...
[10:30] <larsu> ah, natural scrolling only affects two-finger scroll on the touchpad, not the scroll wheel one
[10:31] <larsu> Laney: if you turn natural scrolling off, is it consistent?
[10:31] <seb128> I don't have that setting on
[10:32] <Laney> me neither
[10:32] <seb128> still sound is the wrong way around
[10:32] <seb128> scroll up make it go lower
[10:32] <larsu> okay there are two issues here:
[10:32] <larsu> (1) the sound sliders react in the opposite way from all other sliders on the system
[10:32] <larsu> (2) when natural scrolling is turned on, two-finger scroll behaves in the opposite way from scroll wheel scroll
[10:33] <larsu> seb128: for me, it's the other way around. Which buttons does xev report for scroll up/down?
[10:33] <seb128> (3) the sound slider in u-c-c doesn't react the right way
[10:33] <larsu> seb128: this is (1), no?
[10:33] <seb128> no
[10:33] <seb128> for me it reacts the same way as the other sliders
[10:34] <seb128> the keyboard panel ones in u-c-c do the same
[10:34] <seb128> the a11y ones as well
[10:34] <Laney> they are all backwards in u-c-c for me
[10:34] <seb128> same here
[10:34] <seb128> scroll up xev button 4
[10:34] <seb128> down button 5
[10:34] <larsu> why do I see a difference then?
[10:34] <seb128> good question
[10:34] <seb128> I'm using an usb mouse
[10:34] <seb128> with a wheel
[10:35] <larsu> same for me, up 4, down 5 on the trackpoint and two-finger scroll
[10:35] <larsu> (without natural scrolling)
[10:35] <larsu> sound slider in u-c-c is up/forward, every other slider is up/backwards
[10:36] <seb128> k, for me sound is the same as every other slider
[10:36] <larsu> seb128: maybe you have the mate control center installed?
[10:36] <larsu> I'll look into it
[10:36]  * seb128 slaps larsu with a trout 
[10:36] <Laney> haha
[10:36] <Laney> what's the gtk3 widget factory thing called?
[10:36] <seb128> gtk3-widget-factory
[10:36] <larsu> lol
[10:37] <Laney> oh yeah
[10:37] <Laney> wow
[10:37] <Laney> that has screwed up theming .......
[10:37] <seb128> those behave the same as u-c-c sliders
[10:37] <seb128> up = move to the left
[10:37] <larsu> Laney: hm?
[10:37] <Laney> transparent background
[10:37] <larsu> Laney: apart from non-resizable window and no shadow, it should be fine
[10:38] <Laney> but indeed it is also backwards
[10:38] <seb128> Laney, bug #1285783 might be the same
[10:38] <seb128> there is a fix there we forgot to land :/
[10:38] <seb128> want to test it?
[10:39] <Laney> kay
[10:39] <larsu> wfm
[10:39] <Laney> did he fwd it?
[10:40] <larsu> but I seem to be running a different os from you guys :/
[10:40] <Laney> are you using the archive gtk?
[10:40] <larsu> yes
[10:41] <seb128> larsu, do you have all the sound panels doing right on up?
[10:41] <seb128> like the one from the effects tab as well?
[10:41] <Laney> http://people.canonical.com/~laney/weird-things/wowzers.png
[10:41] <seb128> Laney, https://git.gnome.org/browse/gtk+/commit/?id=02ccfb5d62430590b11b2d3e34b6100e4a6ddcda
[10:41] <larsu> seb128: yes, all the sound sliders go right on up
[10:42] <Laney> thanks, I'll try the upstream one
[10:42] <seb128> Laney, yeah, better, the upstream bug states that the downstream one had an issue
[10:42] <seb128> thanks
[10:43] <larsu> Laney: ah, o-s
[10:43] <seb128> larsu, k, I don't understand what's different between our setups :/
[10:43]  * larsu reproduces
[10:43] <larsu> we should just drop those
[10:43]  * larsu runs
[10:43] <larsu> (again)
[10:43] <Laney> 15.04 man
[10:44] <Laney> I need a bigger SSD so I don't have to delete checkouts all the time
[10:45] <Laney> or git could grow a "give me this commit from this remote as a .patch" command ...
[10:47] <larsu> cgit does that...
[10:48] <Laney> or that could give you it with a nice filename, indeed
[10:51] <seb128> bah
[10:51] <seb128> I don't understand why https://launchpadlibrarian.net/184385786/buildlog_ubuntu-utopic-i386.evolution-data-server_3.12.6-0ubuntu2_UPLOADING.txt.gz has its translations in "list-missing"
[10:51] <seb128> they are installed in debian/tmp
[10:51] <seb128> (from the log)
[10:52] <seb128> e-d-s-common.install lists the directory
[10:54] <seb128> or that's pkgstriptranslations
[10:54] <seb128> but then I don't get why the .mo don't show up on https://translations.launchpad.net/ubuntu/utopic/+source/evolution-data-server/+imports?field.filter_status=all&field.filter_extension=all
[10:54] <seb128> pitti, ^ do you have any idea?
[10:55] <seb128> it makes https://translations.launchpad.net/ubuntu/utopic/+source/evolution-data-server show 3.12 as untranslated
[10:55] <seb128> hum, maybe I should have accepted that template as "evolution-data-server" rather than -3.12?
[10:56] <seb128> where is dpm when have launchpad translation questions? :-)
[11:01] <Laney> seb128: that patch doesn't fix the widget factory
[11:03] <davmor2> seb128: wisely hiding as you have launchpad translation questions?
[11:15] <seb128> Laney, not even combined with the theme fix in the same lp bug?
[11:15] <seb128> davmor2, seems so
[11:15] <Laney> oh, didn't notice that
[11:29] <Laney> nah, still doesn't work :(
[11:34] <seb128> :-(
[11:34] <seb128> did you try gnome-tweak-tools to see if that one is fixed?
[11:34] <Laney> it breaks when I change tab
[11:35] <desrt> Laney: already removed the properties notices.  didn't remove the mutex assert -- i think that will stay, actually
[11:35] <desrt> should backport the gtk fix i guess
[11:35] <Laney> kay, up to you
[11:36] <Laney> you doing a release?
[11:36] <desrt> i can
[11:36] <Laney> also, hi :)
[11:36] <desrt> seems relatively minor at this point, though
[11:36] <desrt> may just wait to do it on schedule
[11:37] <larsu> morning desrt!
[11:37] <desrt> good morning
[11:37] <desrt> i will leave my house in 20 minutes
[11:37] <desrt> to drive to downtown toronto
[11:37] <larsu> seb128: I've MRed a backport for gnome-system-monitor, which fixes it for all themes (Adwaita wasn't affected, but High Contrast etc. were)(
[11:37] <desrt> being that it's 8am, this will take approximately an hour
[11:38] <larsu> desrt: but ... why?
[11:38] <desrt> and is something that, under normal circumstances, i would never ever do in a car
[11:38] <desrt> because, seriously...
[11:38] <desrt> but...
[11:38] <larsu> ya
[11:38] <desrt> it turns out that today is a special day
[11:38] <desrt> i have a friend who is being released from the hospital and he needs a ride home
[11:38] <larsu> awesome \O/
[11:38] <willcooke> yay!
[11:38] <seb128> nice
[11:38] <willcooke> great news
[11:38] <seb128> larsu, thanks, looking at that, so it was not the theme itself for once?
[11:39] <larsu> seb128: yep. The background was drawn incorrectly. I had a fix and then realized there was a (better) one upstream already, so I backported that
[11:39] <seb128> larsu, great, thanks
[11:39] <larsu> we shoudl really update g-s-m... we're on 3.8
[11:40] <seb128> yeah, I think the issue was gtkheaderbar
[11:40] <seb128> going to look at updating those with patches similar to evince
[11:40] <seb128> but that's for next cycle
[11:40]  * larsu makes a note of that
[11:41] <seb128> larsu, looks good, bonus point next time if you do (lp: <nnn>) in the changelog (doing that for you on this one)
[11:41] <larsu> seb128: oops, sorry
[11:41]  * larsu never remembers _all_ the things
[11:41] <seb128> no worry
[11:46] <seb128> larsu, on updating apps topic, next fun is going to be those annoying .desktop renames
[11:46] <seb128> the one to match the dbus name
[11:46] <seb128> I wonder what to do about that
[11:46] <seb128> I guess desrt is not going happy if we revert the renames
[11:46] <desrt> what's the problem?
[11:46] <desrt> users launcher settings getting screwed around?
[11:47] <seb128> yes
[11:47] <desrt> is that the only issue?
[11:47] <seb128> yes
[11:47] <seb128> but it's an annoying one
[11:47] <desrt> do we care about users? ;)
[11:47]  * seb128 slaps desrt with a trout
[11:47] <desrt> i have a plan... ish
[11:47] <larsu> we need a big map
[11:47] <desrt> no
[11:47] <desrt> we need
[11:47] <desrt> [Desktop Entry]
[11:48] <desrt> AliasFor=org.gnome.newname.desktop
[11:48] <larsu> as a separate file?
[11:48] <desrt> yes
[11:48] <desrt> it's the only sane way
[11:48] <seb128> how would that work?
[11:48] <larsu> hello stat!
[11:48] <desrt> larsu: no.
[11:48] <seb128> then you need to patch all the .desktop parsers
[11:48] <larsu> we'd love to call you more often
[11:48] <larsu> stat stat stat
[11:48]  * larsu sings
[11:48] <desrt> larsu: what are you even talking about?
[11:49] <desrt> seb128: other choice is symlinks
[11:49] <seb128> that leads to duplicate items in e.g the unity dash
[11:49] <desrt> seb128: unless we update all the desktop file parsers :)
[11:50] <seb128> :-/
[11:50] <seb128> let's not rename
[11:50] <desrt> one way or another something has to give
[11:50] <desrt> you can't not rename :p
[11:50] <seb128> well, those had a name let's keep it
[11:50] <seb128> bet I can?
[11:50] <desrt> the problem will just get bigger with time
[11:50] <desrt> and a lot of these apps are depending on dbus activation
[11:50] <Laney> keep the old one with NoDisplay
[11:50] <desrt> Laney: NoDisplay would be implied by Alias=
[11:50] <Laney> doesn't require fixing parsers
[11:51] <desrt> with the added benefit that old parsers wouldn't even understand it at all
[11:51] <Laney> if we don't care about that, then ya
[11:51] <seb128> Laney, would e.g nautilus show launchers with NoDisplay?
[11:51] <larsu> desrt: I'm talking about not having a desktop file cache yet
[11:51] <desrt> seb128: when browsing /usr/share/applications, yes
[11:51] <seb128> desrt, well, what if I've a nautilus link on my desktop to /usr/share/applications/gedit.desktop
[11:51] <seb128> and we add NoDisplay there
[11:52] <desrt> yes
[11:52] <desrt> that should still be shown properly
[11:52] <seb128> yes what?
[11:52]  * seb128 tries
[11:52] <desrt> we do want the explicit aliasing functionality though
[11:52] <desrt> because we want to give a mechanism by which things like the launcher can update themselves
[11:53] <desrt> ie: check that the desktop file name is what we think that it is
[11:53] <desrt> and update it if it doesn't match
[11:53] <desrt> we could do that with symlinks as well, but it would involve more stat() calls ;)
[11:53] <Laney> seems like a reasonable feature
[11:53] <seb128> yeah
[11:53] <Laney> you could do both as a bridge
[11:54] <seb128> shame that things are done backward again though :/
[11:54] <seb128> rename first
[11:54] <seb128> deal with migration later
[11:54] <seb128> meanwhile users get screwed
[11:54] <desrt> we could also just do a map
[11:54] <seb128> "map"?
[11:54]  * larsu coughs
[11:54] <desrt> possibly populated via the first mechanism
[11:54] <desrt> or something like it
[11:54] <seb128> "we"
[11:54] <desrt> we is me :)
[11:54] <larsu> s/we/desrt
[11:55] <seb128> would that work for e.g KDE?
[11:55] <desrt> no
[11:55] <seb128> or would they need to do a map as well
[11:55] <seb128> k, what I though
[11:55] <desrt> no matter what we're looking at changes to desktop file parsers
[11:55] <seb128> shrug
[11:55] <seb128> not with the symlinks and NoDisplay
[11:55] <desrt> symlinks are the only way that we could completely avoid that
[11:55] <desrt> but they're only nice if you enjoy double-vision
[11:55] <seb128> well
[11:56] <seb128> having all the main parsers updated is going to take time
[11:56] <seb128> that should have been done before we start renaming
[11:56] <desrt> if you're really upset, i can give you glib by the weekend :p
[11:56] <seb128> no, I'm not, we are one cycle behind GNOME
[11:56] <desrt> anyway... if we do a map file, we can populate it via the desktop files themselves
[11:56] <seb128> so we didn't hit that wall yet
[11:56] <desrt> from WasNamed=gedit.desktop
[11:56] <desrt> or such lines
[11:56] <seb128> oh, the Debian guys were discussing a related issue yesterday
[11:57] <seb128> your favorite apps handler getting screwed on upgrade
[11:57] <desrt> seb128: this is sort of how things work, though....
[11:57] <desrt> upstream does the awesome future stuff
[11:57] <desrt> and the distro gets the fun work of figuring out how not to screw existing users
[11:57] <seb128> the mimetype associations also
[11:57] <desrt> welcome to the last 10 years of gnome-ubuntu relationship :)
[11:57] <seb128> like you upgrade and you get okular used for pdfs
[11:58] <desrt> seb128: the new spec should be backcompat to glib's previous behaviour
[11:58] <desrt> if not, i want to hear about it
[11:58] <seb128> because evince.desktop which is associated to pdf in your config isn't there anymore
[11:58] <desrt> ah
[11:58] <desrt> okay -- that's expected :)
[11:58] <seb128> "expected"
[11:58] <seb128> still wrong :/
[11:58] <desrt> i thought you meant about the mimeapps selection process itself
[11:58] <seb128> oh no
[11:58] <desrt> seb128: stop being grumpy :p
[11:58] <seb128> just another place which records the .desktop names
[11:58] <desrt> this is our job to fix and we will
[11:59] <seb128> I'm grumpy because those sort of things should be figured out before the changes happen :/
[11:59] <seb128> but yeah, let's discuss it in DC
[11:59] <seb128> that's a next cycle topic
[11:59] <desrt> i hope to have a fix before then :p
[11:59] <seb128> well your fixes are glib/GNOME specific
[11:59] <desrt> yup.
[12:00]  * desrt drives into the city
[12:00] <desrt> talk to you in a bit
[12:00] <Laney> say hi to your friend from me
[12:00] <seb128> desrt, see you!
[12:00] <desrt> Laney: will do :)
[12:01] <Laney> maybe talk to him about gtk/theme fixes for gnome-tweak-tool :-)
[12:01]  * Laney runs
[12:09] <Laney> seb128: you planning a gtk upload?
[12:09] <seb128> Laney, no, I did one this morning for gtk2 after our discussion and that was the one I had planned
[12:09] <Laney> k, np, taking that mutex fix
[12:10] <seb128> thanks
[12:11] <seb128> Laney, you can use bug #1376530 for tracking
[12:11] <seb128> bug #1374030 as well
[12:12] <Laney> yeah i had it, ty
[12:15] <dgadomski> hello everyone
[12:16] <dgadomski> seb128: update to https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333
[12:16] <seb128> hey dgadomski
[12:16] <seb128> dgadomski, what update? I see no new comment
[12:16] <dgadomski> seb128: hello :)
[12:17] <dgadomski> seb128: I have been testing the backport for gtk2 and I was observing crashes with firefox
[12:17] <dgadomski> I investigated this issue and there is a bug in gtk (both: 2 and 3)
[12:17] <dgadomski> so this needs to be first patched before this backend may be used
[12:17] <seb128> oh, nice, did you file it upstream?
[12:17] <dgadomski> yes, along with a patch https://bugzilla.gnome.org/show_bug.cgi?id=737777
[12:18] <seb128> thanks
[12:18] <dgadomski> would you like this to be included in the backport or should I make a separate lp bug for gtk2 and gtk3?
[12:19] <seb128> just add it as another patch in the series
[12:20] <dgadomski> you mean a separate patch in debian/patches?
[12:20] <seb128> yes
[12:20] <dgadomski> ok, I will, thanks a lot!
[12:52] <Laney> I just pushed gtk then, given that
[12:52] <Laney> might be best to wait a bit for upstream to review first
[12:56] <seb128> Laney, speaking about the printing issue for the upstream review?
[12:56] <Laney> yeh
[12:56] <seb128> k, makes sense
[13:00] <Laney> lunch,  biab
[13:17] <seb128> pitti, do you know where I can see the <source>translations.tar.gz exported from a build?
[13:17] <seb128> see/download to look at the content
[13:24] <pitti> seb128: ah, I don't think there's a UI for it indeed, you need to use lp-shell; hang on
[13:35] <pitti> seb128: http://paste.ubuntu.com/8479201/
[13:35] <seb128> pitti, danke!
[13:42] <seb128> ok, so the tarball is good
[13:43] <seb128> I guess it's because the launchpad template info was buggy
[13:43] <seb128> I've fixed the server side and did a no change upload of eds, let's see how that goes
[13:44] <immerrr> Hi all. I've run into an issue with gstreamer1.0-plugins-good package: it provides gstreamer1.0-audiosink, probably because it includes jack output plugin, but without jack server installed the plugin doesn't really work as an audiosink. Does it make sense to make a separate gstreamer1.0-jack metapackage to include good plugins and jack audioserver for that reason and have it provide the audiosink instead?
[14:24] <willcooke> immerrr, hrm - I'm not sure, but I think TheMuso might be able to advise you.  It's like 3 in the morning or something for him right now, but he'll no doubt see this message when he logs in
[14:34] <Trevinho> marga: hey, can you verify SRU for this: https://bugs.launchpad.net/unity/+bug/1324114 ?
[14:38] <marga> Trevinho, I can, but not today, how urgent is it?
[14:38] <Trevinho> marga: not much, take your time... I just asked since you were the reporter with a such configuration ready, so it might be quicker for you
[14:39] <marga> Right
[14:41] <Trevinho> marga: thanks
[14:49] <seb128> Laney, do you fancy fixing a segfault in some u-s-s code you wrote? ;-)
[14:49] <seb128> it's glib code
[14:50] <Laney> umm
[14:52] <Laney> link?
[14:52] <Laney> also holy shit that eds fix, I was going to debug that
[14:53] <seb128> hehe
[14:53] <seb128> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1375988
[14:53] <seb128> Laney, see the comment I just added
[14:54] <seb128> not sure what to do there/why they don't stop
[14:54] <seb128> we can wait until the callbacks are done before exiting
[14:54] <seb128> but that seems suboptimal
[14:56] <Laney> is there a trace?
[14:56] <seb128> no but I had a valgrind log and easy to reproduce
[14:57] <seb128> if I put that in the destructor
[14:57] <seb128>     while (!g_cancellable_is_cancelled (m_cancellable))
[14:57] <seb128>         g_warning("not done yet!\n");
[14:57] <seb128> it fixes it as well
[14:57] <seb128> with outputing those "not done yet" for a while
[14:58] <seb128> Laney, it's an invalid free in measure_finished()
[14:58] <seb128> well, as said I think that's because we exit the plugin/structures are freed but the callback are still pending
[14:58] <seb128> when they come back they try to free datas that are gone
[14:58] <seb128> -> segfault
[15:01] <seb128> Laney, http://paste.ubuntu.com/8479699/
[15:01] <seb128> valgrind
[15:02] <seb128> 123 is
[15:02] <seb128>     if (err != nullptr) {
[15:02] <seb128>         if (g_error_matches (err, G_IO_ERROR, G_IO_ERROR_CANCELLED)) {
[15:02] <seb128>             delete data->running;
[15:02] <seb128> the delete ^
[15:02] <Laney> so the cancellable cancels after the plugin is gone
[15:02] <seb128> yes
[15:02] <Laney> 123 is the unref here
[15:02] <seb128> well, I put debug prints
[15:02] <Laney> haha
[15:02] <seb128> that's why I tell you what line it is :p
[15:02] <seb128> it's the delete
[15:02] <Laney> kay
[15:04] <seb128> Laney, do you have any idea what the right fix would be there?
[15:04] <seb128> waiting on the callbacks to be done to exit the destructor?
[15:08] <Laney> I reckon it's because the callback is called multiple times
[15:08] <seb128> could be
[15:09] <seb128> is that one for desrt? ;-)
[15:22] <dgadomski> Trevinho: hi, thanks for your comments to the merge proposal, I have corrected it according to them
[15:22] <Trevinho> dgadomski: cool, I'll review them in a bit
[15:23] <dgadomski> Trevinho: I'll appreciate it, thanks
[15:24] <Trevinho> dgadomski: (privateScreen.optionGetHsize () > 1 || privateScreen.optionGetVsize () > 1) can also be (privateScreen.optionGetHsize () * privateScreen.optionGetVsize () > 1), as you prefer :)
[15:26] <dgadomski> Trevinho: whatever you prefer, they both get the job done ;)
[15:27] <Trevinho> dgadomski: can you also fix indentation for PointCompare? I really hate this way of indenting, but that's it... :/
[15:27] <Trevinho> dgadomski: and also
[15:27] <Trevinho> +	        savedFocus.erase (it);
[15:27] <Trevinho> +	        return w;
[15:27] <Trevinho> should be two tabs...
[15:29] <dgadomski> Trevinho: sure, fixed, please let me know if there is anything else before pushing
[15:30] <Trevinho> dgadomski: just few things, I'll post them in the revew in a sec
[15:30] <dgadomski> ok
[15:31] <Laney> seb128: something like http://paste.ubuntu.com/8479858/ ?
[15:31] <Laney> can't test it, desktop is too fast
[15:32] <seb128> Laney, I put a sleep(1) in the contructor
[15:32] <seb128> so I can click on the header while it's frozen
[15:32] <seb128> reproduce easily on desktop for me
[15:32] <Laney> oh ok
[15:32] <seb128> Laney, that diff ... if (data->running), you access the data structure after the plugin returned
[15:32] <seb128> that's likely to be problematic as well
[15:33] <Laney> where?
[15:33] <seb128> +            if (data->running) {
[15:33] <seb128> +                delete data->running;
[15:33] <seb128> but that callback is called after the plugin exited, I'm not sure the data structure is still allocated
[15:34] <Trevinho> dgadomski: done
[15:34] <Laney> oh right, yeah, it's on the heap so should be
[15:34] <Laney> might be another leak there actually
[16:02] <dgadomski> Trevinho: thanks, I've just updated the merge
[16:20] <Trevinho> dgadomski: thanks... I'm testing it, but for some reason that code don't run... and the correct lib is going, so let me check better :P
[16:20] <Trevinho> dgadomski: btw, there should be just another small clanup to do: if a window closes, then we should make sure that it gets removed from savedViewportFocus
[16:21] <Trevinho> dgadomski: oh, no sorry... that happens automatically in findViewportFocusCandidate
[16:21] <Trevinho> dgadomski: no need to do it, it will be delayed, but it's fine
[16:22] <Trevinho> dgadomski: ouch, no... So please move "savedViewportFocus.erase (it);" up before the "if (w)"... In this way also if we can't find a window that has that id, we erase it from the map
[16:23] <Trevinho> we only return it if found
[16:35] <Laney> seb128: try that
[16:35] <Laney> seems to wfm
[17:02] <Laney> byesie bye!
[17:03] <Sweetshark> chrisccoulson: https://www.youtube.com/watch?v=0YBumQHPAeU <- you brits certainly have the more interesting politicians ...
[21:31] <dupondje> Got an issue in 14.10 with Gnome. When logging in my mouse pointer freezes on the screen.
[21:31] <dupondje> can still move the mouse, but the original one stays visible on the screen. Any idea's?
[21:32] <ochosi> xnox: hey there! we're seeing an odd bug in ubiquity with xubuntu utopic with the background staying black. any idea what that could be related to? (i checked bzr and couldn't find any relevant changes and we haven't changed anything in our setup)
[23:15] <TheMuso> immerrr: Makes sense to me, but I am not in charge of gstreamer, so you may want to talk to gstreamer maintainers.