[07:15] <pitti> Good morning
[07:18] <darkxst> pitti, hi
[07:18] <pitti> hey darkxst, how are you?
[07:19] <darkxst> yeh good
[07:21] <darkxst> pitti, could you take alook at Bug 1192372, fixes the gdb integration for glib
[07:21] <ubot2> Launchpad bug 1192372 in glib2.0 (Ubuntu) "glib's gdb auto-load scripts are not loaded" [Undecided,New] https://launchpad.net/bugs/1192372
[07:23] <pitti> darkxst: ah nice, thanks! That looks like it should go into Debian, too, I'll commit it there
[07:26] <darkxst> pitti, yes, should go into debian
[07:27] <darkxst> thanks
[09:04] <Laney> morning
[09:05] <didrocks> morning Laney
[09:06] <seb128> good morning desktopers
[09:06] <seb128> hey didrocks Laney
[09:08] <didrocks> hey seb128 ;)
[09:11] <darkxst> hey Laney didrocks seb128
[09:11] <didrocks> hey darkxst! how are you?
[09:12] <seb128> hey darkxst
[09:14] <seb128> davmor2 clearly doesn't get how IRC works :/
[09:14] <darkxst> didrocks, yeh good, although not much to do around here while we are blocked on gtk 3.10.....
[09:14] <didrocks> darkxst: well, use those very beautiful days to relax ;)
[09:14] <Laney> can't you work with the PPA version?
[09:15] <didrocks> seb128: what happened?
[09:15] <seb128> didrocks, he finds contentless pings useful/a good thing
[09:15] <seb128> sorry, reading emails and commenting on IRC :p
[09:16] <didrocks> seb128: ah, I was puzzled, yeah ;)
[09:16] <Laney> haha
[09:16]  * Laney feels a split brain coming on
[09:16] <darkxst> Laney, we have most of 3.10 queued up on the ppa,
[09:16] <didrocks> seb128: what you replied before reading the thread? and the "netetiquette?" :)
[09:16] <seb128> ;-)
[09:16] <Laney> darkxst: oh cool, well it's a-coming
[09:17] <didrocks> like when you enter a forum, you are supposed to read all threads!
[09:17] <didrocks> :)
[09:17] <seb128> darkxst, "most of 3.10", that's not for trusty right?
[09:17] <seb128> Laney, ^^
[09:17] <seb128> that makes me not want to update GTK btw
[09:17] <seb128> I especially don't want that to make people think that it's fine to land all tons of cracks and gtkheaderbar and new UI that don't work for us
[09:17] <darkxst> seb128, no, not all of it is aimed at trusty
[09:17] <seb128> not before the LTS
[09:18] <seb128> darkxst, please give us a list of what you plan to update before starting pushing stuff
[09:19] <Laney> yeah, I'm sure they won't push stuff that affects Ubuntu :-)
[09:20] <seb128> Laney, when I see GTK 3.11 on versions I get scared at what is in those ppas :p
[09:20] <Laney> heh
[09:21] <Laney> they are pretty crackful
[09:21] <darkxst> seb128, gnome3-staging trusty pocket is not going into trusty
[09:21] <Laney> that's what PPAs are for!
[09:21] <seb128> ;-)
[09:21] <Laney> ooh, webkit/arm64 overnight build looks interesting
[09:21] <Laney> it failed at some freetype include change instead of an inscrutible arm64 assembler thing
[09:21] <seb128> it built?
[09:21] <seb128> nice!
[09:22] <Laney> could be earlier on in the build than that stuff :P
[09:22] <seb128> :/
[09:22] <Laney> don't think so though, was building javascriptcore (the problematic bit) when I left
[09:23] <Laney> dare to dream
[09:24] <seb128> the #debian-gnome guys were talking about the freetype stuff earlier this week
[09:24] <Laney> yeah, there's an upstream patch for it
[09:24] <seb128> jcristau said he would talk to slangasek about the change
[09:24] <Laney> seems they changed the include scheme or something
[09:24] <seb128> seems like pointless
[09:24] <Laney> not sure why ...
[09:24] <Laney> wonder how much other stuff got broken by that
[09:25] <seb128> quite some by the look of things
[09:25] <seb128> we already saw a few
[09:25] <seb128> I saw cjwatson mentioning he had to fix stuff the other day, doko as well
[09:26] <seb128> https://bugs.launchpad.net/bugs/1257505 btw
[09:26] <ubot2> Launchpad bug 1257505 in unity-control-center (Ubuntu) "Create Unity Control Center so can remain on old GNOME Control Center version" [Medium,In progress]
[09:26] <seb128> just pointing it for reference, robert_ancell is getting stuff ready for testing in a ppa
[09:27] <Laney> yeah I saw the conversation last night
[09:27] <seb128> k
[09:27] <Laney> what's this business about conflicting on libgnome-control-center?
[09:30] <darkxst> libgnome-control-center is an ubuntu patch, we can probably drop that from g-c-c one forked
[09:30] <darkxst> ^once
[09:31] <seb128> Laney, ^ that
[09:31] <Laney> yeah
[09:31] <Laney> but why won't it just go obsolete and get autoremoved?
[09:31] <seb128> Laney, g-c-c doesn't allow external panels, so the lib would stop providing the feature it claims providin
[09:32] <Laney> if nothing is using it any more
[09:32] <darkxst> Laney, it is used by ubuntu panels
[09:32] <Laney> I assume we'll rebuild stuff to get rid of the dependency
[09:32] <seb128> right
[09:32] <seb128> did we suggest having a conflicts?
[09:32] <Laney> yeah
[09:32] <seb128> iirc we said that autoclean would work
[09:32] <seb128> but we can add a conflict if it turns out to be needed
[09:33] <Laney> 03/12 21:09:18 <seb128> 2. just make g-c-c conflicts on the lib
[09:33] <Laney> 03/12 21:09:35 <seb128> the apt resolver should be smart enough, assuming there is no user of the lib left
[09:33] <Laney> those two statements seem to contradict each other :p
[09:33] <Laney> unless you mean apt will be happy to remove it
[09:33] <Laney> anyway, quite a minor point
[09:34] <darkxst> g-c-c won't care though, once we drop the patch, it won't link to it
[09:34] <darkxst> all the panels in upstream g-c-c are staticlly linked now
[09:34] <seb128> right
[09:34] <seb128> Laney, well, I was thinking loud about it, both options should work
[09:35] <Laney> nod
[09:35] <seb128> but since the lib is going to stop doing its job we might want to force remove it with a conflicts
[09:35] <seb128> leftover might confuse people to think it can still be used
[09:36] <Laney> it won't be able to be installed by anyone new
[09:36] <Laney> since it won't be in the archive
[09:36] <seb128> right, I was thinking about upgrades
[09:36] <Laney> only will be a bit of cruft for existing people
[09:36] <seb128> but as you said, minor detail
[09:36] <seb128> right
[09:36] <seb128> a conflicts would be no cruft for anyone
[09:36] <Laney> u-m should autoremove it
[09:37] <seb128> "should"
[09:37] <seb128> some people use apt to upgrade
[09:37] <Laney> then they get to use autoremove regularly
[09:37] <Laney> it's the apt way™
[09:37] <darkxst> well they get told by apt to use auto-remove
[09:38] <Laney> anyways
[09:39] <Laney> I thought the settings daemon would come first, interesting
[09:39] <seb128> yeah, me too
[09:40] <darkxst> seb128, have you look at gnome-desktop?
[09:40] <seb128> darkxst, no, once step at the time, that one is an annoying one
[09:41] <seb128> we can't fork the lib
[09:41] <seb128> we would need 2 versions/builds of all the rdepends, that would be a mess
[09:41] <darkxst> seb128, yes, and can't revert the display config stuff
[09:42] <seb128> why not?
[09:42] <darkxst> it would be a nightmare patch
[09:43] <seb128> so we need to hold on upgrades I guess...
[09:43] <darkxst> well that blocks g-s-d/g-c-c upgrades to 3.10
[09:43] <darkxst> but probably not gnome-shell, which is just blocked on gtk
[09:43] <seb128> do you have a solution to suggest?
[09:44] <darkxst> seb128, yes implement the dbus interface in unity or compiz
[09:44] <seb128> patches are welcome
[09:44] <seb128> I don't see that happening this cycle from the unity team
[09:44] <seb128> they are overloaded already and they have other priorities than changing stuff that work
[09:44] <seb128> I agree it would be nice, I just don't it happening before the LTS/unity8
[09:45] <seb128> don't see*
[09:48] <darkxst> seb128, can I cut+past GPL code into unity or is it CLA only?
[09:48] <seb128> CLA only
[09:50] <darkxst> right, so a reasonably simple task, becomes not so simple
[09:50] <seb128> indeed
[09:58] <seb128> darkxst, we should see what APIs are concerned and archive grep for their users
[09:58] <seb128> if it turns out to be only g-s-d we can probably include the old functions/sources in u-s-d
[09:59] <seb128> but GnomeIdleMonitor might be used by other things
[10:00] <seb128> http://codesearch.debian.net/search?q=gnome_idle_monitor
[10:00] <seb128> gnome-session to start :/
[10:01] <seb128> http://codesearch.debian.net/search?q=gnome_rr
[10:01] <seb128> colord
[10:01] <seb128> gnome-screensaver
[10:02] <darkxst> idle monitor is fine, I can revert that for unity easy enough
[10:02] <seb128> what's the issue?
[10:02] <darkxst> seb128, its just the display config that is a big mess
[10:32] <seb128> tjaalton, mlankhorst: hey, can you put bug #1238410 on your todolist? (basically making sure we get http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.14-branch&id=6cc5efa68e5fdc301ab9a381bffe88fe5c7865e2 in trusty)
[10:32] <ubot2> Launchpad bug 1238410 in X.Org X server "Inconsistent cursor visibility with cursor plugin enabled" [Medium,In progress] https://launchpad.net/bugs/1238410
[10:32] <seb128> that's in xserver git 1.14 branch, I guess we are going to get the current version from there even if we don't get 1.15?
[10:34] <mlankhorst> we'll get it eventually. :P
[10:35] <seb128> mlankhorst, not "eventually" :p thanks!
[10:39] <mlankhorst> if it's in the server then we'll probably have to sru the new upstream release anyway to saucy
[10:41] <seb128> why?
[10:41] <seb128> well, as long as those fixes are in the LTS I'm happy
[10:45] <mlankhorst> because it has some other nice fixes too
[10:45] <seb128> k
[10:45] <seb128> pitti, do you want me to upstream that telepathy-gabbler g_source_remove error?
[10:46] <seb128> I can do it now if you want
[10:46] <pitti> seb128: ah, thank you; sorry, drowning in stuff, need to clean up my firefox tabs/requests
[10:46] <seb128> mvo, hey, do you plan to upload that aptdaemon fix you did yesterday, or should I just cherrypick it?
[10:46] <seb128> pitti, no problem, doing that
[10:47]  * pitti hugs seb128 for chasing bugs
[10:47]  * seb128 hugs pitti back
[10:47] <seb128> LTS cycles ftw ;-)
[10:57] <seb128> pitti, https://bugs.freedesktop.org/show_bug.cgi?id=72303
[10:57] <ubot2> Freedesktop bug 72303 in gabble "Invalid g_source_remove use leads to error with new glib (2.39)" [Normal,New]
[10:58] <pitti> seb128: merci
[11:02] <seb128> de rien
[11:06] <seb128> mlankhorst, thanks for the cft email!
[11:08] <pitti> mlankhorst: indeed, I'm about to add the PPA; that's safe for trusty, i. e.  said xorg patch is in trusty?
[11:09]  * pitti installs -- I miss the "debug today's X.org breakage" fun from 2007!
[11:10] <pitti> nowdadays it's just "seb128 broke my jabber", which isn't half as much fun!
[11:10]  * pitti hugs seb128
[11:10] <seb128> lol
[11:10]  * seb128 hugs pitti
[11:12] <mlankhorst> pitti: yeah and I added a breaks, so it shouldn't even install on saucy :P
[11:13] <pitti> mlankhorst: ok, rebooting; brb (hopefully :) )
[11:13] <mvo> seb128: I prepared both the saucy and trusty branches, but there was test failure in my rebuild test, not sure if its just a local issue or not. it looks unreleeated to my change though. and thanks for the hugging yesterday :-D
[11:15] <pitti> mlankhorst: it's exactly as boring as before, everything seems to work at least initially (unity, dash, video playback, glxgears)
[11:15] <pitti> mlankhorst: where is the breakage/fun you promised!?
[11:15]  * seb128 hugs mvo
[11:15] <seb128> mvo, yw ;-)
[11:15] <seb128> mvo, we miss you there!
[11:16] <mlankhorst> pitti: erm where did I promise that? :p
[11:16] <pitti> mlankhorst: *hug*, I wanted to say: nice job!
[11:16] <seb128> mvo, let me test build here to see if tests are unhappy as well
[11:16] <pitti> mvo: ooh, does that fix the long-standing test failure?
[11:17] <seb128> mvo, no, he fixed the most report e.u.c errors, but can't roll the fix out because a test is failing
[11:17] <mvo> pitti: it fixes a long standing errors.ubuntu.com issue, I have not really looked at the test
[11:17] <mvo> (yet :)
[11:17] <pitti> https://jenkins.qa.ubuntu.com/job/trusty-adt-aptdaemon/20/ARCH=i386,label=adt/console
[11:17] <pitti> KeyError: 'defer'
[12:13] <seb128> http://www.linuxjournal.com/rc2013?page=53
[12:14] <seb128> that's a "fun" list
[12:18] <ogra_> lol
[12:18] <ogra_> "poetterings ideas"
[12:18] <ogra_> awesome
[12:18] <seb128> yeah :p
[12:18] <mlankhorst> tons of ubuntu hate
[12:19] <ogra_> well, but gnome is worse than Mir
[12:19] <mlankhorst> less popular, though
[12:19] <davmor2> seb128: it is indeed a fun list, but the big one for me is that Gnome 3 is knida hated more than anything Ubuntu does :D
[12:20] <seb128> davmor2, don't talk to me, you contextless pinger :p
[12:20] <ogra_> LOL
[12:20] <ogra_> why does it feel so much like friday today
[12:21] <seb128> ogra_, it's december, every day feels like friday
[12:21] <seb128> ;-)
[12:21] <ogra_> heh, yeah
[12:21] <Laney> too much mulled wine
[12:22] <seb128> hum, mulled wine, helps to fight the cold weather ;-)
[12:22] <ogra_> ++
[12:22] <davmor2> seb128: single malt whisky does a better job
[12:23] <Laney> Not sure how constructive that kind of peanut gallery hate list is
[12:23] <seb128> Laney, "not at all"...
[12:23] <seb128> they have some weird sections in that survey
[12:24] <Laney> davmor2: Not a very classy celebration :/
[12:24] <Laney> let's just link to http://www.telegraph.co.uk/finance/1000-companies-inspire-britain/10485791/ubuntu-canonical-hi-tech.html instead
[12:24] <Laney> :-)
[12:24] <davmor2> Laney: not celebrating other than Ubuntu wasn't top which was what I was expecting
[12:25] <seb128> Laney, nice title, /me reads
[12:27] <desrt> ouch
[12:28] <davmor2> Laney: that is a nice read :)
[12:28] <desrt> glad to see ubuntu and gnome still agree on one thing: making everyone hate us
[12:29] <desrt> i have to admit that my vote is with the guy who wrote-in the response for "this question" as the worst thing
[12:30]  * desrt wonders when people will stop doing this pointless shit
[12:30] <Laney> when it stops generating clicks
[12:30] <desrt> seb's fault for putting it on IRC
[12:30] <desrt> bad seb.  no cookie.
[12:33] <Laney> tsk, ogra_ shared it on g+
[12:33]  * ogra_ finds it massively entertaining ... 
[12:34]  * desrt learns that there is, in fact, a market for this stuff
[12:45] <mlankhorst> seb128: hm mouse is still invisible with that patch
[12:45] <seb128> mlankhorst, oh, you can reproduce that bug?
[12:46] <seb128> mlankhorst, in fact I think it's to apply on top of the 2013-10-22 commits on http://cgit.freedesktop.org/xorg/xserver/log/Xext/sync.c?h=server-1.14-branch
[12:46] <seb128> mlankhorst, is xorg doing point bugfix releases? ;-)
[12:47] <mlankhorst> seb128: I was testing xorg-server 1.14.4 which has those fixes
[12:48] <seb128> :-(
[12:48] <seb128> how do you reproduce the issue?
[12:48] <mlankhorst> oh wait, maybe not the corner-case patch
[12:50] <mlankhorst> I'll try cherry picking that one too
[12:51] <seb128> mlankhorst, thanks ... still, how do you reproduce the bug? I never saw it, do you have a special trick?
[12:52] <mlankhorst> not really, nfs netboot + synergy :P
[12:53] <mlankhorst> thought it was a feature for having no mouse plugged in
[12:53] <mlankhorst> never looked closely though
[12:58] <mlankhorst> seb128: nope, even with the cherry pick...
[12:58] <seb128> mlankhorst, well, if you have no mouse your issue seems like a different bug
[12:59] <mlankhorst> "On fresh boots the greeter & desktop may have the cursor visible or may not until mouse is moved."
[12:59] <seb128> well, having a mouse
[12:59] <seb128> which you don't have?
[13:00] <mlankhorst> fine *plugs in dongle*
[13:03] <mlankhorst> yeah looks like it's invisible until moving ;p
[13:03] <seb128> :-(
[13:03] <seb128> ok, well I guess those fixes would still be nice to get in
[13:03] <seb128> even if they are not enough to fix that specific bug
[13:04] <mlankhorst> pushed
[13:05] <mlankhorst> it seems to be deliberate though, mouse is invisible until I move it, and doesn't become visible if I don't have a dongle plugged in
[13:05] <mlankhorst> which makes synergy harder to use :/
[13:07] <seb128> mlankhorst, that bug is about the cursor not becoming visible after moving
[13:08] <mlankhorst> ah
[13:11] <mlankhorst> seb128: but that's still the case if I only have synergy to control the cursor :P
[13:12] <seb128> seems a different issue still ;-)
[13:31] <tkamppeter> seb128, see https://bugs.freedesktop.org/show_bug.cgi?id=72312 for my final Poppler patch, I have uploaded Poppler a second time for the file of comment #3 in the bug report.
[13:32] <ubot2> Freedesktop bug 72312 in utils "[patch] pdftops: Fixes/improvements for -origpagesizes" [Normal,New]
[13:32] <seb128> tkamppeter, thanks
[13:42] <rickspencer3> hi seb128
[13:42] <seb128> rickspencer3, hey, how are you?
[13:42] <rickspencer3> seb128, I'm good
[13:42] <rickspencer3> my laptop with the hybrid graphics, not so much :/
[13:43] <seb128> still not booting?
[13:43]  * rickspencer3 tries booting into recovery console
[13:43] <seb128> did you try to boot an old kernel?
[13:43] <rickspencer3> seb128, yeah, I booted the oldest kernel on it
[13:43] <seb128> still the same issue?
[13:43] <rickspencer3> yes, acts the same
[13:43] <seb128> which means, hangs at boot before lightdm, no way to go to a vt?
[13:43] <rickspencer3> the Ubuntu logo with the dots, then a blank screen with a still cursor
[13:44] <rickspencer3> seb128, correct
[13:44] <seb128> when did that start? did you play with drivers/bios settings before?
[13:44] <rickspencer3> seb128, sounds like I am alone in getting this issue though, which is good
[13:44] <rickspencer3> I was worried you may have other reports of people having problems
[13:44] <seb128> robert_ancell said he was getting it as well with the current kernels
[13:44] <rickspencer3> seb128, well, I had no problems until yesterday
[13:44] <seb128> we don't have that many users running trusty
[13:44] <seb128> and most of us pick intel hardware
[13:45] <rickspencer3> I actually picked this because it had complicated graphics
[13:45] <rickspencer3> to make sure I knew what users experience
[13:45] <rickspencer3> seb128, so, I booted into recovery mode
[13:45] <rickspencer3> thoughts?
[13:46] <seb128> tseliot, mlankhorst: ^ do you know if there is a driver/kernel issue with hybris systems on trusty? rickspencer3's box hangs when xorg tries to start, he can't even go to a vt
[13:46] <mlankhorst> what box?
[13:46] <seb128> rickspencer3, check for kernel oops errors in dmesg or syslog?
[13:46] <rickspencer3> mlankhorst, hybrid graphics with nvidia
[13:46] <mlankhorst> what driver
[13:46]  * ogra_ would ask tseliot ... our nvidia guru 
[13:47] <mlankhorst> and what card :P
[13:47] <rickspencer3> mlankhorst, don't know
[13:47] <mlankhorst> well bug the kernel team then :D
[13:47] <rickspencer3> seb128, is it possible I have a run of the mill packing issue or somehting?
[13:47] <rickspencer3> should I check dkpg first or something?
[13:47] <seb128> rickspencer3, well, you can check /var/log/dpkg.log to see what changed in the upgrade before the issue start
[13:48] <rickspencer3> seb128, oops, I just ran apt-get update
[13:48] <seb128> that doesn't change anything
[13:48] <seb128> that log has timestamp and record of all changes
[13:48] <seb128> it's rotated, not cleaned
[13:48] <mlankhorst> rickspencer3: anyway try the kernel from saucy
[13:49] <mlankhorst> I'm guessing it might be a runtime pm issue, recent kernels enabled it :P
[13:49] <seb128> mlankhorst, can that be turn off from grub with an option?
[13:50] <mlankhorst> if he uses nouveau probably
[13:50] <seb128> rickspencer3, do you use the nvidia binary drivers or nouveau?
[13:50] <rickspencer3> nouveau
[13:50] <rickspencer3> at least I don't recall installing binary drivers :)
[13:50] <seb128> mlankhorst, how do you turn it off with nouveau?
[13:50] <mlankhorst> add nouveau.runpm=0
[13:51] <rickspencer3> mlankhorst, where do I add that?
[13:51] <mlankhorst> to kernel cmdline
[13:51] <seb128> in grub
[13:51] <seb128> you can edit the command line with "e"
[13:51] <seb128> (iirc, didn't do that for a while)
[13:51] <rickspencer3> yeah, let me try it
[13:53] <rickspencer3> mlankhorst, where specifically do I add that option?
[13:53] <mlankhorst> rickspencer3: to the kernel line
[13:53] <rickspencer3> I presume you mean the line that says linux
[13:53] <mlankhorst> yeah
[13:54] <rickspencer3> mlankhorst, do I just add it to the end, after $vt_handoff ?
[13:54] <mlankhorst> anywhere
[13:54]  * rickspencer3 tries
[13:54] <mlankhorst> but that's a good place i think
[13:55] <rickspencer3> uh
[13:55] <rickspencer3> mlankhorst, ok, no love there
[13:55] <mlankhorst> thought so, can you run a kernel from saucy?
[13:55] <rickspencer3> mlankhorst, I suppose I could install one
[13:56] <rickspencer3> mlankhorst, though, it worked until yesterday
[13:56] <seb128> what did you change yesterday?
[13:56] <rickspencer3> and I tried the oldest kernel on my computer
[13:56] <seb128> how old is the oldest one?
[13:56] <rickspencer3> seb128, I did a dist-ugprade
[13:56] <rickspencer3> seb128, hold on not that old
[13:56] <seb128> do you regularly clean those?
[13:57] <rickspencer3> seb128, when I get back to grub menu I can tell you specifically
[13:57] <seb128> rickspencer3, it might be easier to just install a saucy kernel to see if that fixes it
[13:57] <seb128> it would have several advantages
[13:57] <seb128> including nailing down the issue to the kernel
[13:57] <seb128> giving you also a working system to look at your logs, open a bug report, etc
[13:58] <seb128> not sure why it started yesterday, robert_ancell seemed to have the same issue on trusty but before then
[13:58] <rickspencer3> seb128, my oldest kernel is 3.11.0-13
[13:58] <rickspencer3> seb128, robert_ancel and I had the same issue within lightdm
[13:59] <rickspencer3> it wouldn't take keyboard input until we activated a menu
[13:59] <seb128> 3.11.0-13 should be a saucy one I think :/
[13:59] <rickspencer3> but it fixed for him yesterday
[13:59] <rickspencer3> seb128, yeah
[13:59] <rickspencer3> I'm going to try to dist-upgrade again
[13:59] <seb128> mlankhorst, did we get a nouveau update in trusty?
[13:59] <mlankhorst> nothing
[14:00] <seb128> rickspencer3, do you opt in for some testing ppa yesterday?
[14:00] <rickspencer3> seb128, nope
[14:00] <rickspencer3> seb128, could it be related to having the emulator installed? I recall some users had issues with that
[14:00] <rickspencer3> though I did not try to uninstall it
[14:00] <seb128> I doubt it
[14:01] <ogra_> *when* did you install the emulator ... the early version definitely had libc/i386 issues on amd64 machines
[14:01] <rickspencer3> ogra_, it was after those issues were solved
[14:01] <ogra_> that was only around for one or two versions though
[14:01] <rickspencer3> but, there was some error meesage in my indicators about not having dependencies for it or something
[14:01] <ogra_> yeah, then you shouldnt have any issues due to it
[14:01] <rickspencer3> but I igonried it
[14:02] <seb128> ogra_, the machine seems to lock on xorg start
[14:02] <ogra_> right, i have that here too ...
[14:02] <ogra_> seems some multiarch issue, but shouldnt do harm (apart from making update-manager moan)
[14:02] <rickspencer3> I probably don't have xorg even installed or something :)
[14:02] <rickspencer3> ogra_, well, that's what I presumed as well, of course
[14:03] <rickspencer3> but now I'm grasping at straws trying to get the desktop back
[14:03] <ogra_> (surely something that needs fixing ... but very unlikely related)
[14:03] <seb128> rickspencer3, can you copy your /var/log/dmesg syslog(.1) Xorg.0(.old) somewhere?
[14:04] <ogra_> ++
[14:04] <rickspencer3> looks like I'm getting yet another kernel in this dist-upgrade
[14:04] <tseliot> seb128: with or without using the nvidia-prime package?
[14:04] <ogra_> logs ftw
[14:04] <rickspencer3> seb128, yeah, I could ftp it to my server
[14:04] <rickspencer3> let me finish this dist-upgrade and then I'll check back in if it still does not boot
[14:04] <seb128> tseliot, rick dist-upgraded yesterday and got the issue, is that pulled in on upgrade in some way?
[14:04] <seb128> rickspencer3, ok
[14:04] <seb128> rickspencer3, dpkg.log would be useful as well
[14:05] <tseliot> seb128: jockey only installs it in precise
[14:05] <tseliot> so, no
[14:05] <seb128> tseliot, ok, I doubt it's that, rickspencer3 is apparently using nouveau so no jockey or anything
[14:05] <seb128> and it's trusty
[14:05] <ogra_> well, seemingly installed under saucy
[14:05] <tseliot> oh, it sounds like a work for mlankhorst then ;)
[14:05] <rickspencer3> ogra_, no I probably installed with precise, I don't even remember
[14:06] <ogra_> (unless the old kernel was installed manually or some such)
[14:06] <rickspencer3> like precise development
[14:06] <ogra_> ah
[14:06] <rickspencer3> I don't even remember what O was called
[14:06] <rickspencer3> Ornery?
[14:06] <tseliot> rickspencer3: oneiric :)
[14:07] <tseliot> rickspencer3: if you get some logs, I'll see if I can help
[14:07] <ogra_> whee, working KBD on my phone ... and even with umlauts !
[14:07] <rickspencer3> anyway, predictably, the dist-upgrade did not help
[14:07]  * rickspencer3 enables networking, prepares to upload files
[14:10] <didrocks> ogra_: more importantly than any umlauts, the keyboard is now in azerty for sane languages \o/
[14:10] <ogra_> lol ...
[14:11] <rickspencer3> wow
[14:12] <rickspencer3> "French" and "sane" are two words I don't think I've ever seen together in the same phrase
[14:12] <seb128> rickspencer3, stop trolling us if you want your laptop to ever boot again :p
[14:12] <ogra_> haha
[14:12] <rickspencer3> lol
[14:13] <didrocks> seb128: that's how we're supposed to talk! :)
[14:13] <seb128> cyphermox, hey ... looking at e.u.c, did you ever get anywhere with the wpasupplicant issues?
[14:13] <seb128> didrocks, thanks for the support ;-)
[14:17] <cyphermox> seb128: I did
[14:18] <cyphermox> I think I may just be missing the upload to saucy or something, let me look
[14:18] <seb128> cyphermox, thanks!
[14:26] <seb128> cyphermox, the e.u.c trusty report suggests your fix there worked, nice job ;-)
[14:27] <seb128> mvo_, where are the distro template coming from?
[14:27] <seb128> e.g in those errors
[14:27] <seb128>   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in get_sources
[14:27] <seb128>     (self.id, self.codename))
[14:27] <seb128> aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/trusty
[14:28] <seb128> that seems a frequent issue in add-apt-repository
[14:30] <seb128> python-apt-common: /usr/share/python-apt/templates/Ubuntu.info ?
[14:31] <mvo_> seb128: yes, from python-apt
[14:32] <seb128> mvo_, haha, ok, those people have the saucy python-apt-common while on trusty
[14:32] <seb128> not sure how that happens :/
[14:34] <didrocks> Mirv: once you are aroud, you probably want to answer on the ubuntu-devel ML (as expressed in the hangout and other discussions, I'm too in favor of not bumping the soname and rebuild everything in one shot, knowing how many packages we have, that seems like a saner way to deal with it)
[14:34] <didrocks> seb128: can it be mint?
[14:34] <seb128> didrocks, no, some are mint, but most are 14.04 proper
[14:34] <didrocks> ok
[14:34] <seb128> didrocks, e.g https://errors.ubuntu.com/oops/7efa6264-5b43-11e3-88f9-e4115b0f8a4a
[14:35] <didrocks> just a very wild guess :)
[14:35] <seb128> python-apt-common 0.8.9.1ubuntu1
[14:35] <seb128> didrocks, look at https://errors.ubuntu.com/problem/6c2010c50c6aa52ce59374e24c9780acd0505c09
[14:35] <didrocks> ok, so they changed it
[14:35] <seb128> so mint has the issue, but I don't care much about them
[14:36] <seb128> mvo_, I'm just going to make the trusty software-properties depends on python-apt-common (>= 0.9)
[14:36] <mlankhorst> rickspencer3: fwiw my nvd9 seems to lock up too
[14:37] <mlankhorst> so maybe kernel broke somewhere
[14:37] <didrocks> seb128: yeah, sounds like it's needed, maybe they did partial upgrades as you do sometimes :)
[14:37] <seb128> mlankhorst, can you get enough info to open a bug report?
[14:37] <seb128> didrocks, right...
[14:37] <mlankhorst> no idea what he has
[14:37] <mlankhorst> I'm running something crazy unstable anyway, 3.13rc2 + merging drm-nouveau
[14:37] <didrocks> ok, I'm late for running, time for exercising!
[14:38] <seb128> didrocks, enjoy!
[14:39] <didrocks> thanks!
[14:57] <seb128> desrt, hey, do you have time to help with a telepathy test failing with glib 2.39?
[15:02] <desrt> sure
[15:03] <seb128> desrt, do you prefer here or #gtk+?
[15:03] <desrt> here is fine
[15:04] <seb128> desrt, telepathy-glib testsuite started failing one test,  http://paste.ubuntu.com/6520095/
[15:04] <seb128> desrt, xclaesse tested reverting https://git.gnome.org/browse/glib/commit/?id=4e9e7d0cba53a711bd650e9a5e28452b93f0d849 and that fixes it
[15:04] <seb128> desrt, not sure if the issue is on glib or telepathy's side but I would appreciate if you could have a look
[15:05] <seb128> desrt, just try to make check telepathy-glib with glib 2.39 to reproduce
[15:05] <hallyn> hi - my dash suddenly stops giving me any results.  is there some cache that might be corrupt that i can clean out?
[15:05] <seb128> hallyn, hey, try asking mhr3 on #ubuntu-unity
[15:06] <hallyn> seb128: thanks
[15:06] <seb128> yw
[15:09] <xclaesse> desrt, FYI the telepathy-glib code is there: http://cgit.freedesktop.org/telepathy/telepathy-glib/tree/telepathy-glib/file-transfer-channel.c#n275
[15:12] <desrt> i am able to reproduce locally
[15:14] <xclaesse> basically it splice a GFileInputStream into a GSocketConnection's outputstream
[15:15] <xclaesse> or vice-versa, didn't check if it's the receiving file test or sending file test
[15:16] <desrt> will look into it soon
[15:18] <seb128> desrt, thanks
[15:33] <Sweetshark> seb128: sooo, bug 1207057 is hanging in verification-needed as I dont have a native precise install with intel drivers. Would it be enough to take https://bugs.launchpad.net/ubuntu-advantage/+bug/1176923/comments/13 as verification?
[15:33] <ubot2> Sweetshark: Error: launchpad bug 1176923 not found
[15:33] <ubot2> Launchpad bug 1207057 in libreoffice (Ubuntu Precise) "presentation causes system to hang" [Undecided,Fix committed] https://launchpad.net/bugs/1207057
[15:35] <seb128> Sweetshark, yes, it's also enough to state that no regression were found even if the fix isn't fully working
[15:36] <Sweetshark> seb128: which is what I did in https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1207057/comments/11 ;)
[15:36] <ubot2> Launchpad bug 1207057 in libreoffice (Ubuntu Precise) "presentation causes system to hang" [Undecided,Fix committed]
[15:36] <seb128> Sweetshark, just change it to verification-done then ;-)
[15:39] <Sweetshark> seb128: done, thx
[15:39] <seb128> Sweetshark, thank you
[15:57] <sil2100> Hey, anyone else having problems adding new jabber accounts in the online accounts desktop settings?
[16:02] <seb128> sil2100, works fine for me (just added my jabber.org account in a guest session)
[16:02] <seb128> sil2100, what issue do you have?
[16:02] <sil2100> seb128: thanks for checking, I noticed that many things don't work well on my system right now... but when I try to add an account, I'm being asked to give the username and password, but I cannot proceed beyond that
[16:03] <sil2100> Nothing happens when I confirm the data
[16:03] <seb128> weird
[16:03] <seb128> no error on the command line if you run it there?
[16:03] <seb128> no apport file?
[16:03] <sil2100> No apport file, but let me check the cmd output then
[16:08] <sil2100> seb128: no console output, nothing - I'm pressing Ready and nothing happens, no reaction ;/
[16:08] <sil2100> seb128: the app is responsive, just that the button and pressing enter doesn't seem to do anything
[16:08] <seb128> sil2100, dunno, check with kenvandine or mardy I guess
[16:09] <kenvandine> sil2100, look in syslog
[16:10] <sil2100> kenvandine: nothing as well...
[16:13] <xclaesse> seb128, FYI, empathy preference dialog also looks ugly with gtk master
[16:13] <xclaesse> taking the full screen width
[16:14] <seb128> xclaesse, some fixes landed in gtk
[16:14] <xclaesse> upgraded gtk 5min ago
[16:14] <xclaesse> still broken
[16:14] <seb128> xclaesse, 3.10 has https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-10&id=2436627eb4644234a9e577538ec334d224e3d2be
[16:15] <seb128> xclaesse, e.g it's fine in 3.10 now, master needs apps to be fixed I think
[16:15] <xclaesse> ah
[16:15] <seb128> xclaesse, e.g https://git.gnome.org/browse/gtk+/commit/?id=b53b5578f351a26e9ed7898da71624c329f5a8b1
[16:16] <seb128> xclaesse, you probably need to set that property if you have a custom dialog
[16:18] <desrt> xclaesse: something is weird with telepathy-glib's build system
[16:19] <desrt> one change to a .c file should not cause so much rebuilding...
[16:19] <xclaesse> desrt, noticed that as well
[16:20] <xclaesse> if you have autotools super power, feel free to fix it :)
[16:21] <xclaesse> desrt, actually, does it really build lots of things? it seems to "just" relink all tests
[16:22] <xclaesse> and we have tons of them
[16:22] <desrt> indeed it seems you are correct
[16:22] <xclaesse> I think in glib make in ran in tests/ only when doing "make check"
[16:22] <xclaesse> which really makes sense
[16:24] <desrt> so pretty sure this is a telepathy-glib bug
[16:27] <desrt> ya... really quite sure, in fact
[16:27] <desrt> here's the issue
[16:27] <desrt> in the event of success, splice_stream_ready_cb() does nothing except to call g_io_stream_close_async with stream_close_cb as the handler.  that function does nothing (in terms of async ops)
[16:28] <desrt> however, in the failure case, you call operation_failed()
[16:28] <desrt> which calls g_simple_async_result_complete_in_idle() on self->priv->result
[16:28] <desrt> ie: why are you reporting an async result in one case but not the other?
[16:29] <desrt> the problem with the testcase is caused by another bug: when you dispatch the successful case of provide_file() you don't clear out self->priv->result when you're done
[16:29] <desrt> ie: you just say g_simple_async_result_complete_in_idle (self->priv->result); and return without dropping your ref on the result
[16:29] <desrt> which is a leak as well
[16:31] <desrt> if i fix those two issues then the test is passing again
[16:31] <desrt> i'll do up a patch
[16:33] <seb128> desrt, thanks!
[16:33] <seb128> xclaesse, ^^ in case you didn't follow the channel
[16:37] <xclaesse> desrt, cool thanks :)
[16:37] <seb128> jdstrand, hey, could you have a look to https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1257816? (not sure to understand apparmor there, shouldn't the current profile already give acces to the location listed)?
[16:37] <ubot2> Launchpad bug 1257816 in telepathy-mission-control-5 (Ubuntu) "the apparmor profile should allow access to avatars datas" [Low,New]
[16:40] <desrt> xclaesse, seb128: http://paste.fedoraproject.org/59010/38617520
[16:46] <xclaesse> desrt, there is indeed something wrong, I agree
[16:46] <xclaesse> desrt, I think there are even a lot more operation_failed()to remove
[16:46] <desrt> i do find it a bit alarming that the behaviour changed, though...
[16:47] <desrt> it might be interesting to investigate why that is, but this testcase is failing to do so... it only gets caught on these other snags :/
[16:48] <jdstrand> seb128: hey, responded in the bug
[16:48] <xclaesse> desrt, everything that happens in/after start_transfer() should not call operation_failed()
[16:49] <xclaesse> the operation is done when we gave the file to send to the CM
[16:49] <desrt> xclaesse: you're more familiar with the code than me, so i'd be more comfortable with you making any required additional changes
[16:49] <xclaesse> the actual streaming is not part of the operation
[16:49] <xclaesse> that's how I understand the code
[16:49]  * xclaesse moves discussion to #telepathy
[16:50] <xclaesse> desrt, but still, if we hit that, it is because the splice fails
[16:51] <xclaesse> desrt, your patch does not fix that, does it?
[16:51] <desrt> no
[16:51] <desrt> as i said -- it would be interesting to find a testcase that actually manages to discover why glib's behaviour changed here, and if it's valid or not
[16:51] <xclaesse> with that patch it will just silently print DEBUG ("splice operation failed: %s", error->message);
[16:52] <Sweetshark> seb128: around for a quick chat on the pending raring SRU?
[16:52] <seb128> jdstrand, thanks
[16:52] <seb128> Sweetshark, yes
[16:52] <Sweetshark> ^^ note the ping v 2.0 format
[16:54] <seb128> desrt, xclaesse: that patch is not working for me
[16:54] <Laney> pimp my ping
[16:54] <desrt> seb128: 'make check' passes here (in jhbuild)
[16:54] <seb128> desrt, http://paste.ubuntu.com/6520671/
[16:55] <desrt> more bugs!!!
[16:56] <xclaesse> desrt, I think it is racy
[16:57] <desrt> i assume self->priv->stream has already been cleared by this point
[16:57] <xclaesse> the unit test does not wait for the splice to actually happen
[16:57] <desrt> because obviously 'output' is legit
[16:57] <seb128> desrt, xclaesse: worked on a second try
[16:57] <desrt> xclaesse: your use of gmainloop here is super-sketchy too
[16:57] <xclaesse> the test exit when the splice operation starts
[16:57] <desrt> you should rather use while(wait)g_main_context_ieration();
[16:57] <xclaesse> then it doesn't wait for it to finish
[16:58] <desrt> although i guess since this is async and not threaded, this race does not really exist in this case
[16:58] <seb128> got it fail only once, I guess I got unlucky on first try
[16:58] <xclaesse> I'm surprised we have no test that actually to a complete file transfer
[16:59] <xclaesse> desrt, seb128: did you open a tp-glib bug already?
[16:59] <desrt> xclaesse: no.
[16:59] <seb128> xclaesse, desrt: I can do that
[16:59] <xclaesse> I don't know if glib has a bug, but that tp-glib code is clearly wrong
[17:00] <xclaesse> seb128, ok thanks, please do :)
[17:02] <seb128> xclaesse, desrt: https://bugs.freedesktop.org/show_bug.cgi?id=72319
[17:02] <ubot2> Freedesktop bug 72319 in tp-glib "test-file-transfer-channel fails with glib 2.39" [Normal,New]
[17:16] <Sweetshark> seb128: so SRUs are now precise->verified, raring->dropped, saucy->verified. queue clean.
[17:17] <seb128> \o/
[17:39] <xclaesse> desrt, I don't think glib is to blame, our code is completely broken by design... :(
[17:39] <xclaesse> it was not failing by chance because the unit test leave before the splice operation has a chance to return the error
[17:40] <xclaesse> but now splice seems faster to report error and it catch us
[17:57] <seb128> jdstrand, those lines seem to work, should I just upload the change or did you want to do it?
[17:58] <jdstrand> seb128: if you want to upload it, that's fine. I suggest adding them under:
[17:58] <jdstrand> owner @{HOME}/.cache/.mc_connections rw,
[17:59] <seb128> jdstrand, ok, doing that, thanks
[17:59] <seb128> jdstrand, I've a bug fix to upload so I can as well do both changes
[17:59] <jdstrand> cool, thanks! :)
[18:00] <seb128> yw!
[18:47] <seb128> happyaron, hey, how is the fix for https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1221593 going?
[18:47] <ubot2> Launchpad bug 1221593 in ibus (Ubuntu) "ibus-ui-gtk3 crashed with SIGABRT in _g_log_abort()" [High,Triaged]
[18:49] <seb128> chrisccoulson, https://errors.ubuntu.com/problem/fef869f3270e559cb31eba70138d662add193781 ... does it look like an Ubuntu bug to you or a bug in an extension? it's a file in ~/.mozilla/firefox/... which calls hunspell
[18:49] <seb128> chrisccoulson, oh, hey btw ;-)
[18:51] <sarnold> I love the Y axis ranging from 0.00 to 0.00 with the steps between clearly labeled :)
[18:51] <seb128> yeah...
[20:08] <robert_ancell> mterry, we need someone else to approve lightdm patches in your timezone.. Also, feel free to make releases if you need them
[20:08] <mterry> robert_ancell, it wasn't *that* urgent
[20:09] <mterry> robert_ancell, I know, London is even worse than normal
[20:09] <robert_ancell> ah, that's right
[20:09] <mterry> robert_ancell, stupid maguro always screwing things up
[20:09] <robert_ancell> :)
[20:09] <robert_ancell> Stupid VTs always screwing things up
[22:01] <ali1234> what is the upstream source for indicator-sound-gtk2?
[22:14] <kenvandine> ali1234, https://launchpad.net/indicator-sound
[22:15] <kenvandine> ali1234, i don't think the current trunk still builds for gtk2
[22:15] <kenvandine> there should be a maintenance branch for that
[22:15] <ali1234> it doesn't
[22:15] <ali1234> and the maintenance branch doesn't work, assuming it exists
[22:16] <ali1234> because the maintenance branch is really just "lol, here's the old version from raring, dunno if it works, lol"
[22:16] <ali1234> the reason it doesn't work is because -gtk2 and -gtk3 both use the same dbus backend, and changes in the dbus api weren't backported to the -gtk2 branch
[22:17] <kenvandine> ali1234, right, that is just for SRUs
[22:18] <kenvandine> ali1234, yeah, i think you would need dbusmenu and libindicator from raring as well
[22:18] <kenvandine> to build them
[22:18] <kenvandine> probably not possible with what's in trusty
[22:18] <ali1234> it's really odd because somebody went to the trouble of creating a whole new source package and uploaded it to saucy
[22:18] <kenvandine> interesting
[22:18] <ali1234> but apparently they went to all that effort and ten didn't even test if it actually works
[22:18] <kenvandine> i doubt it could work
[22:19] <ali1234> it doesn't, that's what i'm trying to tell you.....
[22:19] <ali1234> it hasn't worked for months
[22:19] <kenvandine> what needs it?
[22:19] <ali1234> there's is a monster 100 comment bug report for xubuntu, because this indicator is broken
[22:20] <ali1234> lubuntu also uses it
[22:20] <kenvandine> nothing in saucy should need it
[22:20] <ali1234> also ubuntu studio
[22:20] <kenvandine> so for something like that, you'd need the whole indicator stack built from the old sources
[22:20] <ali1234> yeah
[22:20] <ali1234> we know
[22:20] <kenvandine> libindicator, dbusmenu and not sure what else
[22:20] <kenvandine> ok
[22:20] <ali1234> we were going to ship -gtk3 indicator support in xubuntu saucy
[22:21] <kenvandine> so you need new sources for all those
[22:21] <ali1234> but that got broken by abi changes
[22:21] <ali1234> so it got delayed until trusty
[22:21] <kenvandine> bummer
[22:22] <ali1234> api changes in the indicators of course
[22:22] <ali1234> anyway, i rather doubt the whole stack needs to be downgraded
[22:22] <ali1234> it worked in raring
[22:22] <ali1234> the reason it's broken is because the dbus api has changed a tiny bit
[22:23] <ali1234> but i need to find the upstream source so i can see what actually changed