[06:44] <pitti> Good morning
[06:44] <larsu> hi pitti!
[06:45] <larsu> wie war dein Wochenende?
[06:45] <pitti> hey larsu! gut, wir waren wieder in Dresden
[06:46] <pitti> und bei Dir?
[06:47] <larsu> auch schön. hab gestern ein bisschen mit poettering über fsckd gesprochen :)
[06:47] <larsu> (es war mal wieder open source meetup in berlin)
[06:49] <pitti> ah, nett!
[06:50] <seb128> good morning desktopers
[06:50] <seb128> hey larsu pitti
[06:50] <larsu> hi seb128!
[06:51] <tmpRAOF> Howdie all!
[06:51] <seb128> hey tmpRAOF
[06:52] <tmpRAOF> “vestigial” is an excellent word that I like to use in commit messages!
[06:52] <tmpRAOF> Hey seb128!
[07:08] <didrocks> good morning
[07:09] <pitti> bonjour didrocks, ça va ?
[07:14] <didrocks> pitti: ça va bien, et toi ?
[07:14] <pitti> didrocks: ça va aussi ! le week-end à Dresden était bien
[07:16] <larsu> bonjour didrocks!
[07:18] <didrocks> hey larsu
[07:45] <didrocks> pitti: seems lennart answered (and mention the fsckd patch as well)
[07:45] <didrocks> :(
[07:46] <pitti> didrocks: I saw, I'll answer today
[07:50] <seb128> didrocks-fsckd vs the universe ;-)
[07:50] <didrocks> seems so :/
[07:51]  * didrocks back to autopkgtests… why lightdm isn't starting into my test bed
[07:55] <didrocks> seb128: especially the previous email stated that we tried without it…
[07:55] <didrocks> anyway
[08:15] <pitti> didrocks: missing "needs-recommends"?
[08:16] <pitti> didrocks: lightdm without recommends doesn't start; needs Xorg, mesa, and stuff
[08:18] <didrocks> pitti: yeah, I just validated that theory ;)
[08:18] <didrocks> thanks for confirming!
[08:19] <didrocks> ok, so now plymouth…
[08:23] <larsu> btw, I had a weird transition issue yesterday where I ended up with gdm after a dist-upgrade
[08:23] <larsu> removing it left my system in an unbootable state (with systemd)
[08:23] <larsu> reconfiguring lightdm made it work
[08:23] <larsu> as did booting with upstart
[08:23] <larsu> not sure if this helps anyone...
[08:26] <didrocks> when you removed gdm, you should had have a prompt with which asked you which dm to choose, right?
[08:27] <pitti> on install, yes; on removal, not sure if there shold be a dialog if there's only one DM left
[08:27] <pitti> (what would you choose?)
[08:28] <didrocks> yeah, but it should have set /e/X/d-d-m anyway to the remaining one
[08:35] <mlankhorst> morning
[08:41] <larsu> didrocks, pitti: didn't have that
[08:41] <larsu> but lightdm was definitely still installed
[08:43] <didrocks> would have been interested to check /etc/X11/default-display-manager if you reproduce it (adding on my list)
[08:43]  * didrocks has the test writing to stderr, but not when I try to reproduce it of course :/
[08:44] <darkxst> hey all
[08:44] <darkxst> seb128, can you test baobab (with titlebar patch) on ppa:ubuntu-gnome-packaging/staging
[08:45] <seb128> hey darkxst
[08:45] <seb128> darkxst, sure
[08:46] <didrocks> evening darkxst
[08:46] <darkxst> seb128, upstream look like they will take the patch but want to use XDG_CURRENT_DESKTOP==Unity, rather the gtk-shell-uses-headers
[08:46] <darkxst> hey didrocks
[08:47] <seb128> darkxst, going to make e.g xfce sad
[08:47] <larsu> wait, what?!
[08:47] <larsu> we have a gtk-shell-uses-headers
[08:47] <larsu> ?
[08:47] <darkxst> larsu, gtk-dialogs-use-headers even
[08:47] <darkxst> https://bugzilla.gnome.org/show_bug.cgi?id=745346
[08:48] <larsu> darkxst: oh, that. Don't use that for header bars
[08:48] <darkxst> others have
[08:49] <larsu> it's wrong, though
[08:50] <larsu> also, a toolbar with a title?
[08:50] <larsu> I'd get rid of the toolbar entirely, replacing the menu button with a menu bar
[08:51] <larsu> and merging the title into the title bar
[08:56] <larsu> darkxst: mind chaning the patch to simply hiding the headerbar when on !GNOME?
[09:01] <darkxst> larsu. what about the "Back" button then though?
[09:01] <larsu> darkxst: ugh, right...
[09:01]  * larsu hates toolbars with only one or two buttons
[09:05] <Laney> morning
[09:05] <larsu> hi Laney!
[09:06] <didrocks> it's a Laney!
[09:06] <Laney> what's up?
[09:06] <larsu> right on time for some headerbar discussion
[09:06] <larsu> how was your weekend?
[09:06] <seb128> hey Laney
[09:06] <seb128> larsu, Laney, speaking about headerbar, gnome-log-viewer has some in utopic/vivid
[09:07]  * Laney sinks
[09:07] <larsu> seb128: and no menubar anymore. Why do we update those apps before we port them?
[09:08] <seb128> larsu, we don't, that one came with a direct sync from Debian
[09:09] <Laney> what's gnome-log-viewer?
[09:09] <seb128> the log viewer app from GNOME
[09:09] <seb128> yeah, I know, the name is not obvious :p
[09:09] <Laney> I mean which package
[09:10] <darkxst> seb128, gnome-logs?
[09:10] <Laney> because
[09:10] <Laney> laney@raleigh> apt-file search gnome-log-viewer                                                                                            ~
[09:10]  * larsu was struggling to explain it without using "gnome", "log", and "view"
[09:10] <Laney> laney@raleigh>                                                                                                                             ~
[09:10] <darkxst> which is systemd only?
[09:10] <seb128> no
[09:10] <seb128> the old thing we install for ever
[09:10] <seb128> gnome-system-log?
[09:10] <seb128> or how is it called
[09:10] <larsu> ya, gnome-system-log
[09:10] <seb128> just type "log" in your dash
[09:10] <Laney> oh this thing
[09:11] <seb128> bug #1376565
[09:11] <larsu> "wrong" *giggle*
[09:11] <seb128> I would almost be of the opinion to don't bother, keep the headerbar for those sort of non important applications
[09:11] <larsu> also, the bug uses "should". We should warn people when doing that
[09:12] <seb128> but we would need to have them themed to look at least a bit similar to our theme
[09:12] <seb128> and to have unity handle them correctly of course, which is still not the case... Trevinho!
[09:13] <larsu> seb128: I tend to agree. Maybe style the close buttons better, like mitya57 started in https://code.launchpad.net/~mitya57/ubuntu-themes/window-buttons/+merge/250526
[09:13] <seb128> larsu, I never understood why not using "should" in bug description, I seem to remember mpt doesn't like that but it doesn't make sense to me
[09:13] <seb128> description or title
[09:13] <larsu> seb128: because it implies a solution
[09:13] <seb128> well, "nautilus should not crash"
[09:13] <seb128> doesn't imply a solution
[09:13] <larsu> a bug report should do at least one thing: describe a problem
[09:13] <seb128> just state a fact
[09:13] <larsu> and optionally describe possible ways of solving the problem
[09:14] <seb128> no it doesn't
[09:14] <seb128> cf ^
[09:14] <larsu> seb128: not true in all cases. It crashes by design when running out of memory, not finding .ui or .gschema files, etc.
[09:14] <Laney> I'm +1 on theming as mitigation
[09:14] <larsu> "should not crash" is just not true in the general case
[09:15] <seb128> "nautilus should not hit segfault due to invalid use of memory"
[09:15] <seb128> ?
[09:15] <larsu> hm, I wonder why I didn't get an email for mitya57's comments - I'm subscribed according to the right sidebar
[09:16] <larsu> seb128: it should, though
[09:16] <larsu> seb128: you might be right for some cases of course, but generally we should (!) avoid 'should'
[09:16] <seb128> larsu, ok, what about "indicator-session should not format your drive when installed"? ;-)
[09:16] <Laney> thou shalt not double free
[09:17] <larsu> seb128: rephrase as "indicator-session formats my hard-drive when I install it"
[09:17] <seb128> larsu, well, I find them both as correct
[09:17] <larsu> but yeah, in those very obvious cases the difference isn't large
[09:17] <seb128> anyway
[09:17] <larsu> :)
[09:17] <seb128> can we theme the gtk decoration to be closer from ours?
[09:18] <seb128> like thiner bar, round buttons, colored close?
[09:18] <larsu> seb128: yes. I've played around with the branch a bit this morning and the things you describe are possible
[09:18] <larsu> seb128: thinner bar will be hard because of the subtitle widget
[09:18] <larsu> it's already quite crammed
[09:19] <seb128> hum, k
[09:19] <larsu> but we really, really need Trevinho to land frame extents before we can do this
[09:19] <seb128> right
[09:19] <larsu> because we also need to add client-side shadows
[09:19] <seb128> well, theming would put us a step closer
[09:19] <seb128> and it doesn't conflict with the unity work
[09:19] <larsu> and there's a spacing problem which I indend to fix in gtk in some way (see that MR)
[09:19] <larsu> seb128: indeed
[09:20] <Laney> nice
[09:22] <larsu> seb128: "alternatives.log — updated yesterday 12:00" would be better for us and give us slighly thinner title bars (note that we're still bound by the buttons on the right side)
[09:22] <larsu> seb128: but we can't change that from the theme sadly
[09:22] <Laney> gtk-has-thin-toolbar
[09:23] <seb128> yeah...
[09:23] <larsu> no...
[09:23] <larsu> we're getting into weird territory
[09:24] <Laney> hahaha
[09:24] <Laney> ↑ poe's law
[09:25] <larsu> Laney: I was sincere..
[09:25] <Laney> about what?
[09:25] <larsu> not liking adding another xsetting. seriously, app authors will have to test all kinds of combinations
[09:26] <larsu> we already have a few of those, I'd like to keep that number as low as possible
[09:26] <Laney> yes it was me who wasn't being serious
[09:26] <Laney> that is a stupid thing to have a setting for
[09:27] <larsu> oh. oops :)
[09:28] <Laney> we can probably just live with it
[09:28] <darkxst> hey Laney
[09:28] <larsu> make the font smaller and dim the label
[09:29] <larsu> which Adwaita seems to be doing despite the wider bar
[09:29] <larsu> maybe we can do something similar for baobab?
[09:29] <Laney> hi darkxst
[09:30] <darkxst> did I start a theme war ;)
[09:30] <larsu> rather you rekindled it ;)
[09:31] <Laney> it's a good war
[09:31] <Laney> noble and just
[09:31] <darkxst> Game of thrones vs Ubuntu ?
[09:37] <darkxst> the new gnome-shell sass theme is a little rough around the edges right now
[09:40] <flexiondotorg> MATE is not fully compatible with glib 2.43
[09:40] <flexiondotorg> We've created the required patches.
[09:40] <flexiondotorg> Tested in Debian Jessie and Ubuntu 15.04.
[09:40] <flexiondotorg> Debian have denied our unblock request to patch Debian, due to freeze for Jessie final.
[09:40] <flexiondotorg> Therefore I need to get these patches applied in Ubuntu directly.
[09:41] <flexiondotorg> How do I progress that?
[09:41] <flexiondotorg> Laney, Your thoughts? ^^^^^^
[09:41] <Laney> flexiondotorg: patches to what?
[09:41] <larsu> flexiondotorg: file a bug with a pointer to the patches (or a branch)
[09:42] <Laney> I think you should put them in the sponsor queue for normal processing
[09:42] <flexiondotorg> Laney, 5 MATE components that require a patch.
[09:42] <flexiondotorg> Laney, All 5 packages have been synced directly from Debian in the past.
[09:43] <larsu> flexiondotorg: do you know who is maintaining those packages in ubuntu?
[09:43] <Laney> Sounds like you want to make them diverge
[09:43] <flexiondotorg> larsu, Well I am on the upstream Debian maintainers team. But so far, I'm not aware of anyone maintain them in Ubuntu.
[09:44] <flexiondotorg> larsu, But it should probably be me considering I'm the lead for Ubuntu MATE.
[09:44] <flexiondotorg> Laney, Thought so.
[09:44] <flexiondotorg> Laney, No idea where to start on this though.
[09:44] <Laney> File bug, attach debdiff, subscribe ubuntu-sponsors
[09:44] <flexiondotorg> Laney, Thanks.
[09:44] <Laney> Or: upload into unstable and don't care that it's not going to go into jessie, sync
[09:47] <flexiondotorg> Laney, We've been told to not do that. Not even to experimental 😞
[09:47] <Laney> ...
[09:48] <flexiondotorg> Laney, I'll start preparing debdiffs.
[09:48] <Laney> Up to you and your sponsor I guess. If experimental's empty then I would use it personally.
[09:48] <Laney> 'kay, diff away
[09:50] <flexiondotorg> Laney, We (The Debian maintainers for MATE) want to upload to experimental. But we have been expressly told not to do so.
[09:50] <Laney> By one of your sponsors?
[09:50] <flexiondotorg> We filed an unblock request. The DDs on our team have been told to not upload these patches packages to anywhere.
[09:51] <seb128> restricting uploads to debian experimental seems weird
[09:51] <flexiondotorg> We've spent to weekend trying to get some other DDs to help fight our corner. But no.
[09:51] <Laney> are you sure that's what happened?
[09:51] <flexiondotorg> I think it is political, because these patches "fix" Ubuntu 15.04.
[09:52] <flexiondotorg> But without them, Jessie will work.
[09:52] <flexiondotorg> Technically, out implementation for gsettings was incorrect in some places.
[09:52] <Laney> I don't know who would have the authority to tell you not to upload to experimental
[09:52] <flexiondotorg> So, these patches actually make MATE technically correct.
[09:53] <flexiondotorg> Laney, I can dig up the unblock.
[09:53] <Laney> Please
[10:01] <flexiondotorg> Laney, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779340
[10:08] <Laney> flexiondotorg: I don't think it's right to interpret anything in there as preventing an upload to experimental
[10:09] <flexiondotorg> Laney, I believe our DD has had other emails. I am no privvy to them.
[10:09] <flexiondotorg> I'm still pushing that end.
[10:09] <flexiondotorg> But, I'll prepare debdiffs.
[10:09] <Laney> As you wish. I think that sunweaver might have the wrong end of the stick on this oen.
[10:11] <flexiondotorg> Laney, Possibly.
[10:11] <flexiondotorg> Laney, I'll preapre the debdiffs so I'm ready to go either way.
[10:12] <flexiondotorg> I don't want to diverge.
[10:52] <flexiondotorg> Laney, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779340#24
[10:52] <Laney> what about it?
[10:55] <flexiondotorg> Laney, I'm agreeing with your reading.
[10:55] <flexiondotorg> There is nothing there to suggest we couldn't upload to experimental.
[10:56] <Laney> Indeed. mehdi's on the release team so he's commenting on jessie matters, and then suggesting some things you might do to help the release happen sooner so you can get your stuff into testing again.
[10:57] <Laney> Nothing which stops you uploading to exp (or even sid, really, but that might get in the way of future fixes)
[10:57] <flexiondotorg> Laney, Well my take is glib 2.43.x is in experimental. Therefore, if we upload MATE fixes to experiemental we are "fixing" the issue that resides there.
[10:57] <Laney> Yes, that's fine
[10:57] <Laney> So if you can convince sunweaver, more's the better, otherwise toss the patches in the queue
[11:08] <flexiondotorg> Laney, I'm making progress in Debian land 😃
[11:08] <Laney> \o/
[11:21] <flexiondotorg> Laney, Would you be able to upload some updated package for Ubuntu MATE?
[11:21] <flexiondotorg> *packages
[11:21] <Laney> flexiondotorg: I'll be patch piloting at some point soon - toss them in the queue and I will look then
[11:22] <flexiondotorg> Laney, OK. New words to me there. "patch piloting"? What queue?
[11:28] <Laney> flexiondotorg: 1. https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews?action=show&redirect=PatchPilot#Patch_Pilots
[11:28] <Laney> 2. http://reqorts.qa.ubuntu.com/reports/sponsoring/ (subscribe ubuntu-sponsors)
[11:39] <flexiondotorg> Laney, I'm not clear how I add something to the queue.
[11:40] <Laney> flexiondotorg: Take your bug and add ubuntu-sponsors as a subscriber
[11:50] <flexiondotorg> Laney, Understood. Sorry for delayed replay.
[12:01] <flexiondotorg> Laney, do I raise the bugs against 'ubuntu-mate'?
[12:01] <Laney> flexiondotorg: against the source package you want updating
[12:01] <flexiondotorg> Laney, Thanks.
[12:45] <seb128> hum, those using vivid (and systemd maybe?), is picking another user from the indicator-session bringing you to the greeter to enter the password for that user
[12:46] <seb128> ?
[12:46] <seb128> didrocks, Laney, pitti ^
[12:46] <seb128> it just locks unity for me
[12:49] <Laney> guest ok or a real user?
[12:50] <seb128> real user
[12:51] <seb128> guest opens directly a session
[12:51] <seb128> it's not sending you to the greeter to auth
[12:51] <Laney> yeah just wondering where the problem is
[12:51]  * Laney makes a user
[12:54] <Laney> this password strength checker is mean
[12:55] <didrocks> seb128: once my current tests finshes, I can give it a try
[12:55] <didrocks> seb128: don't want to mess up with it :)
[12:55]  * Laney is also waiting for a glib build to finish :P
[12:55] <didrocks> well, let's wait first for Laney's test
[12:55] <didrocks> ahah
[12:55] <Laney> nearly done
[12:55] <Laney> dh_shlibdeps
[12:56] <Laney> Status: successful
[12:56] <didrocks> Laney: here, the testbed is installing 300M of deps, not nice turnaround fix/run timing
[12:56]  * Laney clicks the big bad button
[12:56] <seb128> brb, session restart
[12:56] <Laney> seb128: I'm at the greeter
[12:56] <Laney> with the user selected
[12:56] <seb128> Laney, ok, so it works for you :-(
[12:56] <seb128> Laney, upstart or systemd?
[12:56] <Laney> systemd
[12:56] <seb128> bah
[12:56] <seb128> I wonder why it doesn't work here
[12:57] <Laney> sorry!
[12:57] <seb128> no worry
[12:57] <seb128> needs more debugging I guess
[12:57] <seb128> I'm unsure if that "bring to greeter" is lightdm's doing?
[12:57] <seb128> but brb first
[12:57] <Laney> dm-tool iirc
[12:57] <Laney> do some playing there I guess
[12:57] <seb128> need to restart that session, click screwed it
[12:58] <Laney> still got those borders in the greeter
[12:58]  * Laney files a bug
[12:58] <Laney> oh, someone at the door, brb
[12:59] <seb128> didrocks you didn't debug more that click/schroot/ecryptfs/homedir mount issue we looked at in Bruxelles?
[12:59] <pitti> seb128: that usually works for me, hang on
[13:00] <pitti> seb128: just tried it again, works fine
[13:00] <seb128> pitti, danke
[13:00] <didrocks> seb128: didn't get the time yet to get there
[13:00] <didrocks> seb128: but I have an ecryptfs directory working here
[13:01] <didrocks> the other issue was click/schroot, and I didn't start looking at the sdk issues yet
[13:01] <didrocks> (the non cleaning up part)
[13:03] <seb128> didrocks, k, that issue is starting to really annoy me
[13:03] <seb128> I wanted to try to publish a click, but I can't install a framework due to that
[13:04] <flexiondotorg> Laney, I've files the bugs. Is it appropriate for me to assign importance to them for 'Ubuntu'?
[13:04] <didrocks> seb128: did you talk about it with the sdk guys?
[13:04] <seb128> let's see if mvo replies to my pings, I'm a bit stucked meanwhile :-/
[13:04] <seb128> didrocks, define "sdk" :-)
[13:04] <seb128> didrocks, zoltan&co bounce those issues to click, which is mvo's afaik
[13:05] <didrocks> seb128: well, click is part of the sdk to me, but yeah, fundation's for that part of the sdk :)
[13:10] <Laney> flexiondotorg: No real benefit unless you want to for your own purposes
[13:11] <xnox> didrocks: did you get to look at v2 patch for transient presets?
[13:18] <flexiondotorg> Laney, I've added the bugs to ubuntu-amte and set the priority there.
[13:19] <Laney> k
[13:28] <didrocks> xnox: didn't yet
[14:09] <seb128> bah
[14:10] <seb128> mvo, same issue when running qtcreator from another user
[14:10] <seb128> it still tries to unmount the homedir from my user
[14:10] <seb128> even more annoying, it does manage to unmount the ecvryptfs mount
[14:11] <seb128> I've to run again ecryptfs-mount-private to get back to my user dir
[14:14] <mvo> seb128: meh :/
[14:42] <desrt> good morning, all
[14:43] <seb128> hey desrt, had a good w.e?
[14:43] <desrt> not really -- sick again :(
[14:43] <seb128> :-(
[14:44] <seb128> do you feel better today?
[14:44] <desrt> not really :p
[14:44] <seb128> get some rest!
[14:44]  * desrt has been working, but has annoying cough that won't go away
[14:44] <desrt> worse is that i'm going to a sleater-kinney concert tonight
[14:44] <desrt> i hope it's loud, 'cause i don't want to be annoying everyone around me with my cough :p
[15:01] <seb128> wooot
[15:01] <seb128> got it to work
[15:02] <seb128> mvo, it's not your fault, seems to be https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/769595
[15:02] <mvo> seb128: puhhh, sounds like I got lucky this time :)
[15:03] <seb128> mvo, I'm unsure if click could help though, since it's an issue with the default fstab
[15:03] <seb128> though that the click config uses rbind, which something suggested in that bug
[15:06] <Sweet5hark> seb128: fyi: libreoffice 4.4.1 has been in the ppa for more than a week without any issues, so we should bump to that version on vivid this week. i'll prepare the package.
[15:06] <seb128> Sweet5hark, great, give me a ping when you are ready for sponsoring
[15:06] <Sweet5hark> seb128: willdo
[15:09] <flexiondotorg> Laney, when are you being a pilot or whatever?
[15:09] <Laney> in a minute
[15:09] <Laney> usually people expect to wait a bit of time for their patches to be sponsored
[15:09] <flexiondotorg> OK. Just seeing if I have time to push some more stuff today.
[15:10] <Laney> There's people looking at the queue every day
[15:10] <flexiondotorg> Laney, Cool.
[15:22] <seb128> k
[15:22] <seb128> mvo, so yeah, it's somewhat a click bug too, same bug as stock schroot
[15:23] <seb128> changing
[15:23] <seb128>  /home           /home           none    rw,rbind        0       0
[15:23] <seb128> to
[15:23] <seb128>  /home/user           /home/user           none    rw,bind        0       0
[15:23] <seb128> resolves the issue with ecryptfs
[15:24] <seb128> didrocks, ^ just as a fyi
[15:36] <mvo> seb128: oh, I think there was a branch for this actually at some point
[15:38] <seb128> mvo, https://code.launchpad.net/~mvo/click/lp1319790-chroot-fstab/+merge/219728 ?
[15:46] <mvo> seb128: yeah
[15:47] <didrocks> seb128: nice catch!
[15:53] <qengho> seb128: Here's my plan for the Chromium bug reports at errors.u.c . Tell me if it makes sense to you? ...
[15:53] <seb128> didrocks, mvo, opened https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264 about it (just as a fyi)
[15:53] <seb128> qengho, k
[15:57] <qengho> seb128: First finding is that the GPU vendors in reports roughly match the population's hardware. This suggests it's wide-ranging, and not a particular hardware feature that causes it.  Lots of Intel, AMD, some nvidia, and even "vmware". The GPU watchdog timeout is 10 seconds. That's a long time, but not so long that I'm sure it's an actual hang. Very busy CPU could cause it too. Some reports mention business.
[15:58] <qengho> seb128: So, I plan to 1) submit a apport bugpattern that scans the dmesg for specific GPU-related messages and route them to gpu-specific bug reports.
[15:59] <qengho> seb128: 2) extend the chromium watchdog timeout by a bit. If it's really a hang, then another 10 seconds won't help, and if it's not, the user gets a machine back without a watchdog killing something.
[16:01] <seb128> qengho, increasing the timeout makes sense to me yeah, having an apport script to collect more info as well
[16:06] <qengho> seb128: In addition to load, what additional info should the apport hook collect?  Already getting "hardware", df, drm, dmesg, lspci.
[16:07] <seb128> qengho, those seem enouygh to me
[16:07] <qengho> seb128: thanks for listening!
[16:07] <seb128> yw!
[16:08] <seb128> thanks for investigating the issue
[16:08] <qengho> :)
[16:28] <seb128> larsu, http://paste.ubuntu.com/10503326/ ... bug in libmessaging-menu or in the user of the lib? (g_variant_unref: assertion 'value->ref_count > 0' failed)
[16:30] <larsu> seb128: good question :)  My first guess would be in the library
[16:31] <larsu> but we've never seen this before...
[16:31] <seb128> larsu, or we never paid attention to the warnings in logs :-)
[16:33] <larsu> seb128: indeed. I'll have a look. Do you have a bug?
[16:33] <seb128> larsu, no, I'm asking where to file it :-)
[16:34] <larsu> seb128: file it for i-messages please. I'll reassign if necessary
[16:36] <flexiondotorg> Laney, saw you upload ubuntu-mate-artwork. Thanks.
[16:37] <flexiondotorg> Laney, Do you want me to ad LP: #xxx references to the changelog in the other packages?
[16:37] <Laney> Yes please
[16:37] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1427286
[16:38] <larsu> seb128: thanks. The bt doesn't correspond to trunk - do you know which version it is of?
[16:38] <larsu> rtm 248?!
[16:39]  * larsu wonders how to find out which i-messages version is shipped on there
[16:39] <seb128> larsu, https://launchpad.net/ubuntu-rtm/+source/indicator-messages/13.10.1+14.10.20141007-0ubuntu1
[16:40] <larsu> seb128: thanks!
[16:40] <seb128> larsu, dget https://launchpad.net/ubuntu-rtm/+source/indicator-messages/13.10.1+14.10.20141007-0ubuntu1
[16:40] <seb128> ups
[16:40] <seb128> larsu, dget https://launchpad.net/ubuntu-rtm/+archive/primary/+files/indicator-messages_13.10.1%2B14.10.20141007-0ubuntu1.dsc
[16:40] <seb128> still having firefox often not taking my right click/copy url orders :-/
[16:40] <seb128> larsu, yw
[16:42] <flexiondotorg> Laney, Will do.
[16:44] <larsu> seb128: turns out it is an issue in telephony-service...
[16:44]  * larsu reassigns
[16:45] <seb128> larsu, not surprised, thanks!
[16:46] <larsu> seb128: floating refs ftw!
[16:46] <seb128> heh
[16:47] <larsu> seb128: should I ping someone about it?
[16:47] <larsu> I described the problem and how to fix it
[16:47] <seb128> larsu, no, we can do that in some time if nobody responds
[16:47] <larsu> ok
[16:48] <seb128> but seems like tiagosh looks at those bugs
[16:48] <seb128> so no need to be nagging (yet)
[16:48] <seb128> larsu, danke
[17:36] <qengho> My IRC client adds (I think) duplicate entries to the messaging menu. Anyone have a tip of where to start to debug what's wrong? http://i.imgur.com/7TscLqn.png
[17:39] <larsu> neat icons...
[17:40] <qengho> :)
[17:43] <flexiondotorg> Laney, All done.
[17:43] <larsu> qengho: in d-feet, navigate to smuxi on the session bus and call "ListSources" on the com.canonical.indicator.messages.application interface (should be on at least one object)
[17:43] <larsu> qengho: I have to run now, but feel free to file a bug with the ouput of that call
[17:43] <larsu> and ping me with it
[17:44] <qengho> larsu: Thanks.
[18:11] <didrocks> see you tomorrow guys!
[18:11] <Laney> me too
[18:11] <Laney> bye!
[18:16] <desrt> Laney: btw: dconf-editor just got released for the first time
[18:16] <desrt> hopefully this doesn't make too much of a paperwork hassle this late in the cycle...
[18:17] <desrt> but uh.... you could also just keep 0.22.0 for vivid
[18:17] <desrt> dconf had a __really__ slow cycle