[03:12] <micahg> TheMuso: did you see GTK2 and GTK3 failed on i386?
[03:13] <TheMuso> micahg: Yes I did.
[03:13] <TheMuso> micahg: I suspect the version of glib that was uploaded before seb reverted it, but the reverted version probably hadn't been published in time...
[03:14] <micahg> TheMuso: yep, looks like it
[03:16] <TheMuso> Yeah pretty sure its glib related, because amd64 for GTK 2 built fine.
[03:17] <TheMuso> heh and even powerpc.
[03:17] <TheMuso> for GTK3 at least.
[03:17] <micahg> well, it looks like the new glib is published on i386 and powerpc
[03:17] <TheMuso> Yep
[03:18] <TheMuso> Going to retry them.
[03:18] <micahg> oh, and armhf, the old one 2.31.2 on amd64,armel
[03:18] <TheMuso> Grr this stuff gets messy at times. :S
[03:28] <TheMuso> Glib is weird in that it occasionally seems to get transient FTBFS issues... Seems it built fine second time around on amd64 after I verified it built locally.
[05:34] <desrt> TheMuso: one of the gdbus testcases is known to have an unknown race/deadlock in it
[05:34] <desrt> TheMuso: nobody has been able to get a backtrace for us, so we're unable to pin it down
[05:34] <desrt> TheMuso: add to this the fact that the failure only seems to happen on the launchpad builders.... possibly due to some weird interaction with the old kernel version
[05:36] <TheMuso> desrt: Yeah thought as much, seems if you kick it hard enough, it goes again. :p
[06:33] <pitti> good morning
[06:40] <TheMuso> pitti: Morning.
[08:25] <seb128> hey
[08:25] <pitti> hey seb128
[08:25] <seb128> hey pitti, how are you?
[08:26] <seb128> pitti, it's meeting reminder day!
[08:26] <seb128> ;-)
[08:26] <pitti> seb128: ah, thanks; still catching up with last night's tech board stuff and this morning's breakage :)
[08:27] <ricotz> good morning
[08:27] <seb128> pitti, what breakage? please tell me it's not something I did :p
[08:27] <pitti> hello ricotz, wie gehts?
[08:27] <ricotz> seb128, http://bazaar.launchpad.net/~ricotz/glib/ubuntu/revision/122
[08:27] <seb128> hey ricotz, how are you?
[08:27] <pitti> seb128: nah, vte3 broke everyone's gnome-terminal, but mterry already fixed that
[08:27] <ricotz> pitti, danke, gut, ich hoffe dir auch
[08:27] <seb128> pitti, ok
[08:27] <seb128> ricotz, thanks
[08:27] <pitti> seb128: and there was lots of uninstallability due to some component-mismatches
[08:27] <ricotz> seb128, i am fine, hoping you too
[08:27] <pitti> ricotz: oh ja, danke
[08:28] <seb128> ricotz, I'm good thanks
[08:28] <seb128> ricotz, no issue with the new glib? I uploaded by error to precise but decided I didn't feel comfortable with the few testing and reverted to the previous version by tweaking the number
[08:28] <ricotz> seb128, i had a look at the glib packaging and there was this missing include
[08:28] <seb128> ricotz, good catch!
[08:29] <ricotz> which will result in build failures if this packages isnt pulled
[08:29] <ricotz> seb128, i will update my precise package again, but i wont at the include-reversion
[08:30] <ricotz> s/at/add/
[08:30] <seb128> ricotz, I should add an hook to my builds to diff the .pc between versions ;-)
[08:30] <seb128> bah, between rickspencer3 and jibel we are bugs flooded :-(
[08:46] <chrisccoulson> lol, this is funny - https://twitter.com/#!/dolske/status/146449634301194240
[08:46] <chrisccoulson> good morning everyone
[08:47] <seb128> hey chrisccoulson, how are you?
[08:47] <chrisccoulson> hi seb128
[08:47] <chrisccoulson> i'm good thanks, just fixing that cursor bug ;)
[08:47] <chrisccoulson> how are you?
[08:48] <seb128> I'm good thanks
[08:48] <seb128> chrisccoulson, did you manage to get your debug symbols stuff sorted?
[08:49] <chrisccoulson> seb128, yeah, pretty much, although it got sidelined yesterday when i had to work on something else
[08:49] <chrisccoulson> today though ;)
[08:49] <seb128> does anyone here has a clue or interest for libgee or gegl or babl?
[08:49] <seb128> chrisccoulson, good ;-)
[08:50] <chrisccoulson> then it's on to scrollbars :)
[08:50] <seb128> hehe
[08:50] <chrisccoulson> or :( , not sure which ;)
[09:01] <pitti> hey chrisccoulson
[09:02] <chrisccoulson> hi pitti, how are you?
[09:02] <pitti> chrisccoulson: quite alright, now that the morning dust has settled
[09:02] <pitti> how are you?
[09:02] <chrisccoulson> pitti, yeah, good thanks. just about to make some coffee :)
[09:03] <seb128> pitti, there is a new pygobject tarball out but I guess you noticed?
[09:03] <pitti> seb128: ah, great
[09:03] <seb128> RAOF: hey, we are 1 version behind Debian and 3 versions behind upstream for colord, is there any chance you could do the update?
[09:03] <pitti> seb128: the new g-i is already in debian svn, waiting for testing migration
[09:03] <seb128> pitti, ok, well I'm looking to version
[09:04] <pitti> so, can do pygobject soon
[09:04] <seb128> pitti, we are being on polkit-gnome as well compared to Debian (though the new version doesn't seem to have lot) if you want to update that as well when you have free slots
[09:04] <pitti> *nod*
[09:14] <jibel> pitti, current blocker for main-all upgrade bug 903475
[09:14] <ubot2> Launchpad bug 903475 in openoffice.org "Failed to upgrade from Oneiric to Precise: E:Could not perform immediate configuration on 'openoffice.org-writer'" [High,New] https://launchpad.net/bugs/903475
[09:14] <pitti> jibel: right, on my list
[09:15] <pitti> jibel: but I had to revert the unixodbc fix again :( soprano-daemon needs porting first
[09:15] <pitti> jibel: fixing bug 902947 ATM, then looking at ^
[09:15] <ubot2> Launchpad bug 902947 in openthesaurus "package mythes-de 20110119-2ubuntu2 failed to install/upgrade: update-openoffice-dicts: not found" [High,In progress] https://launchpad.net/bugs/902947
[09:16] <jibel> pitti, ok, thanks
[09:31] <ricotz> seb128, speaking of new stuff, you want to keep this one in mind, libwacom -- http://cgit.freedesktop.org/~whot/libwacom/
[09:32] <seb128> ricotz, yeah, I noticed, another thing which made me glad we stay on 3.2 :p
[09:32] <ricotz> ;)
[09:33] <ricotz> of course packaging and adding it to the repo in this cycle would be nice
[09:33] <tjaalton> ricotz: does the driver depend on it?
[09:34] <ricotz> g-c-c uses it
[09:34] <Sarvatt> libwacom? hmm
[09:34] <tjaalton> ok
[09:34] <ricotz> but the input-driver could probably use it too
[09:35] <ricotz> tjaalton, it just looks for a wacom device and its capabilities
[09:36] <seb128> ricotz, I'm happy to sponsor your package if you work on one ;-)
[09:36] <ricotz> i already have one, not sure about the section
[09:36] <tjaalton> ricotz: ok
[09:37] <ricotz> sounds more like something for the xorg group
[09:37] <ricotz> seb128, so far there isnt a release yet
[09:38] <tjaalton> ricotz: I could package it
[09:40] <ricotz> tjaalton, i can send you my packaging if you want
[09:40] <tjaalton> ah good
[09:41] <ricotz> tjaalton, http://people.ubuntu.com/~ricotz/wacom/libwacom.tar.gz
[09:45] <tjaalton> ricotz: actually, since it's only used by the desktop environment(s), it fits better in the desktop-team category?
[09:46] <ricotz> tjaalton, yeah, that is what i am not sure about, maybe it will be used by other things too soon
[09:51] <Sarvatt> ricotz: xf86-input-wacom isnt even in pkg-xorg in the first place either :(
[09:52] <tjaalton> yeah, doubt ron will maintaina libwacom
[09:52] <tjaalton> -a
[09:55] <ricotz> Sarvatt, i see
[09:58] <Sarvatt> kind of a grey area, can see it needing to be updated in tandem with xf86-input-wacom when setting names change but its only going to be consumed by a gnome capplet or whatever they are called now
[10:00] <ricotz> Sarvatt, do you see any indications yet that input-wacom will use it?
[10:04] <Sarvatt> cant see any reason why it would, it's just wrapping stuff the driver does already in a more consumable form..
[10:05] <RAOF> seb128: Sure thing; I'll colord tomorrow.
[10:05] <Sarvatt> a wacom control panel applet is a very nice thing though :)
[10:05] <seb128> RAOF: thanks
[10:05] <ricotz> Sarvatt, yeah, which made me think they will make use of it instead of duplicating things
[10:05] <seb128> RAOF: how are you btw? ;-)
[10:06] <RAOF> Pretty good.
[10:06] <RAOF> Roughly caught up on email, just come back from a very nice dinner of paella for Sam's birthday.
[10:06] <Sarvatt> RAOF: is g-c-m working in precise? :)
[10:07] <Sarvatt> bring my huey to budapest!! :P
[10:07] <ricotz> RAOF, hey
[10:07] <RAOF> Sarvatt: I certainly will!  Sorry for forgetting it in Orlando :)
[10:07] <RAOF> ricotz: Whatup, dawg?
[10:08] <Sarvatt> RAOF: totally my fault, was locked up in a room working on OEM crap and didn't see you after I passed it off :)
[10:08] <ricotz> RAOF, just wanted to say hello :)
[10:08] <Sarvatt> except for when i left but yeah i forgot too then
[10:09] <RAOF> ricotz: Hi :)
[10:19] <RAOFer> Urgh.  My Intel laptop has suddenly decided that hard-locking every hour or so is a good idea.  Stupid i915.
[10:20] <bryceh> RAOFer, running stock ubuntu on it or edgers?
[10:20] <RAOFer> Stock Precise.
[10:21] <bryceh> RAOFer, ok, can you file a report please?
[10:21] <bryceh> RAOFer, is it a GPU lockup or just an ordinary kernel OOPS/BUG/etc.?
[10:21] <RAOFer> Yeah.  Sadly I've got *no* debugging data; this kills the kernel stone dead; nothing makes it to disc
[10:22] <RAOFer> I'll file the bug and spend some quality time with the netconsole documentation tomorrow.
[10:22] <RAOFer> (File the bug now, debugging info tomorrow)
[10:22] <bryceh> RAOFer, weird.  I've put 4 -intel systems on precise, updated 2x / wk, no problems like that.  Must be a magic-only bug?
[10:23] <RAOFer> Maybe.
[10:23] <RAOFer> Might also be DP-only.
[10:23] <bryceh> mm
[10:24] <bryceh> yeah there's been remarkably few gpu lockup bugs reported so far this cycle
[10:24] <bryceh> haven't even seen any of the false gpu lockups
[10:25] <bryceh> RAOFer, there is an Intel call tomorrow morning (which unfortunately I'll miss due to vacation) - might be good to escalate the bug to them prior to that
[10:26] <RAOFer> I'd like to have done at least *some* debugging before escalating.  I guess I can give a heads-up, though.
[10:27] <bryceh> RAOFer, so fwd the bug upstream and then email ickle or one of the other Intel guys
[10:28] <RAOFer> Yeah.
[10:31] <RAOFer> Grrrargh!  Apparently, it knows.  And would like to prevent me from filing a bug :)
[10:34] <bryceh> RAOFer, anti-magic!
[10:34] <RAOFer> It has become aware.  We must destroy it now!
[10:36] <RAOFer> Oooh boy that laptop could do with a clean install.  I'm not entirely sure what I've done to it, but it takes about a minute to log in.
[10:39] <pitti> RAOFer: does it also take a minute for a fresh user or a guest session?
[10:39] <bryceh> RAOFer, same laptop as the one experiencing the lockups?
[10:39] <pitti> RAOFer: first step there is to check if it's a broken system or a broken user account
[10:40] <RAOFer> bryceh: Yeah, same system.
[10:40] <RAOFer> pitti: Much faster into a guess session.
[10:40] <RAOFer> s/guess/guest/
[10:40] <pitti> RAOFer: so I guess a reinstall won't help, you need to check what's wrong in your user account :(
[10:41] <bryceh> RAOFer, aha, doing an upgrade is a great way of incurring anti-magic.
[10:41] <RAOFer> My x200s has been upgraded from... 10.10, I think.  It's been a champ until now :)
[10:45] <JamesTait> Good morning all. :)
[10:45] <JamesTait> Is this the right place to talk about some desktop breakage in Precise? I'd like to file bugs, but I could use some help picking apart what's happening so the bugs go to the right places.
[10:49] <JamesTait> In fact, it seems like it's just my system themes that are broken. I'm missing icons (Nautilus, Terminal, Gwibber action icons), the widgets look like stock GTK2 widgets, my panel is the wrong colour  and my session indicator is not displayed (due to no icon, I think) although it is reachable via F10.
[10:50] <chrisccoulson> glatzor, the problem i mentioned with aptdaemon yesterday seems to happen with software-center too (it sees timeouts when trying to talk to it too, and won't let me install anything)
[10:50] <pitti> hm, gnome-settings-daemon crash? but that wouldn't explain all symptomps, only most
[10:50] <pitti> JamesTait: ^
[10:50] <chrisccoulson> is there anything i can do to debug that?
[10:50] <pitti> JamesTait: does a guest session work?
[10:50] <pitti> JamesTait: also, is gnome-settings-daemon running?
[10:51] <JamesTait> pitti: I have /usr/lib/gnome-settings-daemon/gsd-printer and gnome-fallback-mount-helper
[10:51] <pitti> JamesTait: can you try running "gnome-settings-daemon" from a terminal and see what happens?
[10:52] <glatzor> chr1sccoulson, hello, you can run "sudo aptd -td --replace" in a terminal to get some output from software-center
[10:52] <glatzor> from aptdaemon :)
[10:52] <seb128> JamesTait, can you pastebin your .xsession-errors?
[10:53] <JamesTait> pitti: I think I raised a bug about this last night, actually - I didn't make the connection.
[10:53] <glatzor> chr1sccoulson, but you have to close fotware-center before
[10:54] <glatzor> chr1sccoulson, ah now i also get the same behavior
[10:55] <JamesTait> pitti: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/903483
[10:55] <ubot2> JamesTait: Error: <Bugtracker.plugin.Launchpad instance at 0x9083dec> bug 903483 not found
[10:55] <pitti> JamesTait: ah, that would be due to the new development glib
[10:55] <pitti> seb128: ^ Settings schema 'org.gnome.nautilus.nautlius.extensions.ubuntuone' is not installed
[10:56] <pitti> JamesTait: try installing ubuntuone-client-gnome
[10:56] <seb128> pitti, heh, no, that would be due to ubuntuone
[10:56] <pitti> /usr/share/glib-2.0/schemas/nautilus-ubuntuone.gschema.xml
[10:56] <pitti> oh, WTH
[10:56] <seb128> pitti, whatever use a key from that schemas should depends on it
[10:56] <pitti> "nautlius"?
[10:56] <pitti> and nautilus.nautlius?
[10:57] <seb128> that seems a very buggy software ;-)
[10:57] <pitti> seb128: weird, why doesn't it crash here then?
[10:57] <seb128> JamesTait, dpkg -l | grep ubuntuone
[10:57] <chrisccoulson> glatzor, http://paste.ubuntu.com/768820/
[10:57] <JamesTait> pitti: It is installed.
[10:57] <chrisccoulson> it actually seems to see nothing at all :/
[10:57] <glatzor> chr1sccoulson, but there haven't been any changes to aptdaemon for about two weeks
[10:57] <seb128> pitti, ^ I bet it's a daily ppa or something
[10:57] <pitti> JamesTait: which version do you have?
[10:57] <glatzor> mvo, ping
[10:58] <JamesTait> seb128, pitti: For reference, I'm on the U1 team, so I run from the U1 nightlies PPA and also have the U1 hackers private PPA.
[10:58] <JamesTait> So ubuntuone-client-gnome is 3.1+r10-46~precise1
[10:58] <seb128> pitti, that typo is in the .convert merged in https://code.launchpad.net/~dobey/ubuntuone-client-gnome/gsd-schema/+merge/76771
[10:59] <mvo> hey glatzor
[10:59] <pitti> JamesTait: so that bug might be just for you then :)
[10:59]  * JamesTait goes to get the .xsession-errors
[10:59] <pitti> JamesTait: I updated it
[10:59] <JamesTait> pitti: I think the same bug is affecting mandel, but he's also on the team. ;)
[11:00] <JamesTait> Maybe worth backing out ubuntuone-client-gnome to the repo version?
[11:00] <pitti> JamesTait: at least it doesn't seem to happen with current precise, yes
[11:03] <glatzor> hello mvo, aptdaemon seems to not respond anymore http://paste.ubuntu.com/768820/
[11:03] <JamesTait> pitti: Indeed - I just downgraded ubuntuone-client-gnome and my desktop is beautiful again.
[11:03] <mandel> JamesTait, so, is there a public bug for this?
[11:03] <pitti> JamesTait: so, happy typo fixing :)
[11:04] <JamesTait> pitti: Oh, and ran gnome-settings-daemon
[11:04] <pitti> mandel: bug 903483
[11:04] <ubot2> Launchpad bug 903483 in ubuntuone-client-gnome "gnome-settings-daemon crashed with signal 5 in g_object_newv()" [Medium,New] https://launchpad.net/bugs/903483
[11:04] <mandel> JamesTait, do I just have to downgrade the package?
[11:04] <seb128> JamesTait, to what version did you downgrade?
[11:05] <JamesTait> mandel: Yes, I just did sudo apt-get install ubuntuone-client-gnome=2.0.1-0ubuntu3 and then ran gnome-settings-daemon
[11:05] <JamesTait> seb128: ^^
[11:05] <pitti> precise has 2.0.1-0ubuntu3
[11:05] <pitti> and that's working fine
[11:05] <seb128> so NOTUBUNTU
[11:05] <seb128> seems lile a bug in your (u1) daily builds
[11:06] <JamesTait> Looks like it, yes.
[11:06] <pitti> we need to package nautlius
[11:06] <seb128> pitti, ;-)
[11:06] <JamesTait> A little nautlius (sic) typo.
[11:06] <pitti> JamesTait: also, org.gnome.nautilus.nautilus... doesn't look right
[11:06] <pitti> org.gnome.nautilus.extensions.ubuntuone seems better
[11:07] <seb128> it's weird
[11:07] <seb128> https://code.launchpad.net/~ubuntuone-control-tower/ubuntuone-client-gnome/trunk has no recent commit
[11:07] <seb128> nothing that could explain the bug
[11:08] <JamesTait> I have to wonder if gsd couldn't be more robust against this kind of thing as well though.
[11:08] <pitti> it's glib
[11:08] <pitti> during development releases we get those crashes precisely to make these kinds of errors much more obvious
[11:08] <pitti> otherwise they would just be hidden, forgotten, and the breakage is more suble
[11:09] <pitti> such as settings not actually working
[11:09] <pitti> "subtle"
[11:09] <JamesTait> I'll caveat that heavily with "I know nothing about desktop development".
[11:09] <pitti> well, that's upstream glib's justification
[11:09] <JamesTait> :)
[11:09] <pitti> and as long as we disable that assertion for the final release, I must say I fully agree
[11:09] <pitti> otherwise we'll never find all those
[11:10] <pitti> that error message is just about perfect
[11:10] <JamesTait> Well, yes - as mandel said earlier, this is an alpha, after all.
[11:11] <JamesTait> So I'm a very happy chap now then.
[11:11] <mandel> yeah, I'm not surprised this happened, and the fix is easy enough :)
[11:11] <mandel> ok, I'm back to work then, JamesTait pitti thx for the help!
[11:11] <pitti> mandel: YW!
[11:11] <JamesTait> Yep, me too.
[11:12] <JamesTait> Thanks pitti, seb128. :)
[11:12] <pitti> de rien
[11:14] <seb128> hum, "fix"
[11:14] <seb128> pitti, mandel: did you actually find where is the typo?
[11:14] <seb128> trunk has no commit for a month, it's a bit weird
[11:14] <pitti> seb128: I didn't look
[11:15] <seb128> pitti, ok, I will let the u1 guys sort it
[11:16] <mandel> seb128, let me try to take a look
[11:16] <mandel> seb128, at the end of the day, I'm in the desktop team of u1 :)
[11:16] <seb128> ;-)
[12:08] <pitti> seb128: pygobject 3.0.3 updated in pkg-gnome, but can't upload to debian yet
[12:08] <pitti> seb128: do you want an upload to Ubuntu now, or is it ok on Thursday, when the whole stack (hopefully) goes to testing?
[12:38] <seb128> pitti, your call, I don't "need" an update for any bug fix or particular reason out of red lines on versions ;-)
[12:45] <chrisccoulson> glatzor, i tried downgrading aptdaemon btw, and the last one to work correctly on my machine is 0.43+bzr703-0ubuntu1
[12:45] <chrisccoulson> 0.43+bzr712-0ubuntu1 doesn't work (including the ability to install anything from software-center)
[12:53] <glatzor> chr1sccoulson, quite strange. Running from trunk works for you? bzr branch lp:aptdaemon and then sudo ./aptd -td --replace
[13:05] <chrisccoulson> glatzor, ok, will try the latest trunk too
[13:05] <chrisccoulson> btw,the last working revision between those 2 versions is r709
[13:05] <chrisccoulson> it seems to be this one which breaks it: http://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/main/revision/710
[13:08] <chrisccoulson> glatzor, the latest trunk is also still broken
[13:12] <glatzor> thanks chr1sccoulson
[13:13]  * rodrigo_ lunch
[13:15] <glatzor> chr1sccoulson, I am away but will have a look at it later
[13:15] <chrisccoulson> glatzor, excellent, thanks :)
[13:20] <rye> hm, what if I get bold Ubuntu font in QT applications in Oneiric and Precise - bug #744812. ttf-ubuntu-font-family: 0.80-0ubuntu1+console
[13:20] <ubot2> Launchpad bug 744812 in ubuntu-font-family-sources "FontConfig/Qt stack choke on Ubuntu Medium font meta-data (No medium in Inkscape and too bold in Qt apps)" [High,Fix released] https://launchpad.net/bugs/744812
[13:57] <pitti> seb128: btw, I have an appointment this afternoon, so if someone wants to do a meeting, could you drive it?
[13:59] <glatzor> chr1sccoulson, sorry, but I cannot reproduce the error on trunk. s-c also hangs on your computer?
[14:00] <seb128> pitti, sure, I can do that ;-)
[14:03] <pitti> seb128: merci
[14:04] <seb128> pitti, de rien ;-)
[14:21] <chrisccoulson> hi glatzor
[14:21] <chrisccoulson> yeah, it hangs software-center here
[14:28] <glatzor> chr1sccoulson, you can also reproduce the error running from the soure repository? could be an issue with dbus activation
[14:30] <chrisccoulson> glatzor, ah, are you running ubuntu or debian?
[14:31] <chrisccoulson> i've just figured out that if i kill indicator-session-service, then it works ;)
[14:31] <chrisccoulson> indicator-session-service seems to talk to it as soon as it comes on the bus, which seems to be the trigger for it breaking
[14:31] <chrisccoulson> hah
[14:31] <chrisccoulson> yeah, it works fine now i've killed that
[14:37] <kenvandine> chrisccoulson, does that just make it really busy right away then?
[14:37] <seb128> chrisccoulson, unity hater! ;-)
[14:37] <kenvandine> or do you think something is blocking?
[14:38] <chrisccoulson> kenvandine, no, it just seems to end up being completely unresponsive to anything
[14:38] <chrisccoulson> seb128, it's all DX fault ;)
[14:38] <seb128> kenvandine, well I know that glatzor said indicator-session should be updated to use the pk interface
[14:39] <seb128> the way they are trying to check if updates are available is a hack because aptd wasn't providing the interfaces required to do it properly but it does in the current version
[14:39] <seb128> so somebody needs to fix indicator-session
[14:39] <chrisccoulson> yeah, i'm starting to realize that as i'm looking through the indicator-session code ;)
[14:39] <kenvandine> seb128, do you know if there is already a bug filed for that? if not I'll file one
[14:39] <seb128> glatzor, ^ did you file a bug about that?
[14:40] <seb128> kenvandine, no bug that I know about, I asked glatzor to open one when he mentioned it but I didn't see one in my bug emails
[14:40] <chrisccoulson> i'm guessing the fact that indicator-session seems to kill aptdaemon is probably still an aptdaemon bug though :)
[14:40] <seb128> chrisccoulson, yeah, and the fact that old version don't have the issue suggest that it used to handle it better
[14:41] <kenvandine> yeah, but i don't want to let it fall through the cracks
[14:41] <kenvandine> i'll make sure there is one
[14:41] <chrisccoulson> seb128, right. it stopped working at this change: http://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/main/revision/710
[14:42] <seb128> kenvandine, seems like glatzor didn't open a bug, you should probably do it
[14:42] <seb128> then we should talk to dx about fixing bugs ;-)
[14:42] <chrisccoulson> lol
[14:42] <kenvandine> on my todo list for today... :)
[14:43] <seb128> kenvandine, thanks ;-)
[14:43] <seb128> chrisccoulson, speaking of bug fixing is my indicator bug fixed yet? ;-)
[14:43] <chrisccoulson> seb128, i will get to it ;)
[14:43] <chrisccoulson> i'm turning in to DX!
[14:44] <desrt> seb128: bad upload?
[14:44] <seb128> desrt, I hate glib :p
[14:44] <desrt> what now?
[14:44] <seb128> desrt, can't get it to build, it hangs in the testsuit every time
[14:44] <chrisccoulson> hah, running the old glib was the first thing i tried when i realized aptdaemon didn't work
[14:44] <desrt> it built on your machine?
[14:44] <chrisccoulson> just in case ;)
[14:45] <desrt> seb128: same gdbus case?
[14:45] <seb128> desrt, https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages?field.name_filter=glib
[14:45] <seb128> desrt, no, "codegen-peer-to-peer", seems new
[14:45] <seb128> on both amd64 and i386
[14:45] <desrt> sigh.
[14:46] <nessita> hello everyone! quick question, is there any procedure I can follow to have this package https://launchpad.net/ubuntu/precise/+source/qt4reactor available for oneiric and natty?
[14:46] <seb128> desrt, well, I built without make check there because I wanted to have it running earlier, I should do a try with make check, I just got busy with other things today
[14:46] <seb128> nessita, https://wiki.ubuntu.com/UbuntuBackports
[14:46] <seb128> nessita, hey btw ;-)
[14:46] <desrt> seb128: you really need to get a backtrace one of these days :p
[14:47] <chrisccoulson> is it reproducible on one of the porter boxes?
[14:47] <seb128> desrt, yeah, I need to talk to lamont or somebody, I've no clue if we can get,how to get a stacktrace from a buildd
[14:47] <desrt> evil gdbus.
[14:47] <desrt> glad it wasn't my stuff that broke it, at least :)
[14:47] <nessita> hola seb128!
[14:48] <nessita> seb128: so backports is the only way? there is no way to have it in the universe repo?
[14:48] <BigWhale> When you connect the camera to USB and you open it in nautilus nautilus will start making previews of all the files on the camera... is there a way to turn off this? because it hinders file transfer
[14:48] <seb128> nessita, we don't add new stuff to old version usually, people who need it can get it from backport
[14:49] <seb128> BigWhale, you can turn off thumbnailing but not in a specific way for cameras or some locations
[14:49] <BigWhale> disturbing
[14:49] <BigWhale> :/
[14:49] <seb128> you can go to the nautilus preferences, turn it off, copy and then on again I guess
[14:49] <nessita> seb128: ack, duly noted. Thanks!
[14:50] <BigWhale> yeah, I know that. I'd love to have this per device or per folder specific
[14:50] <seb128> bug #673140
[14:50] <ubot2> Launchpad bug 673140 in gvfs "gvfsd-gphoto2 loads previews for all files regardless of settings in Nautilus for previewed file size" [Low,Incomplete] https://launchpad.net/bugs/673140
[14:50] <seb128> ups, wrong bug
[14:51] <seb128> BigWhale, bug #886323 for example
[14:51] <ubot2> Launchpad bug 886323 in nautilus "Thumbnail Creation on Digital Camera Slows System and Crashes Nautlilus" [Low,New] https://launchpad.net/bugs/886323
[14:51] <seb128> nessita, yw ;-)
[14:52] <seb128> but I'm pretty sure it's a duplicate of an older bug
[14:53] <seb128> ricotz, btw did you get those "codegen-peer-to-peer" test hangs in your glib ppa builds?
[15:02] <ricotz> seb128, yes, both tests i disabled there were leading to hangs (caused by the same reason)
[15:06] <seb128> ricotz, did you report that upstream? is that specific to ppas again or does it happen locally?
[15:07] <seb128> desrt, ^
[15:07] <ricotz> seb128, afaik, this is the same gdbus problem
[15:09] <ricotz> (havent seen it locally)
[15:10] <seb128> ok
[15:10] <ricotz> seb128, i have resynced totem package in gnome3-ppa
[15:10] <seb128> ricotz, btw I don't get the g-c-c grid corruption bug with your ppa gtk version so I assume it has been fixed since
[15:11] <seb128> ricotz, you have no idea around when it stopped for you?
[15:11] <ricotz> seb128, sorry, no
[15:11] <seb128> ok
[15:11] <desrt> there was a dbus change that i was concerned would introduce subtle problems like this
[15:11] <seb128> ricotz, "resynced"? on debian you mean?
[15:11] <ricotz> pitti, could you bump these builds https://launchpad.net/~gnome3-team/+archive/gnome3/+packages?field.name_filter=totem&field.status_filter=published&field.series_filter=
[15:11] <ricotz> seb128, synced with ubuntu
[15:11] <ricotz> it was base on ubuntu5
[15:12] <seb128> desrt, ricotz: well the hang was random before, it happened several retries in a row on both i386 and amd64 there
[15:12] <seb128> ricotz, ok, thanks
[15:12] <desrt> but never locally
[15:12] <ricotz> seb128, and it needed a rebuild anyway after the nautilus changes
[15:13] <desrt> seb128: i'm getting really close to thinking the kernel used on the builders has some weird bug
[15:13] <desrt> seb128: because this problem never happens anywhere else ever
[15:13] <seb128> desrt, hum ok, "fun"
[15:13] <ricotz> desrt, yeah, it is an old kernel too :\
[15:13] <chrisccoulson> which kernel is it?
[15:14] <ricotz> 2.6.24
[15:14] <desrt> 2.6.27 or so
[15:14] <desrt> oh.  even older, then
[15:14] <ricotz> (at least my xorg.0.log says so ;) )
[15:15] <chrisccoulson> oh, probably explains why i'm wasting my time on a porter box, where it works every time ;)
[15:15] <desrt> that's 4 years old
[15:15] <chrisccoulson> 2.6.32
[15:15] <desrt> people weren't using threads back then like we are now
[15:15] <desrt> could easily be some subtle issues there
[15:15] <seb128> chrisccoulson, did you try to debug that glib issue?
[15:16] <seb128> ok
[15:16] <chrisccoulson> seb128, i just tried it on osageorange, just on the off-chance it might hang there. but i didn't realize that the buildd kernels were even older
[15:16] <desrt> plus... glib threading already found a confirmed bug in the libc... so why not the kernel? :)
[15:16] <seb128> chrisccoulson, ok
[15:17] <seb128> so, anyone here again uploading gtk 3.3.4 to precise today?
[15:17] <chrisccoulson> seb128, i have a bunch of firefox test hangs too, and i can recreate those on the porter boxes :)
[15:17] <seb128> desrt, chrisccoulson, ricotz, pitti, mterry, cyphermox: ^
[15:17] <seb128> kenvandine, ^
[15:17] <pitti> ricotz: done
[15:17] <desrt> seb128: i hear ricotz has a plan to wait until after you start building it locally and then do a PPA upload
[15:17] <seb128> i.e anyone knows a good reason to wait for next year rather?
[15:17] <pitti> seb128: not me
[15:17] <mterry> heyo!
[15:18] <pitti> I need to leave in 10 mins
[15:18] <seb128> pitti, don't worry I don't ask you to do the update :p
[15:18] <kenvandine> seb128, maybe
[15:18] <mterry> seb128, what do you want?  peeps to test the ubuntu-desktop PPA?
[15:18] <seb128> mterry, no, just asking if anyone has an object against us going with the new gtk today
[15:19] <kenvandine> seb128, were you asking if we could upload it or if we already have plans to?
[15:19] <pitti> so, good night everyone!
[15:19] <kenvandine> no objection
[15:19] <seb128> 'night pitti
[15:19] <kenvandine> good night pitti
[15:19] <mterry> pitti, bye!
[15:19] <seb128> kenvandine, I've it ready for upload, it's in the gnome3-team ppa for a week
[15:19] <seb128> well the amd64 built failed there
[15:19] <mterry> seb128, I used to work in OEM, you know I'm all for pushing buttons :)
[15:19] <seb128> lol
[15:19] <kenvandine> mterry, lol
[15:19] <seb128> ok, so let's upload that
[15:19] <kenvandine> woot :)
[15:20] <chrisccoulson> right, i need to pop out for a few minutes to find a new bulb for my desk lamp
[15:20] <seb128> it breaks at least the gnome-control-center spacing
[15:20] <chrisccoulson> it's way to dark in here
[15:20] <kenvandine> it has a higher version number, it must be better!
[15:20] <seb128> but that's the only issue I noticed
[15:20] <seb128> but that seems to be fixed in git builds from ricotz
[15:20] <seb128> so I'm not too woried about it
[15:27] <ricotz> pitti, thanks
[15:27] <ricotz> desrt, ;)
[16:29] <ricotz> seb128, seems like the archive was in a bad state for the totem precise-amd64 build, do you know who can bump the build again?
[16:31] <seb128> ricotz, https://launchpad.net/~launchpad-buildd-admins
[16:31] <seb128> the people in this team
[16:31] <ricotz> seb128, thanks
[16:31] <seb128> ricotz, yw
[16:32] <seb128> bryceh, chrisccoulson, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, tkamppeter, pedro_, desrt, agateau, Sweetshark: it's meeting time
[16:32] <ogra_> rickspencer3, https://wiki.ubuntu.com/ArchiveAdministration#Archive_days
[16:32] <seb128> does anyone has a topic or something to discuss?
[16:32] <ogra_> see the schedule
[16:32] <cyphermox> o/
[16:32] <seb128> ogra_, wrong nick
[16:32] <kenvandine> hey
[16:32] <ogra_> yeah, sorry rick
[16:32] <kenvandine> nothing from me
[16:32] <ogra_> ricotz, https://wiki.ubuntu.com/ArchiveAdministration#Archive_days see the schedule
[16:33] <seb128> ogra_, and archive admins can't bump builds scores
[16:33] <Riddell> hi
[16:33] <ogra_> oh, crap i always mix these up :(
[16:34] <cyphermox> seb128: well, it's simple; planning to upload NetworkManager soon, but waiting for a transition in Debian, though I just might have it synced from experimental and do the build-deps fixes to the 10 or so packages that need it myself
[16:35] <cyphermox> (it == libnl3)
[16:37] <seb128> cyphermox, we are in sync with Debian now?
[16:37] <seb128> thanks for the notice
[16:37] <cyphermox> seb128: not NM, though it's close enough
[16:37] <seb128> on the same line I updated gtk to the unstable serie, I hope it's not going to create any issue for what others are doing
[16:37] <seb128> cyphermox, ok
[16:37] <cyphermox> seb128: libnl3: we mostly are, and will be with 3.2.3, since the patch we carry was from upstream
[16:38] <cyphermox> (and I did most of the packaging work for 3.2.3, I know it works on Ubuntu)
[16:39] <chrisccoulson> back
[16:39] <chrisccoulson> and can't stop sneezing!
[16:40] <seb128> chrisccoulson, you got a cold?
[16:40] <seb128> cyphermox, thanks for the update?
[16:40] <seb128> did anybody else had any topic?
[16:40] <chrisccoulson> seb128, i hope not, but it does feel like it
[16:40] <chrisccoulson> i could do without being ill again :)
[16:41] <seb128> chrisccoulson, tonight for you hot tea and early sleep then! ;-)
[16:41] <chrisccoulson> heh
[16:41] <chrisccoulson> "early sleep", what's that? :)
[20:28] <seb128> desrt, there?
[20:29] <desrt> yup
[20:30] <seb128> desrt, ok, so somewhat the new glib makes the build hang every single time, I got somebody from #is trying to get a stacktrace
[20:30] <desrt> thanks
[20:30] <seb128> desrt, do you know if attaching gdb to the hanging process will be enough to get the debug symbols?
[20:30] <seb128> i.e will it try to use the local library or the system one?
[20:31] <desrt> it should be smart enough
[20:31] <seb128> ok
[20:31] <seb128> let's see, he's trying to get the infos
[20:32] <seb128> desrt, but we got it 3 times in a row on amd64 and i386 so at least it's consistent and less racy with the new version ;-)
[20:32] <desrt> seb128: i have a patch that you can try to revert :)
[20:32] <desrt> (although i think that another test may begin to deadlock if you do so)
[20:32] <seb128> desrt, well I can abuse the ppa builders for testing
[20:33] <chrisccoulson> perhaps our porter boxes should be the same environment as the buildd's :)
[20:34] <desrt> seb128: this is the one i'm suspicious about: http://git.gnome.org/browse/glib/commit/?id=70dacf83d23ed468ff60972fd166769482d7195f
[20:34] <seb128> desrt, thanks
[20:35] <desrt> seb128: unfortunately, that was introduced to solve a deadlock elsewhere
[20:35] <desrt> seb128: the menumodel exporter, iirc
[20:35] <desrt> seb128: so better disable those tests if you revert that patch :)
[20:36] <desrt> (and i wouldn't consider the resulting glib to be usable... i'm just saying that you could test a theory this way)
[20:37] <seb128> desrt, bt is http://pastebin.ubuntu.com/769405/ I've asked a t a a bt
[20:38] <desrt> ya.  not so helpful, that one :)
[20:38] <desrt> "oh look.  it looks like every program ever." :)
[20:38] <seb128> ;-)
[20:41] <seb128> desrt, http://pastebin.ubuntu.com/769408/ still doesn't seem useful? :-(
[20:43] <seb128> desrt, ?
[20:44] <desrt> seb128: i see it and i'm inclined to agree
[20:44] <seb128> desrt, is there anything else he could get?
[20:44] <chrisccoulson> would getting the test to set G_DBUS_DEBUG=all in its environment help you get a better idea of where it stops working?
[20:44] <chrisccoulson> it would dump a lot of information to the build log
[20:44] <desrt> seb128: a core and a tarball? :)
[20:44] <desrt> (of the build directory)
[20:45] <desrt> at least we have some kind of vaguely clues now
[20:45] <desrt> *vague
[20:45] <seb128> desrt, lol, what else do you think you would get from it?
[20:45] <desrt> seb128: i don't know
[20:45] <desrt> seb128: but after i start digging in, i might
[20:45] <seb128> desrt, do we? it's stucked in a poll() how is that useful?
[20:46] <desrt> seb128: oh.  you're right.
[20:46] <desrt> that second thread is the dbus worker thread
[20:47] <desrt> i was hoping that it would be some testcase thread stuck in a maincontext iteration that i could look closer at :p
[20:47] <seb128> desrt, would chrisccoulson's G_DBUS_DEBUG=all suggestion be of any use?
[20:48] <desrt> it certainly wouldn't hurt
[20:48] <desrt> i'd turn it down to =message though
[20:48] <desrt> and try only to do it for that one test
[20:48] <desrt> otherwise the log is going to be a monster
[20:48] <chrisccoulson> heh
[20:49] <seb128> would be a good launchpad stress test? :p
[20:50] <chrisccoulson> i did have a test hang that ended up stuck in a tight loop printing the same message to the console
[20:50] <chrisccoulson> filling the disk up quite quickly :)
[20:50] <seb128> desrt, I think I will not ask for a dump and tarball, I wasted enough of your time on it, if that's really a kernel issue I think we should just comment the testcases hitting it
[20:51] <seb128> chrisccoulson, you seem to have some experience in stressing out the buildds ;-)
[20:51] <chrisccoulson> seb128, yeah, they hate me
[20:51] <desrt> seb128: i'm going to take a look at the testcase to see if i can find any obvious races there
[20:51] <chrisccoulson> they would hate me even more if i maintained libreoffice :)
[20:51] <seb128> chrisccoulson, if you made me build firefox daily I would hate you as well :p
[20:51] <desrt> another issue could be that the builders are more heavily loaded
[20:51] <desrt> so things get scheduled differently and some race happens
[20:52] <chrisccoulson> i'm wondering whether to set up a hardy install in virtualbox :)
[20:53] <seb128> chrisccoulson, stop it, you have enough to do ;-)
[20:53] <seb128> like you could fix my indicator bug :p
[20:53] <chrisccoulson> lol
[20:53] <seb128> or the tb spam indicator bug
[20:53] <seb128> or g-s-d ;-)
[20:53] <chrisccoulson> i can fix that after feature freeze can't i? ;)
[20:53] <seb128> or make the scrollbars
[20:53] <seb128> or
[20:53] <seb128> will stop there :p
[20:54] <chrisccoulson> right, i'm moving my laptop downstairs
[20:55] <chrisccoulson> i might get cut off when i undock and my session freezes ;)
[20:57] <chrisccoulson> it worked :)
[20:57] <seb128> chrisccoulson, ;-)
[20:58] <seb128> desrt, http://paste.ubuntu.com/769429/
[20:58] <seb128> desrt, the amd64 hang, seems similar to the previous one which was i386
[21:01] <desrt> seb128: thanks for the attempts
[21:02] <seb128> desrt, yw, sorry it's not useful
[21:05] <seb128> desrt, strace says
[21:05] <seb128> " Process 3126 attached with 2 threads - interrupt to quit
[21:05] <seb128>  [pid  3126] restart_syscall(<... resuming interrupted call ...> <unfinished ...>
[21:05] <seb128>  [pid  3150] restart_syscall(<... resuming interrupted call ...> <unfinished ...>"
[21:06] <desrt> no surprise there.  that's what it says when you connect it in the middle of a poll() call :)
[21:06] <seb128> indeed
[21:06] <seb128> desrt, but I'm out of ideas :p
[21:07] <desrt> tell lamont to kill the build, then
[21:07] <seb128> desrt, well I guess I will just do an upload commenting the other testcase and ask them to stop the builds
[21:07] <desrt> seb128: sounds like a good course of action
[21:07] <seb128> desrt, thanks and sorry for wasting your time
[21:07] <desrt> seb128: i could say the same :)
[21:08] <seb128> ;-)
[22:04] <jasoncwarner_> RAOF TheMuso bryceh hey guys...meeting time. https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-12-13
[22:04] <jasoncwarner_> please be sure to update the wiki and add agenda items, if any
[22:05] <jasoncwarner_> robert_ancell just mentioned time for meeting...add your items to wiki and agenda items if you have any
[22:05]  * TheMuso has done so.
[22:07] <chrisccoulson> seb128, i've just set up a precise chroot on a hardy install ;)
[22:08] <seb128> chrisccoulson, \o/
[22:08] <chrisccoulson> i wonder what will happen
[22:08] <chrisccoulson> need to get everything installed in the chroot now
[22:08] <TheMuso> chrisccoulson: Why would you do that?
[22:08] <chrisccoulson> TheMuso, seeing if i can get glib tests to hang
[22:09] <RAOF> Aaah.
[22:10] <jasoncwarner_> FYI RAOF TheMuso bryceh and robert_ancell , no agenda items so moving on from meeting. :)
[22:10] <robert_ancell> \o/
[22:10] <RAOF> :)
[22:11] <TheMuso> Cool.
[22:11] <TheMuso> chrisccoulson: aaaaah.
[22:12] <RAOF> To colord, QA testing, and figuring out why all my technology suddenly hates me!
[22:15] <chrisccoulson> hmmm, first thing to install in the chroot - bash-completion!
[22:16] <chrisccoulson> and vim!
[22:18] <TheMuso> lol
[22:28] <chrisccoulson> wow, my laptop is using 42W with virtualbox running
[22:29] <seb128> hum, dsl disconnect
[22:29] <RAOF> Mmm, toasty warm!
[22:29] <seb128> robert_ancell, hey
[22:29] <robert_ancell> seb128, hello
[22:29] <chrisccoulson> RAOF, yeah, it's starting to burn my leg
[22:29] <seb128> robert_ancell, guess you didn't get what I was saying when I disconnected?
[22:29] <chrisccoulson> seb128, got glib building now ;)
[22:29] <seb128> robert_ancell, I wanted to point bug #902698
[22:29] <ubot2> Launchpad bug 902698 in lightdm "lightdm crashed with SIGSEGV in check_stopped()" [High,Confirmed] https://launchpad.net/bugs/902698
[22:29] <seb128> robert_ancell, it's collecting some precise dups, it's a bit weird since lightdm didn't change there?
[22:30] <seb128> robert_ancell, dunno if that's due to the new glib or something but if you could check today?
[22:30] <seb128> chrisccoulson, great ;-)
[22:30] <robert_ancell> seb128, ok, will have a look
[22:30] <seb128> robert_ancell, thanks
[22:30] <seb128> chrisccoulson, https://bugzilla.gnome.org/show_bug.cgi?id=666129
[22:30] <ubot2> Gnome bug 666129 in build "the testsuit is hanging in gdbus tests" [Normal,Unconfirmed]
[22:30] <seb128> chrisccoulson, it's the upstream bug if you want to add infos
[22:31] <chrisccoulson> thanks
[22:31] <chrisccoulson> fingers crossed it hangs here
[22:31] <chrisccoulson> there's still no guarantee ;)
[22:32] <seb128> bug #870297 is weird
[22:32] <ubot2> Launchpad bug 870297 in lightdm "Lightdm logins not being logged in wtmp" [Low,Confirmed] https://launchpad.net/bugs/870297
[22:32] <chrisccoulson> hmmm, i think i'm going to have to look for my charger
[22:32] <chrisccoulson> i can normally go a whole evening in the lounge without it, but not tonight
[22:34] <seb128> lol
[22:34] <seb128> go glib go ;-)
[22:36] <robert_ancell> seb128, yeah, I have no idea about the wtmp stuff
[22:41] <chrisccoulson> having a SSD and 8GB of RAM really helps when running a VM :)
[22:41] <chrisccoulson> this is the first time i've used virtualbox on my new hardware, and it's much faster than i'm used to
[22:41] <seb128> hehe
[22:42] <seb128> ok, time to call it a day
[22:42] <seb128> see you tomorrow ;-)
[22:44] <chrisccoulson> desrt, i got a test hang outside of the buildd!
[22:45] <chrisccoulson> (different test though)
[22:45] <chrisccoulson> gdbus/delivery-in-thread
[22:46] <desrt> i start to wonder if it's gdbus itself that's broken
[22:46] <desrt> rather than just a test here or there
[22:48] <chrisccoulson> desrt, this is in a precise chroot with the hardy kernel series from the buildd btw
[22:48] <chrisccoulson> i just did a minimal server install to try it out :)
[22:52] <desrt> oh.  interesting!
[22:53] <desrt> so we can rule out the load of the buildd as a factor
[22:53] <desrt> seems quite related to kernel version, then
[22:53] <desrt> so here are the items on my list of things we do differently on newer kernels:
[22:53] <desrt>  - eventfd instead of pipes
[22:54] <desrt>  - o_cloexec as a parameter to pipe2 and various other fd-creating calls
[22:54] <desrt>  - futexes (would impact arm, but those have been the same on intel since before 2.6.24)
[22:55] <desrt> it's quite possible that gmaincontext is to blame and the gdbus tests are the ones that fail all the time because of how heavily they use threads
[22:56] <desrt> it could also be that the kernel has a race between an event being delivered to a pipe just as poll() is starting in a different thread
[22:56] <desrt> *shrug*