[06:20] <pitti> Laney: in your staged gnome-terminal merge in bzr, what happened with 03_add_keywords.desktop, 20_add_alt_screen_toggle_ui.patch, and 60_add_lp_handler.patch?
[06:20] <pitti> are these all obsolete? (not mentioned in merged changelog anywhere)
[07:08] <darkxst> pitti, hey, your systemd 215 is working well here ;)
[07:08] <pitti> darkxst: great, thanks for the feedback
[07:09] <pitti> darkxst: I just saw debian bug 765101 which seems to cause some trouble, that's on my list (but that's in -shim)
[07:09] <pitti> oh, slangasek already fixed it
[07:20] <darkxst> seb128, https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1380278/comments/7
[07:20] <darkxst> maybe you have a coredump laying about?
[07:22] <seb128> let me have a look
[07:31] <larsu> darkxst: it would already have crashed in line 870 in that case, when scroll_evaluators->len is accessed
[07:33] <darkxst> larsu, but it is crashing at line 870
[07:34] <darkxst> #0  0x00007f4aed57b3a4 in _gdk_device_xi2_reset_scroll_valuators (device=0x24c4b10) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdevice-xi2.c:870
[07:34] <larsu> darkxst: oops, I misread. For some reason I was under the impression that it crashed in line 874. Sorry!
[07:34] <darkxst>         i = 0
[07:34]  * larsu <-- needs more tea
[07:36] <larsu> scroll_evaluators is created in every case, though...
[07:37] <larsu> I wonder if 'device' has been unreffed one too many times and is dangling?
[07:37] <darkxst> larsu, I am thinking its somehow getting finalized
[07:37] <larsu> right
[07:37] <seb128> darkxst, the bt of the dump here starts with ??, so I can't get the info
[07:37] <seb128> let me see next time it happens
[07:38] <seb128> oh, in fact I've a new one
[07:38] <seb128> (gdb) p device->scroll_valuators
[07:38] <seb128> $1 = (GArray *) 0x0
[07:38] <darkxst> larsu, we were hitting a double free of GdkDevice, which seemed to be coming from gdk
[07:39] <TheMuso> Hey folks.
[07:39] <larsu> seb128: `p *(GObject *)device`
[07:40] <seb128> $2 = {g_type_instance = {g_class = 0x9559ca0}, ref_count = 71,
[07:40] <seb128>   qdata = 0x95610b8}
[07:40] <seb128> hey TheMuso, how are you?
[07:40] <TheMuso> Well thanks.
[07:40] <larsu> seb128: thanks. Object seems to be alive
[07:40] <TheMuso> Is anybody looking into https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721 or one of its variants? THis is affecting my usage of Orca in GNOME apps rather heavily, as I use modifiers quite a lot...
[07:41] <TheMuso> Haven't tried the work-around yet as I haven't relogged today...
[07:41] <seb128> TheMuso, no, but it would be great if you could have a look/help on that one since you hit it
[07:43] <TheMuso> Sure, I'll see what I can do tomorrow. This seems to have only bitten me after a fresh install, since I must have had something in my settings such that I didn't have ibus-daemon running in my sessiion, and now I do, well at least until I killed it today to see if it would help, given I don't need it.
[07:45] <darkxst> larsu, so we are taking a ref on the GdkDevice in idle_monitor to avoid the double free that was triggering,
[07:46] <darkxst> but somehow scroll_valuators is getting free'd but not the device?
[07:46] <larsu> ya, this is what I find strange... might be that the pointer is dangling and the ref count we're seeing is not real, though
[07:46] <larsu> darkxst: which idle_monitor do you mean?
[07:47] <darkxst> larsu, see the commit to unity-settings-daemon
[07:47] <larsu> there's a suspicious "GDK_IS_DEVICE(device)" failed in the log, too
[07:47] <larsu> darkxst: h, u-s-d, thanks
[07:52] <darkxst> larsu, yeh I saw that too
[07:54] <larsu> uhm, you take a ref in on_device_added but never unref it?
[07:55] <willcooke> morning
[07:55] <darkxst> larsu, yes, otherwise we hit a double free of the device
[07:55] <larsu> interesting. Clearly that's not the right fix ;)
[07:55] <darkxst> I'll blame Laney for that one
[07:55] <larsu> this looks suspicious as well:
[07:55] <larsu>   g_object_unref(device_monitors[device_id]);
[07:55] <larsu>   g_clear_object (&device_monitors[device_id]);
[07:56] <larsu> g_clear_object() unrefs, too
[07:57] <darkxst> larsu, we take a ref on the monitor otherwise it gets disposed before that point
[07:58] <larsu> darkxst: just to get the bug picture: this is copied from g-s-d, right? Do they have the same issues?
[07:58] <larsu> *big, not bug
[07:58] <larsu> (as I said, I'm low on tea)
[07:58] <larsu> willcooke: morning, how goes?
[07:58] <willcooke> good thanks larsu
[07:58] <seb128> hey willcooke
[07:58] <darkxst> its copied from mutter
[07:58] <willcooke> hey seb128
[07:59] <darkxst> they don't have the same problems, but the device management is handled in clutter (and that also leaks a GdkDevice ref)
[07:59] <larsu> ugh. "fun"
[07:59] <larsu> seb128: how do you reproduce?
[07:59] <seb128> larsu, I don't :-/
[07:59] <larsu> more fun \o/
[07:59] <seb128> larsu, it happens a few time a day in "normal use"
[08:00] <seb128> I've an apport file with the dump, so I can use gdb on it
[08:00] <seb128> but that's about it
[08:00] <larsu> seb128: and you don't have some weird device combination?
[08:00] <seb128> I don't think so
[08:00] <seb128> that's a dell latitude laptop undocked without anything plugged into it (out of an ubuntu phone I adb to)
[08:01] <larsu> ok, thanks
[08:04] <Laney> darkxst: what are you talking about?
[08:04] <Laney> good morning
[08:04] <darkxst> larsu, hmm, clutter has its own implementation (although very similar) of the scroll valuators, and incidently they check for NULL before reset/unset
[08:04] <darkxst> Laney, leaking the GdkDevice ref
[08:05] <larsu> hi Laney!
[08:05] <Laney> you were trying to blame gdk and now you're blaming me
[08:05] <Laney> how about stopping the blame :)
[08:05] <Laney> hey larsu
[08:06] <seb128> hey Laney
[08:06] <seb128> how are you?
[08:07] <Laney> pretty good
[08:08] <Laney> I think it's been raining for 24 hours now
[08:08] <seb128> that's u.k for you!
[08:08] <Laney> making up for lost time
[08:08]  * seb128 looks out of the windows
[08:08] <seb128> doh, it's raining here too
[08:09] <Laney> it was the driest september since records began or something
[08:09] <darkxst> Laney, well there is a bug in gdk
[08:10] <darkxst> and it possibly hasnt been noticed since clutter also leaks a ref on GdkDevice
[08:11] <darkxst> larsu, https://git.gnome.org/browse/clutter/commit/?id=676a31743993915437da419551d7c5193f0b9f43
[08:12] <Laney> pitti: is 60_ newer than that?
[08:12] <Laney> I was going to drop 20_, don't remember about 03_ but probably that too
[08:12] <Laney> I would freshen that up when coming to the point of upload of course
[08:13] <larsu> darkxst: that class creates scroll_info lazily, that's why it needs the NULL checks
[08:15] <darkxst> hmm ok
[08:17] <pitti> Laney: hey!
[08:17] <Laney> hello
[08:17] <pitti> Laney: 60_ isn't newer, it was added on Sep 30 last year, and your merge is from this May?
[08:18] <pitti> Laney: so initially I was going to take the 3.6.1 debian-ubuntu debdiff and apply it to 3.14, but as bzr already has a lot of changes staged up it might be better to update to 3.12 first, finish the merge, sort out the "cwd of new tabs" issue, and then update to 3.14 in a second step?
[08:18] <larsu> darkxst: remove_device in gdkdevicemanager-xi2.c runs dispose, but fails to unref the reference device_manager->devices has
[08:19] <larsu> that _seems_ like a leak
[08:19] <larsu> ah stop, g_object_run_dispose() also removes a ref
[08:19] <larsu> bah, I hate that function
[08:20] <Laney> pitti: then maybe it wasn't committed to bzr
[08:20] <larsu> (false alarm: it doesn't. I still hate the function)
[08:20] <Laney> I don't know if 3.14 would be much work on top
[08:20] <Laney> I would probably just do it all at once
[08:20] <pitti> Laney: possibly; so I take it the LP:# support should stay
[08:21] <seb128> larsu, thanks for helping debugging that
[08:21] <larsu> seb128: what have I gotten myself into?!
[08:21] <seb128> larsu, ;-)
[08:21] <larsu> seb128: if only I could reproduce
[08:21] <pitti> Laney: and I don't know what "Hook new vte alternate screen scrolling toggle via UI" (20_* patch) is supposed to mean; so that should go?
[08:21] <seb128> larsu, that would be too easy
[08:22] <larsu> seb128: what exactly does the idle monitor do? Is that the thing making my screen go to sleep when I don't interact?
[08:22] <seb128> right
[08:22] <larsu> this hasn't been working for me for a couple of days...
[08:22] <seb128> go to sleep/lock
[08:22]  * pitti waves to Laney and seb128 from sunny Duesseldorf, we had dinner outside yesterday, and I walked to the conference center in the sun :-P
[08:22] <Laney> pitti: if it applies, sure
[08:22] <seb128> pitti, hey, it's raining quite a lot here :/
[08:23] <Laney> alternate screen scrolling is passing mouse wheel stuff through to the terminal IIRC
[08:23] <darkxst> I have to go for dinner, will be back a bit later
[08:23] <larsu> pitti: nice, enjoy! Could you get desrt a beer from me please. He had travel trouble ;)
[08:24] <larsu> I'll repay with ice cream in DC ;)
[08:24] <pitti> larsu: yeah, he told me this morning
[08:24] <pitti> larsu: I should see him this afternoon, I'll forward the greeting and get him a beer tonight :)
[08:24] <larsu> thanks!
[08:24] <Laney> It'll need porting to the new series, so we need to decide to do that or drop it
[08:25] <pitti> Laney: oh, scrolling back through the output with the mouse wheel isn't upstream, but an Ubuntu patch?
[08:25] <pitti> how odd
[08:25] <Laney> the UI for configuring it
[08:25] <Laney> I *think*, this is dusty memory
[08:25] <pitti> ah
[08:25] <Laney> check if vte has a patch to add it or supports that upstream
[08:26] <Laney> configuring → toggling
[08:26] <pitti> Laney: ack; thanks for the heads-up so far; I had an initial look at the merge yesterday, I'll see whether I can spend some time on it this week
[08:26] <Laney> would they take the env var fallback stuff upstream?
[08:26] <pitti> Laney: do you remember a use case where people would not want it? It's not like CLI programs usually use the scroll wheel..
[08:27] <Laney> I don't think I was going to bother porting it
[08:27] <pitti> Laney: most probably not, but the discussion was fairly fruitful in the end, so maybe we can convince them
[08:27] <pitti> Laney: yeah, my feeling, too
[08:27] <pitti> (not porting the 20_ patch)
[08:27] <Laney> well you can probably work on a git checkout instead of needing to do the merge in the first instance
[08:27] <Laney> we should record the dropped patches in the changelog
[08:29] <larsu> hm, I wonder if I'm looking for an extra unref or a leak
[08:30] <larsu> Laney: do you know about this gdkdevice issue? ^
[08:30] <larsu> darkxst was saying there's a leak, but also that you needed to add extra refs to not make it crash or something
[08:32] <Laney> I think there was an extra unref somewhere
[08:33] <Laney> but his latest commits were meant to fix that, I thought
[08:33] <larsu> where are those?
[08:33] <larsu> here? https://code.launchpad.net/~darkxst/unity-settings-daemon/lp1377847/+merge/237507
[08:34] <Laney> yeah
[08:34] <Laney> if you take that branch at revision 4056 you can get the crashy version back
[08:34] <Laney> I guess that the fix for that wasn't completely right
[08:35] <Laney> I found that the GsdIdleMonitor was losing a ref in fire_watch when coming out of the monitor_became_active callback
[08:36] <Laney> anyways I'm not sure I understood it properly so feel free to take it
[08:36] <Laney> was easy to crash at that revision, just user switch to guest account and back
[08:37] <seb128> just to the greeter is enough
[08:37] <seb128> like pick another user
[08:37] <seb128> and on the greeter instead of typing the password, just go back to your user
[08:37] <Laney> yeah it's the leaving the session thats enough
[08:40] <larsu> Laney: monitor_became_active?
[08:40] <Laney> yes
[08:41] <Laney> it's a callback
[08:41] <larsu> I can't find that
[08:41] <Laney> it's in the cursor plugin
[08:41] <larsu> ah, thanks
[08:43] <Laney> anyway maybe that's meant to unref it
[08:43] <Laney> you can build it at r4056 and poke around for yourself :)
[08:44] <larsu> will do. Thanks!
[09:26] <ogra_> hmm, am i supposed to be able to install desktop-next alongside woth -desktop in utopic ?
[09:26]  * ogra_ sees urfkilld go wild on his laptop
[09:28] <seb128> pitti, re. your compiz segfault, do you have unity-settings-daemon report from apport on disk?
[09:29] <seb128> ogra_, desktop-next is an iso, you can install it, nothing block you from installing unity8 on a normal ubuntu install or unity7 on an desktop-next one
[09:29] <ogra_> seb128, well, i installed the desktop-next meta on my utpic laptop
[09:30] <ogra_> (which works fine ... but seems some services arent really desktop ready ... like urfkill)
[09:30] <seb128> ogra_, well, what you get is the current state of that stack on a desktop
[09:30] <seb128> right
[09:30] <seb128> we didn't claim it was user ready
[09:30] <seb128> the goal is to be able to test and report that sort of issues
[09:30] <ogra_> right
[09:30] <seb128> you should probably log a bug about that
[09:30] <ogra_> yep, will do
[09:30] <seb128> thanks
[09:30] <ogra_> its up to now the only actual issue i have seen
[09:32] <seb128> that's somewhat good ;-)
[11:25] <larsu> woah, u-s-d crashes a lot for me :/
[11:25]  * larsu has fixes and is testing
[11:29] <Laney> A+ would palm bugs off onto again
[11:30] <Laney> :P
[11:30] <larsu> ?
[11:30] <Laney> oh god that's not worth explaining
[11:30] <willcooke> lol
[11:39] <willcooke> dropbox pwnage :(
[11:40] <willcooke> oh, actually not Dropbox's fault, but people trying other hacked creds against dropbox
[11:40] <larsu> willcooke: they say they didn't get hacked
[11:40] <larsu> right
[12:35] <larsu> seb128, Laney: so I think I've got a fix, but I can't reproduce the crash, even with r4056
[12:37] <Laney> even with user switching?
[12:37] <LocutusOfBorg1> xnox, please let me know about 1334234
[12:37] <LocutusOfBorg1> #1334234
[12:37] <larsu> Laney: yes. I switched to Guest Session and back
[12:37] <Laney> wow
[12:38] <Laney> it crashed 100% of the time for me
[12:38] <Laney> guess it's device specific
[12:38] <larsu> might be
[12:38] <Laney> the device_id in the bt referred to my mouse
[12:38] <larsu> I don't have a mouse
[12:38] <larsu> let me enable my trackpad though :)
[12:38] <Laney> don't know if it is necessary or sufficient
[12:39] <Laney> I can try though, just hand over a branch
[12:39] <larsu> oh, that doesn't work anymore :(
[12:41] <LocutusOfBorg1> xnox, also commented on bug 1245105
[12:44] <larsu> Laney: got it when installing the package (I ran it from the source dir with --replace before)
[12:44] <larsu> I wonder what the difference is there
[12:44] <Laney> with your fix?
[12:44] <larsu> no, without. Building with the fix right now
[12:44] <larsu> I'll give you the branch once I verified
[12:44] <Laney> phew ;-)
[12:45] <larsu> do you know why it can't access any dbus services when running from the source?
[12:45] <larsu> apparmor?
[12:45] <Laney> don't know
[12:45] <Laney> that'd be in dmesg
[12:49] <larsu> Laney: doesn't crash. I love when things work out just by going through the code and looking where ref counting is done wrong :)
[12:49] <Laney> well done
[12:49] <Laney> it got a bit twisty for me to follow properly
[12:49] <larsu> ya, it was quite hairy
[12:50] <larsu> I'm thinking about writing a test for it
[12:50] <larsu> needs to get into g-s-d, too
[12:51] <larsu> but first, please test it: lp:~larsu/unity-settings-daemon/lp1380278
[12:51] <Laney> do you revert the latest commits?
[12:52] <larsu> Laney: not literally, but more or less, ya
[12:52] <Laney> good, thanks
[12:52]  * Laney builds
[12:53] <seb128> larsu, good job:
[12:53] <seb128> !
[12:53]  * seb128 gets that as well
[12:53] <Laney> did pitti ever confirm if he was hitting that?
[13:04] <tkamppeter> mvo, hi
[13:05] <seb128> Laney, no, but he's a plumber and doesn't seems to be online a lot
[13:06] <Laney> just wondering
[13:06] <larsu> is it working for you?
[13:16] <pitti> Laney: hitting what?
[13:16] <Laney> a crash in u-s-d
[13:16] <pitti> Laney: I did get u-s-d crashes along with the compiz ones, but I haven't looked at them
[13:17] <Laney> The suspicion is that your bug is the one larsu fixed ^^^
[13:17] <Laney> if you have the resources to compile u-s-d
[13:17] <pitti> Laney: or is it the other way around, and a crashing u-s-d causes compiz to crash with bug 1366351?
[13:17] <Laney> yes
[13:17] <pitti> ooh
[13:17]  * pitti hugs larsu
[13:17] <pitti> I'll build and test that, yes
[13:18] <larsu> pitti: not sure if it solves your issue. I just fixed a couple of ref counting errors
[13:18] <larsu> it's fixing the u-s-d crash for me
[13:18]  * larsu hopes for everyone else too
[13:18]  * pitti feeds sbuild
[13:25] <pitti> Laney, larsu: running desktop with your package now
[13:26] <seb128> pitti, hey, yeah u-s-d going down segfaults compiz for some reason, I pinged Trevinho about it yesterday
[13:26] <seb128> not sure he looked at it yet
[13:26] <seb128> bregma, ^ do you know?
[13:27] <bregma> seb128, is there at least a backtrace?
[13:27] <pitti> seb128: ah, so it's that way around
[13:27] <seb128> bregma, can get one if you want, it's trivial, just kill unity-settings-daemon and look yourself?
[13:27] <seb128> bregma, or segfault or or use "stop" from upstart
[13:28] <pitti> ah yes, I remember unity wetting its pants whenever I was testing a new settings-daemon
[13:28] <larsu> yep :(
[13:28] <pitti> larsu: so in the meantime my desktop already survived 5 minutes, that's good!
[13:28] <bregma> we're having a good deal of trouble reproducing #1366351 on any of our machines, if that's the key we'll be doing some wacky haopy dancing
[13:29] <pitti> before that I got compiz crashing once a minute or so
[13:29] <seb128> bregma, it might be, can you try if stopping u-s-d leads to compiz issues for you?
[13:29]  * bregma is playing with it now
[13:31] <larsu> pitti: good luck :)
[13:33] <Laney> looking good here, byw
[13:35] <larsu> glad to hear
[13:35] <seb128> same here
[13:35]  * Laney luncheon
[13:37] <pitti> larsu: my hero!
[13:38] <larsu> :)
[13:38]  * pitti back to unity -- it was absolutely useless before :(
[13:38] <pitti> odd that it never happend with my exernal monitor at home
[13:39] <larsu> pitti: do you have different input devices at home?
[13:41] <pitti> larsu: yes; the laptop is closed in the dock, i. e. no touchpad and trackpoint; I only use the external USB mouse and keyboard
[13:42] <pitti> larsu: arges in #u-devel has the same problem, I tossed him the debs from your branch
[13:42] <larsu> pitti: that might be the crucial difference. Even though I'm not sure how that would work exactly, the redundant unrefs should hit in any case
[13:43] <larsu> pitti: cool. Let me know if anyone finds problems with it. Otherwise let's try to get this in asap
[13:43] <pitti> +1
[13:43]  * pitti hugs larsu
[13:43]  * larsu is happy about all the hugs
[13:43] <larsu> and hugs back ;)
[13:49] <pitti> bregma, seb128: bug 1366351 reproducer confirmed, I updated bug title and description accordingly
[13:49] <pitti> and added the reproducer
[13:49] <seb128> pitti, thanks
[13:50] <seb128> bregma said he would confirm if he gets the issue
[13:50] <seb128> I also pointed it to Trevinho yesterday but didn't get any reply from him
[13:51] <bregma> I get the crash, I'm running apport-retrace locally to confirm it;s the same bug
[13:52] <seb128> cool
[13:52] <bregma> stuipid thing wants to download debug packages for pretty much everything installed on the system, bye-bye bandwidth
[13:53] <seb128> just use gdb on the dump?
[13:53] <pitti> bregma: everything in unity's /proc/pid/maps, which supposedly is $lots :/
[13:54] <seb128> I usually don't bother with apport-retrace to get bt for things like that
[13:54] <seb128> install glib, gtk, compiz, unity dbgsym and it's often good enough
[13:54] <seb128> I've most of those installed on my dev box
[14:13] <pitti> Laney, seb128: ok, I bent upstream git head gnome-terminal to my will; I'll send the patch upstream in case they adopt it, and otherwise just commit it to bzr
[14:14] <seb128> pitti, k
[14:25] <pitti> patch sent upstream, and now session o'clock
[14:25] <Laney> nice, ty
[14:34] <Laney> larsu: can haz MP for u-s-d?
[14:35] <larsu> Laney: sure, it seems to work, eh?
[14:35] <Laney> I'd say so
[14:37] <larsu> Laney: https://code.launchpad.net/~larsu/unity-settings-daemon/lp1380278/+merge/238309
[14:38] <Laney> merci
[14:41] <mdeslaur> hrm, is empathy supposed to work in 14.10? I can't seem to open a new chat window by clicking on people, and I am getting their new messages as weird "phone call" bubbles
[15:14] <willcooke> qengho, chrisccoulson - you got mail
[15:14] <qengho> AIEE!
[15:14] <willcooke> qengho, nothing to worry about :)
[15:29] <willcooke> yikes
[15:29]  * willcooke is slack
[15:29] <willcooke> no list of attendees yet
[15:30] <Laney> shit no summary yet
[15:30] <willcooke> :D
[15:30]  * Sweetshark sneak in at the back of the class room
[15:30] <willcooke> wing it
[15:30] <seb128> hey
[15:30] <Laney> never
[15:30] <willcooke> #startmeeting Ubuntu Desktop Weekly Meeting 2014-10-14
[15:30] <meetingology> Meeting started Tue Oct 14 15:30:37 2014 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <Laney> sexy bullet points are a must
[15:30] <willcooke> This weeks special guests include:
[15:32] <Laney> haha
[15:32] <willcooke> attente_, desrt, FJKong, happyaron, Laney, larsu, qengho , seb128, Sweetshark, tkamppeter
[15:33] <willcooke> but attente_ and desrt  might not be here
[15:33] <seb128> _o/
[15:33]  * willcooke works on the assumption that attente_ and desrt are out - if you're in, we'll come back to you
[15:33] <willcooke> actually, I'm going to skip straight to Laney because FJKong and happyaron might be asleep
[15:33] <willcooke> #topic laney
[15:34] <willcooke> Laney, over to you
[15:34] <Laney> oh man
[15:34] <willcooke> I can come back
[15:34] <Laney> no no, this has been ready for many hours
[15:34] <Laney> • Short week due to BEER
[15:34] <Laney> • evolution/e-d-s/gtkhtml updates in D & U, brown paper bag new upstream for e-d-s coming (https://bugzilla.gnome.org/show_bug.cgi?id=737903)
[15:34] <Laney> • gtk2 update
[15:34] <Laney> • webkit in Utopic and Trusty, package/test/SRUify/upload
[15:34] <Laney> • some debugging of u-s-d crashes / ref errors, finally fixed by larsu & soon to be in silo 008
[15:34] <Laney> • gst-base upload for a touch fix
[15:34] <seb128> willcooke, that's a mean thing you are doing that to a fellow u.k team mate
[15:34] <Laney> • queue and FFe reviews, etc
[15:35] <Laney> DONE
[15:35] <willcooke> seb128, Laney is solid gold - I knew he'd be ready
[15:35] <seb128> ;-)
[15:35]  * seb128 gets ready as well
[15:35] <willcooke>  /furtive
[15:35] <willcooke> thanks Laney
[15:35] <willcooke> #topic larsu
[15:35] <willcooke> larsu, you're up
[15:36] <larsu> oh wow, it's me already?
[15:36] <larsu> - triaged, investigated, and reassigned rtm14 messaging menu and sound bugs
[15:36] <larsu> - evolution theme fixes
[15:36] <larsu> - fixed the ref count problems in unity-settings-daemon
[15:36] <larsu> (upstreaming that right now + some tests for it)
[15:37] <larsu> that's it for this week (that first point took quite some time)
[15:37] <willcooke> thanks larsu
[15:37] <Laney> how's the opw stuff?
[15:37] <larsu> oh, there were some menumodel issues/discussion as well
[15:37] <larsu> Laney: trying to find out what the acceptance criteria are
[15:38] <larsu> Laney: I've got quite some candidates for the project
[15:38] <Laney> will/can you set a test or something?
[15:39] <larsu> not sure. Also not sure who to ask :( Do you know any previous mentors?
[15:39] <larsu> (we can discuss this after the meeting)
[15:39] <willcooke> let's do that
[15:40] <willcooke> #topic qengho
[15:40] <Laney> desrt might be better to ask
[15:40] <willcooke> qengho, over to you
[15:40] <qengho> * done: Cleared years of legal hurdles. Packaged actual Adobe Flash (PPAPI&NPAPI) for partners repo.
[15:40] <qengho> * in-progress: releasing chromium 38. Working on bug with internal launchpad translations.
[15:40] <qengho> * to-do: speaking of translations: adding "gd" language to whitelist. 100% as of yesterday.
[15:40] <qengho> * need: reviews of packaging.
[15:41] <willcooke> congratulations on the Flash packaging, and thanks for sticking with it to the end :)
[15:42] <qengho> I hope to have it in repo this evening.
[15:42] <willcooke> qengho, could you reply to my email re: UA when you get a sec, I'd like to get that off my list today if poss
[15:43] <willcooke> (if you haven't already)
[15:43] <qengho> willcooke: i will. it's not a "yes, done."
[15:43] <willcooke> qengho, ah, kk, thx
[15:43] <willcooke> ok, shall we move on to seb128?
[15:43] <willcooke> #topic seb128
[15:44] <seb128> • looked at translations issues on the rtm image (uitk, indicator-power, content-hub, gallery), provided fixes for most of those
[15:44] <seb128> • reported some bugs on the rtm images, looked at providing details/patches for some issues
[15:44] <seb128> • ubuntu-system-settings for touch
[15:44] <seb128> ∘ no much hacking this week, mostly reviews and testing of changes from others
[15:44] <seb128> • updated glibmm to be in sync with our glib version/fix ftbfs
[15:44] <seb128> • fixed gtk+3 translation template being outdated
[15:44] <seb128> • tested unity-settings-daemon update (fix for idle monitor issues), hit some segfaults, tried to provide useful debug info
[15:44] <seb128> • some sponsoring
[15:44] <seb128> • usual share of bugs triaging and desktop discussions

[15:44] <willcooke> excellent, thanks seb128
[15:45] <willcooke> #topic Sweetshark
[15:45] <willcooke> Sweetshark, over to you
[15:45] <Sweetshark> - configured TDF-owned hardware for shipping to datacenter
[15:45] <Sweetshark> - fixed dict-ss, dict-ve FTBFS
[15:45] <Sweetshark> - libixion MIR
[15:45] <Sweetshark> - grinded through all ~150 upstream writer regressions
[15:45] <Sweetshark> -- identified offending commits etc.
[15:45] <Sweetshark> -- did some stats on how the regressions where triaged (are they bisected? is the bugfix that caused the regression known etc.)
[15:45] <Sweetshark> - some upstream leadership and direction of employees as our ED was on vacation
[15:45] <Sweetshark> EOF
[15:45] <willcooke> thanks Sweetshark
[15:45] <willcooke> tkamppeter, you're up
[15:45] <willcooke> #topic tkamppeter
[15:46] <tkamppeter> - cups-filters: Released 1.0.61 upstream and in Utopic, to let the PPD files use the "*cupsFilter2: ..."  entry instead of "*cupsFilter: ..." to supply the destination file format as some backends, especially the IPP backend do certain things depending on the data format. Also fixed a memory leak in cups-browsed
[15:46] <tkamppeter> - First look into how to backport the IPP Everywhere support into Trusty
[15:46] <tkamppeter> - Investigations on printing multiple copies on PDF printers
[15:46] <tkamppeter> - Bugs.
[15:46] <willcooke> thanks tkamppeter - I will get back to you asap on the back porting stuff
[15:47] <willcooke> #topic willcooke
[15:47] <willcooke> * Slides
[15:47] <willcooke> * Slides
[15:47] <willcooke> * Slides
[15:47] <willcooke> * More Slides
[15:47] <willcooke> #topic TheMuso
[15:47] <willcooke> * Further discussion upstream about moving Speech DIspatcher forward and making it useful for touch.
[15:47] <willcooke> * Discussion with Qt devs upstream about whether Qt is going to have its own text to speech API. I started work on QML bindings for Speech Dispatcher some months back, but it may be quicker to work on Qt's cross-platform API instead, which would improve portability.
[15:47] <willcooke> * Hit an interesting bug with ibus-daemon and modifier keys causing issues with Orca in GNOME apps, need to debug further.
[15:47] <willcooke> * Sponsored an upload for at-spi2-atk which pulls a fix from upstream needed for GNOME shell in combination with synaptic and some other apps.
[15:48] <willcooke> #topic robert_ancell
[15:48] <willcooke> Worked on:
[15:48] <willcooke> - Released lightdm 1.10.3, 1.12.1
[15:48] <willcooke> - Prepared documentation for 1.10.3 SRU and uploaded package
[15:48] <willcooke> - Bug triage, fixing
[15:48] <willcooke> Currently working on:
[15:48] <willcooke> - Bug fixing for utopic release
[15:48] <willcooke> - Preparing for sprint
[15:48] <willcooke> Not blocked on anything.
[15:48] <willcooke> #topic AOB
[15:48] <willcooke> Looking forward to seeing you all at the sprint next week, sadly tkamppeter won't be able to join us in person
[15:49]  * Sweetshark is looking forward so see willcookes various waterslide designs in washington in action ...
[15:49] <willcooke> :D
[15:49] <willcooke> Some of them are really good
[15:49] <Sweetshark> wheee!
[15:49] <willcooke> I'm not sure the loop-the-loop will work
[15:50] <willcooke> ok, anything else from anyone before we wrap?
[15:50] <willcooke> 1 min...
[15:50] <seb128> don't spoil the slide jokes now, let some surprises for next week
[15:50] <willcooke> :D
[15:50] <seb128> ;-)
[15:51] <willcooke> #endmeeting
[15:51] <meetingology> Meeting ended Tue Oct 14 15:51:33 2014 UTC.
[15:51] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2014/ubuntu-desktop.2014-10-14-15.30.moin.txt
[15:51] <willcooke> thank you all
[15:51] <seb128> thanks!
[15:51] <Laney> b+ would meet again, if asked
[15:52] <willcooke> Laney, how were the delivery times?
[15:52] <willcooke> ooohhhhhhhh
[15:52] <willcooke> totally missed a joke about packaging there
[15:52] <willcooke> :/
[15:52] <Laney> now that part is always top notch
[15:52] <willcooke> \o/
[15:52] <Laney> but try as I might, I just could not find the trolling I'd ordered
[15:52] <willcooke> :)
[15:53] <seb128> some people here clearly need some sleep
[15:53] <seb128> could be you guys or could be me, because I've nfc what's going on :p
[15:53]  * seb128 grabs some coffee
[15:54] <willcooke> Laney's leaving us eBay feedback
[15:54] <Sweetshark> seb128: I heard if you have nfc what going on, the usual procedure is to blame it on systemd these days ...
[15:56] <seb128> Sweetshark, I don't care, having nfc is cool nowadays anyway, even the iphone6 have it from what I read!
[15:56] <Laney> I tried nfc once
[15:58] <willcooke> Laney, is that a chicken shop on Mapperley Road?
[15:59] <Laney> you just reminded me of http://www.nottinghampost.com/Magistrates-close-Khyber-Pass-takeaway-Hyson/story-21309594-detail/story.html
[15:59] <Laney> I used to go there, RIP
[16:00] <willcooke> :/
[16:31] <Chipaca> desrt: you around?
[16:31] <seb128> Chipaca, you better state your question ;-)
[16:31] <Chipaca> seb128: oh oh
[16:32] <seb128> Chipaca, he's (going?) to plumbers, so might be travelling/jetlagged/at conf/...
[16:32] <seb128> Chipaca, others might be able to help you here though
[16:32] <Chipaca> desrt: we're seeing gsettings (specifically, some but not all in the com.ubuntu.notifications.hub blacklist) get reset on reboot, any idea what may be doing that and why?
[16:32] <seb128> oh
[16:32] <seb128> he's not going to have an idea about that
[16:32] <seb128> it's not gsettings/dconf doing
[16:32] <Chipaca> tedg suggested he might
[16:32] <seb128> it's likely a buggy client
[16:33] <seb128> tedg, weird suggestion
[16:33]  * Chipaca imagines tedg having a giggling fit and Chipaca's expense
[16:33] <seb128> tedg, why would desrt would know best what on our touch device could do buggy write to that key?
[16:33] <tedg> Seems like it's not a client issue since writes happen via dbus, no?
[16:34] <tedg> And to be fair, it's desrt's touch device too :-)
[16:34] <tedg> Chipaca, After you write the value can you see it via the command line tool?
[16:34] <tedg> Chipaca, gsettings get
[16:37] <seb128> tedg, define "client"
[16:38] <seb128> tedg, I mean we have some code somewhere that write that key
[16:38] <dednick> damn. my bluetooth refuses to unblock :(
[16:38] <seb128> tedg, I suggested to Chipaca to do a dbus-monitor/bustle with an upstart job (as you blogged about some time ago) to see what calls are made by what process
[16:38] <tedg> seb128, Sure, that could work as well, I was thinking it wasn't getting saved.
[16:39] <tedg> seb128, But if someone is clearing it that's different.
[16:39] <seb128> right
[16:39] <seb128> well, from what I understood of the description something is set the key on boot
[16:39] <seb128> set->(re)setting
[16:44] <Chipaca> i did do the monitor thing
[16:44] <Chipaca> and see it getting set
[16:44] <Chipaca> but it's from a numeric id
[16:45] <Chipaca> let me run that thing again
[16:45] <Chipaca> tedg: it is getting set; it gets reset on reboot
[16:47] <Chipaca> hrm
[16:47] <Chipaca> it's the upstart bridge
[16:47] <Chipaca> tedg: ^
[16:48] <tedg> Chipaca, Wow, okay. That's weird.
[16:48] <Chipaca> upstart-dbus-bridge
[16:48] <Chipaca> owns 1.26
[16:49] <Chipaca> which is where the write is coming from
[16:49] <Chipaca> tedg: wasn't there a cleanup somethingorother?
[16:49] <Chipaca> i thought that had been dropped
[16:49] <tedg> Chipaca, I believe it has been.
[16:50] <tedg> Well, I don't think it ever got added, so dropping wasn't an issue.
[16:50] <Chipaca> that is, it was part of your original schema branch, but got nuked
[16:50] <Chipaca> yeah
[17:15] <Laney> byeee
[17:15] <seb128> dpm, do you know where the gallery-app translations are coming from on the rtm? it's a click, so from the vcs?
[17:15] <seb128> Laney, see you!
[17:16] <seb128> Laney, oh, btw, should we land the u-s-d's fix from larsu?
[17:16] <seb128> +1 from me
[17:16] <larsu> we should
[17:16]  * larsu hides
[17:16] <seb128> larsu, :-)
[17:44] <Laney> seb128: I silo'd it and commented on the bug
[17:48] <seb128> Laney, thanks
[17:48] <Laney> I can publish tomorrow if nobody has said anything bad
[18:20] <dpm> seb128, let me double-check, if it's a click, yes, the vcs
[18:27] <dpm> seb128, it seems gallery-app is being shipped as a package, and translations are shipped within the package
[18:38] <seb128> dpm, ok, thanks
[19:25] <RobBurkeOne> Hey guys. Did anyone test Gnome 3.14 in Ubuntu 14.04 so far? Perhabs by using the PPA of Rico Tzschichholz?
[19:54] <bryceh_> seb128, fyi cairo 1.14.0 is available now.  http://cairographics.org/news/cairo-1.14.0/
[20:20] <Saviq> bregma, is it known that unity is really crashy in utopic these days? I seem to get a new compiz run every time I resume, sometimes it just dies for no apparent reason, it seems especially connecting ext displays makes it unhappy
[20:20] <Saviq> it looks like settings daemon might be the reason as I'm losing gtk theming every time
[20:22] <seb128> bryceh_, thanks, I saw but we are frozen for utopic so likely for next cycle rather
[20:22] <seb128> Saviq, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008 has a fixed u-s-d
[20:22]  * Saviq gets
[20:22] <seb128> Saviq, the unity/compiz issue is something bregma / Trevinho are looking at from what they said
[20:22] <Saviq> seb128, thanks
[20:22] <seb128> yw
[20:23] <bryceh_> seb128, despite the round number 1.14.0 is largely just a lot of bug fixes.
[20:23] <bryceh_> seb128, but yeah know it's late.  cya
[20:46] <bregma> Saviq, the unity crasher bug is #1366351 if yu want to follow it
[20:46] <Saviq> bregma, awesomes, thanks
[21:10] <larsu> seb128: looks like the fix is working (from the one additional comment on the bug)
[21:12] <k1l> hey guys. i want to test the mir/unity8 to help and find bugs. so the actual way is to use the live-isos? there was a unity8 package some releases ago (which broke my install on my netbook in the end) but that is not to be used anymore?
[21:13] <seb128> larsu, great
[21:13] <larsu> k1l: the unity8 package still exists. I think you want the desktop-next meta package though, as that will pull in all dependencies
[21:13] <larsu> k1l: or install the iso
[21:14] <larsu> seb128: so I guess we can land it? Do you need anything else from me in that branch?
[21:14] <larsu> (I didn't do any changelog stuff etc)
[21:14] <k1l> larsu: i would prefer a "choice on login". is that actual possible and keeps my unity7 untouched?
[21:15] <larsu> k1l: I heard it is possible, but I'm not sure how well it works
[21:16] <k1l> larsu: ok.
[21:16] <larsu> k1l: thanks for wanting to help!
[21:19] <seb128> larsu, Laney put it in a silo, I guess he's going to handle the landing tomorrow
[21:20] <larsu> cool