[00:28] wow gwibber_messages is a very bid database! [00:45] kenvandine, http://theravingrick.blogspot.com/2010/04/todays-slip-cover-feature.html [06:48] Good morning [07:40] morning [08:11] bonjour [08:13] good morning [09:11] seb128: hm, sorry for all the python import warning cron spam -- no idea why it started doing that :-( [09:11] seb128: but at least it's running reasonably stable now [09:11] pitti, hello [09:11] pitti, that's ok, I though you have been restarting a lot when first looking ;-) [09:12] * pitti accepts gnome-games and hopes the new pkgbinarymangler will behave [09:12] pitti, thanks [09:13] hey pitti, seb128 [09:13] bonjour didrocks [09:45] seb128: meh, seems pkgbinarymangler on i386 buildd was held back and disabled for some reason [09:45] * pitti pings lamont [09:45] pitti, :-( [09:49] seb128: hi.. the humanity distribution upload was from last week or from the latest packagers branch.. [09:49] ? [09:50] vish, it was the one you asked me to upload one week ago which didn't get approved before beta2 [09:50] hmm .. :( [09:50] why ":("? [09:51] seb128: well , i fixed a few others bugs in lp as well , after that , expecting them to be uploaded at the same time [09:51] ? [09:51] we can still do uploads [09:51] I don't see the issue and why the ":(" [09:51] ah , neat , then no problems [09:52] what got uploaded was what was in bzr when you asked for upload [09:52] :) [09:52] I'm sure what else should have happened? [09:52] ok, good ;-) [09:52] seb128: i thought that was the last possible uplaod for Lucid , obviously i was wrong :) [09:53] right [09:53] there is still a week for fixing bugs [09:53] neat.. thanks [10:10] err .. "apt-get dist-upgrade" on the other lucid laptop wants to remove the compiz and compiz-gnome packages. That's not right, is it? [10:13] al-maisan: no, wait a little bit [10:13] al-maisan: until a new compiz is build [10:13] mvo: ok .. thanks! [10:13] seb128: that is the issue btw, metacity breaks older compiz, but new compiz is not the in the archive yet [10:14] oh ok [10:14] mvo, thanks [10:21] mvo: heh, I guess we ask for rebuilding in the same time (just got i386, you got the others :)) [10:34] didrocks: LP tells me "start in 12h" [10:34] didrocks: that is pretty bad [10:34] mvo: yeah, I saw that too :( I think rescoring could be good if possible [10:35] I think seb128 has the magic for this [10:35] those got accepted yesterday night [10:35] I'm wondering what the buildds have been doing [10:35] mvo, no, pitti has, slangasek already pinged him about it [10:35] seb128: they have been dep wait, we just relaunch the ping [10:35] s/ping/build [10:35] mvo, I've archive admin powers, not buildds [10:36] didrocks, depwait should automagically work [10:36] didrocks, it's weird [10:36] do you depwait on the wrong version? [10:36] didrocks: what do you need bumped? [10:36] pitti, compiz [10:36] seb128: I checked again, it seems not [10:36] yes, a failed build due to depwait will reset the build score to 0 [10:37] Rescoring build amd64 to 5000... [10:38] pitti, danke [10:39] is LP lying to me? it looks like compiz/i386 is waiting too [10:39] pitti: can you do the same for i386, please? [10:39] already done [10:39] except that LP timed out on me, bah [10:40] seems to be on the slow side today :/ [10:40] nope [10:40] didrocks: I'll keep trying [10:40] pitti: thanks [10:40] why was the updated build-depends needed for there? [10:41] do you statically use the lib? [10:41] ie do you need compiz to be "built" with the change [10:43] seb128: compiz seems to take some part of the button rendering layout from the -dev. and the patch "13_better_support_for_button_layout.patch" in metacity show that we have weird behavior in compiz if not rebuilt [10:44] weird [10:50] . o O { nemiver is really nice } [10:50] pitti, ;-) [11:06] in which corner should the notifications bubbles show up? because right now I see it show up in the upper left corner for a fraction of a second before it jumps to right corner (but sometimes I have two notifications bubbles for a short time: one in left corner and one in the right corner) [11:06] didn't change since karmic [11:07] right corner [11:07] hmm [11:07] notify-osd code almost didn't change this cycle [11:07] I guess I need to file a bug [11:07] do you use a multiscreen setup or something? [11:07] yes [11:09] k, could be it [11:11] I've a dual-screen setup and when there are 2 or more notifications event in the queue, I get two notification bubbles till the last event is shown (tested with notify send) === MacSlow is now known as MacSlow|lunch === njpatel_ is now known as njpatel [11:40] chrisccoulson, fta: wrt. bug 527138, should we just remove enigmail from the archive? it might better suited to install from tbird's extension manager? [11:40] Launchpad bug 527138 in enigmail "enigmail is uninstallable in lucid, needs update to 1.0 - blocked by missing thunderbird-config" [Medium,Confirmed] https://launchpad.net/bugs/527138 [11:40] (tbird should be fine now) [11:46] seb128: bug 530605 has a million tasks; should they really be all open against lucid? or is the libgnome-keyring fix sufficient? [11:46] Launchpad bug 530605 in desktopcouch "gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu." [Critical,Confirmed] https://launchpad.net/bugs/530605 [11:46] pitti - i'm not sure. i thought we were going to fix that actually (but i need to check) [11:46] pitti, it has been used as a collector for all cpu eating issues [11:47] pitti - should bug 544139 be milestoned? it doesn't appear on the RC bugs, but i'm not sure who it should be assigned to... [11:47] Launchpad bug 544139 in consolekit "Active VT tracking can fail at startup" [High,Triaged] https://launchpad.net/bugs/544139 [11:47] pitti, I would close it and ask people who still have a bug to open new bugs [11:47] pitti, the gvfs cpu issue has been fixed in libgnome-keyring or should have been [11:47] seb128: ack [11:48] pitti, other bugs are mainly design issue as discussion this way, now that libgnome-keyring uses dbus it runs in new class of interesting issues if used out of the mainloop etc [11:48] discussion this way -> discussed this week [11:49] seb128: FYI, I reenabled karmic in the retracers, it's catching up now (it caught up with lucid) [11:50] \o/ on lucid catching [11:50] pitti, danke [11:55] chrisccoulson: I assigned bug 557640 to you, which seems related to the other search engine changes you were working on [11:55] Launchpad bug 557640 in firefox "[Lucid Beta2] nrf-003 testcase failed Default "Welcome to Ubuntu" page doesn't appear without connectivity" [High,Triaged] https://launchpad.net/bugs/557640 [11:55] chrisccoulson: it sounds like it'd magically fix itself once you switch back to google? [11:56] pitti, schedule seems tighter than usual this cycle to get GNOME .1 in lucid, is that still something we should count on? [11:56] pitti - i'm not sure the switch back to google will fix that [11:56] that's probably an issue with ubufox actually [11:56] pitti, or should we rather play backporting git changes [11:56] pitti, or do .1 in sru updates? [11:57] seb128: like hardy, we should probably put point releases into SRUs either way (up to .2 or .3?) [11:57] seb128: when will .1 be released? [11:57] seb128, what's the deadline for a next Empathy stable release? [11:57] cassidy, wednesday next week [11:57] seb128: for bugs >= high I'd backport either way [11:57] if I read the calendar correctly [11:57] seb128, ok, I'll release it this afternoon or at the beginning of next week [11:58] seb128: we can still accept some .1 packages during final freeze (the first week, anyway) [11:58] pitti, tarballs due on the 26 [11:58] seb128: ugh, that's definitively outside the lucid final range [11:59] seb128: so, I guess .1 in SRU (so that they'll be in 10.04.1) and backporting important stuff? [11:59] pitti - did you recreate bug 557640? it's working as expected here (ie, it redirects to a local start page) [11:59] Launchpad bug 557640 in firefox "[Lucid Beta2] nrf-003 testcase failed Default "Welcome to Ubuntu" page doesn't appear without connectivity" [High,Triaged] https://launchpad.net/bugs/557640 [11:59] right, I wouldn't have asked if it was the week before [11:59] chrisccoulson: no, I just saw it on the RC bug list [11:59] pitti, ok, was my though too, I wanted to mention it and check with you [11:59] hmmm :-/ [11:59] seb128: thanks [11:59] seb128: weird; we don't seem to release earlier than usual; does GNOME release later? [11:59] cassidy, thanks [12:00] chrisccoulson: if it's not reproducible, set it to incomplete and lower priority [12:00] pitti, I think they are one week off compared to usual [12:00] pitti, they did some schedules change for GNOME3 [12:00] seb128: I remember that we usually even uploaded them right after RC [12:00] ie respinned a bit things around [12:00] pitti, right, it's usually one week earlier [12:00] which is tight but doable [12:01] one week later is out of scope [12:01] it will avoid the rush before rc [12:01] which is at least something ;-) [12:01] hum, lunch ready [12:01] * seb128 bbl [12:01] seb128: enjoy [12:02] seb128: I'm sure people will cry for things like http://git.gnome.org/browse/gvfs/commit/?id=1cb5861795d375719b196ecf93fb0a10397414d3 :-) [12:03] seb128: I'm happy to do and test git snapshots of gvfs/gdu and some other bits if you want me to [12:05] pitti: well, I mean, seeing the price of the iPad, they deserve to see "iPad" as a title :-) [12:06] kenvandine: can you please update https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus for DX/OLS? [12:06] hm, where is our favourite Kubutu rocker today? [12:11] Is there any chance of getting the enigmail plugin to work with thunderbird3 btw? [12:13] al-maisan: that's the point of that bug [12:16] pitti: ah, I see. [12:17] some users have an unique UNE interface: http://launchpadlibrarian.net/43533691/The%20Blue%20Screenshots.png (that's a bug, still can't find it, he will try with a cleaned /home) [12:17] pitti, I will review all git changes next week [12:17] pitti, but I think we should "snapshot" git for some of the things [12:17] or git diff between stable and current and use that as a patch [12:18] seb128: yeah, whatever you prefer [12:18] gvfs being one [12:18] seb128: will you need some help for the review? [12:18] seb128: but usually there are tons of translation updates, so a make distcheck in git trunk seems easier [12:18] didrocks, I can use help for this yes ;-) [12:18] pitti, right [12:18] * seb128 dessert and coffee, brb [12:20] * pitti -> lunch [12:28] pitti - ok, i reproduced that bug now (i had to clear my cache) ;) === MacSlow|lunch is now known as MacSlow [12:54] is it worth deviating from Debian just to add an lpi patch? [12:57] Laney, depends [12:58] Laney, it's the case for quite some GNOME components [12:58] out of the fact that we package those before debian since we track unstable series where they don't [12:58] seb128: not this one (gbrainy) [12:59] robert_ancell wanted to work on an upstream vendor lib [12:59] which would make those deltas be reduced [12:59] I'm doing the merge anyway [12:59] just wondered whether we could sync it instead [13:00] I've no strong opinion on whether those entries are worth the diff for games [13:00] I would say it's low cost to keep it for lucid now [13:00] it needs some porting to the new upstream release [13:00] lets see if it worked [13:21] didrocks, how busy are you for lucid? looking to bug to work on still? [13:22] seb128: I'm doing nothing important right now (update testing and minor things). So if you have something, I can handle it :) [13:22] didrocks, would you like to look at the desktop effects option hang issue? [13:22] (btw, reinstalling karmic with the old theme seems *so ugly* now :)) [13:23] seb128: sure, is there a bug report for that? [13:23] (noticed that but didn't look at g-c-c bug) [13:23] yes [13:23] one with quite some duplicates, let me get the number [13:24] seb128: bug #554106 ? [13:24] Launchpad bug 554106 in gnome-control-center "Gnome Appearance Properties dialog hangs when changing desktop effects" [Medium,Triaged] https://launchpad.net/bugs/554106 [13:24] right [13:25] didrocks, you start being faster than me it seems ;-) [13:25] * seb128 hugs didrocks [13:25] seb128: I will never be, don't be afraid :) [13:25] * didrocks hugs seb128 [13:26] hey pedro_ [13:26] bonjour seb128! [13:27] pedro_, how are you? [13:28] didrocks, I would not be surprised if that was another sideeffect of gtk-threading there [13:28] seb128, good, thanks , what about you? [13:28] 2.30 had fixes for this which lead to look when things are not hanlded as they should [13:28] pedro_, I'm good thanks! [13:29] pedro_, how is lucid looking for you? [13:29] seb128: yeah, I just saw "mutex" in the bt and become to be frigthened. Let's take it as a good exercice :) [13:29] didrocks, hehe [13:29] seb128, is looking great here, can't wait for the final release :-) [13:30] salut didrocks [13:30] didrocks, https://bugzilla.gnome.org/show_bug.cgi?id=614256 too [13:30] Gnome bug 614256 in Appearance "crashes when installing icon themes by dnd" [Normal,New] [13:30] hey pedro_ [13:30] olà Pedro [13:31] seb128: yes, I saw you discussed about that yesterday. Having a look too [13:31] didrocks, obviously the capplet still has locking issues, maybe looking at the recent changes as an inspiration and apply that where it needs to be still done would be a good start [13:31] didrocks, as you said a good learning experience too if you never looked at such issues ;-) [13:31] bonjour baptistemm! [13:31] lut baptistemm [13:31] salut seb128 [13:31] I feel better to have some power to triage all those blueooth bugs [13:31] seb128: definitely :) [13:32] pitti, will do [14:03] bah [14:03] g-s-d is crash land on launchpad [14:03] it should really not crash because any of the .so is crashing [14:03] ie lot of those are due to keyboard or libgnomekbd issues [14:05] seb128 - yeah, i just noticed all those crashes in my inbox :( [14:09] shouldn't crash> hm, it's all in-process, isn't it? [14:11] pitti, right, "shouldn"t was a "would be nice if it was redesigned to not be this way" [14:26] pitti - ok, we figured out bug 557640 in the end [14:26] Launchpad bug 557640 in firefox "[Lucid Beta2] nrf-003 testcase failed Default "Welcome to Ubuntu" page doesn't appear without connectivity" [High,In progress] https://launchpad.net/bugs/557640 [14:26] chrisccoulson: \o/ [14:26] * kenvandine hugs rodrigo_ for always using a NEWS file :) [14:27] kenvandine, I do it because I know you like it :D [14:27] :) [14:27] i wish tedg cared what i liked :) [14:27] :) [14:27] he makes me guess what's changed [14:28] with ted was around for me to harass :) [14:28] s/with/wish [14:29] kenvandine, talking about this, do you know how to see the bug# for bzr commits you used 'bzr commit --fixes lp:..." for? [14:29] rodrigo_, nope [14:29] there must be a way though [14:30] yeah, that's the only thing preventing me from generating NEWS automatically :D [14:33] it's in bzr log [14:33] revno: 1757 [14:33] fixes bug(s): https://launchpad.net/bugs/539427 [14:33] Launchpad bug 539427 in apport "apport-collect gives apport-gtk help" [Low,Fix released] [14:33] committer: Martin Pitt [14:33] branch nick: trunk [14:33] [...] [14:41] pitti, it's in the bzr log of the branch, but not in trunk it seems [14:42] rodrigo_: ah, it won't be kept across merging, I guess [14:42] pitti, yeah, seems so, and when doing the release I just branch from trunk [14:42] rodrigo_: bzr log -n 2 might help [14:42] seb128, btw, how can I know rhythmbox was started because a device was connected? [14:43] rodrigo_, it's called with the device as argument on the command line I guess [14:43] rodrigo_, ie "rhythmbox " [14:44] seb128, I can't get the command line of rhytmbox from the plugin, except via /proc, afaik, right? [14:44] rodrigo_, I don't know, better asking on #rhythmbox I guess [14:44] pitti, ah, cool, that shows it indeed [14:50] i'm going to have hardly any bugs left after today! [14:53] pitti, see that mail i sent with the U1 bugs? [14:53] chrisccoulson: sounds great! [14:53] kenvandine: didn't get to it yet, sorry [14:54] pitti, no worries... it's a long list [14:54] pitti, should we put anything about those on the release status page? [14:54] or wait until they get targeted ? [14:55] kenvandine: feel free to add them [14:55] ok, will do [14:55] pitti, put them under RC bugs, Triaged problems? [14:56] yes [15:04] chrisccoulson, on a bug fixing rampage today? ;-) [15:04] go, chrisccoulson, go! [15:05] seb128 - the firefox upload which i will do later closes 5 bugs [15:05] chrisccoulson, do you still have the xulrunner startup notification one on your lucid list btw? [15:05] seb128 - yeah, that's been fixed upstream in the 1.9.2 branch, and will be in the FF3.6.4 update [15:05] kenvandine: looked at it now -- it's just accepting the nominations? doing that now [15:06] chrisccoulson, is that coming before lucid? [15:07] seb128 - that will come as a security update right after lucid [15:07] in fact, i'll probably be doing the update from UDS ;) [15:07] chrisccoulson, ok, fair enough, still looks weird to have that extra tasklist entry when you start your browser but I guess I'm picky there [15:08] kenvandine: I expect that we need to drop the milestones for most/many of them; but those can all be fixed in SRUs as well, so the lucid targetting still makes sense [15:09] kenvandine: ok, all nominations accepted [15:10] pitti, thx [15:10] saving wiki page now [15:11] kenvandine: hm, you added all of them? only high/critical should be on that list [15:11] (the release blockers) [15:11] oh... damn [15:11] * kenvandine edits [15:12] kenvandine: also, since these are by and large done by OLS, I don't think we need to track all of them on our status page [15:12] (but if it helps you, please do) [15:12] kenvandine: but usually those have an associated status [15:12] humm... do they have their own status for the release meeting? [15:13] usually yes, so that we can see at a glance where we are [15:14] i. e. which ones are well on track (some are also "fix committed" upstream, btw), which ones are difficult because they lack reproducers, etc. [15:21] pitti, ok moved the fixed committed ones and dropped < high [15:21] also FYI, the desktopcouch run_couchdb() bug is not fixed [15:21] bug 530541 [15:21] Launchpad bug 530541 in desktopcouch "desktopcouch-service crashed with RuntimeError in run_couchdb()" [High,Triaged] https://launchpad.net/bugs/530541 [15:22] chad is working on it still, he thought it was fixed, but not so much :/ [15:22] kenvandine: yes, I thought I said so on the wiki page [15:22] you did [15:23] just making sure that wasn't stale info :) [15:23] it really is still broken [15:23] kenvandine: thanks for the info [15:49] pitti - is there any way to avoid uploading a tarball again when uploading a new revision of a package with dput? [15:49] (i should probably know the answer to that already) [15:50] but uploading 50MB tarballs takes a long time [15:50] chrisccoulson: not with dput, but you can specify -sd on debuild or dpkg-buildpackage [15:50] pitti - oh, i didn't know that. i'll give that a try, thanks [15:50] chrisccoulson: you can also drop it from the source_changes an re-debsign [15:50] (if building the source takes long) [15:50] building the source doesn't take long, but uploading the 50MB tarball that i only uploaded a week ago takes a long time ;) [15:53] heh, that was much quicker [15:53] about 3 seconds :) [15:59] chrisccoulson, does uploading a new revision with tarball work? [15:59] yes, it does, as long as it's identical [15:59] usually you get an error saying the tarball is already there no? [15:59] oh ok [15:59] I didn't do that for years [15:59] I though it would complain that you try to overwrite the tarball ;-) [15:59] I've a sucking ul, I avoid uploading tarballs twice ;-) [15:59] seb128 - yeah, it works. i always did that before just because i didn't know how to do it without the tarball ;) [16:00] but that's ok for small tarballs [16:00] but for 50MB firefox uploads, it's not so great ;) [16:00] chrisccoulson: the default behaviour should be quite fine [16:00] i. e. with tar for -1 and -0ubuntu1, and without tar otherwise [16:01] chrisccoulson: wow, you rock (just read the changelog) [16:01] pitti - heh, it got a few bugs closed :) [16:02] * pitti updates https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus for the one RC bug [16:04] chrisccoulson, nice update indeed ;-) [16:04] kenvandine: bug #559151 may become a heavy duplicate bug soon. Introduced in Gwibber with the 2.29.95.0ubuntu1 just released (sorry if you're not the gwibber guy) [16:04] Launchpad bug 559151 in gwibber "gwibber-service crashed with KeyError in get_records()" [Medium,Confirmed] https://launchpad.net/bugs/559151 [16:05] pitti, when is the meeting today? [16:05] pitti, dst changes confused my calendar [16:05] seb128: just started [16:05] pitti, thanks [16:06] bcurtiswx, looking [16:10] seb128: but our turn is still some 45 to 60 minutes out [16:10] Good morning guys [16:11] good morning Nafai, how are you? [16:11] pretty well [16:11] pitti, right, I'm just hanging there, end of week mood now :p [16:11] hey Nafai [16:11] hi Nafai [16:12] seb128: speaking of good moods: http://people.canonical.com/~fader/hw-testing/current.html :-) [16:12] really nice [16:12] waouh [16:14] good :) [16:14] that is nice [16:14] so, lamont fixed the buildd chroots, let's give gnome-games another spin [16:15] pedro_, https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/528299 [16:15] Launchpad bug 528299 in nautilus "nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()" [Medium,Triaged] [16:15] pedro_, did you bug watch the wrong bug? [16:15] seb128, let me check [16:15] pitti, nice! what was the issue on the buildd? [16:15] seb128: yes, pkgbinarymangler is on hold and only gets updated manually [16:16] seb128: there were two catastrophes within 4 weeks, and both outside lamont's core hours :) [16:16] I see [16:17] bcurtiswx, ok, testing a fix [16:17] kenvandine: good, thank you [16:22] seb128, all fixed now, thank you for checking ;-) [16:23] pedro_, np, thanks [16:30] chrisccoulson: you don't happen to have an updated idea about bug 447431 yet, do you? [16:30] Launchpad bug 447431 in gnome-desktop "gnome-settings-daemon dies with BadMatch" [Medium,Triaged] https://launchpad.net/bugs/447431 [16:31] pitti - not yet, i thought the upstream change would have fixed the crash [16:31] pitti - i'll see if i can still reproduce that in a bit [16:31] chrisccoulson: ah, you could in the past? [16:32] chrisccoulson: if not, perhaps you can arrange ssh access to slangasek's machine [16:32] pitti - yeah, it crashed for me before [16:32] it's a good SRU candidate, too, though [16:32] chrisccoulson: just mentioning in case you run out of RC bugs :) [16:33] pitti - i don't think i'll run out, but my list of assigned bugs is quite a bit shorter than it was this morning :) [16:34] bah this g-c-c hand on desktop effects change is weird [16:34] I'm wondering if that's another gtk locking issue similar to the crasher on theme dnd [16:35] seb128: did you look more into that ? [16:35] Has anyone filed a bug about the latest metacity? I can't use alt-space to bring up the window menu and I get the following output in ~/.xsession-errors: http://paste.ubuntu.com/411659/ [16:35] mclasen, didrocks is trying to look into it right now [16:36] mclasen, I'm wondering if it would not be easier to just do the theme install in an callback [16:36] or in a idle function or something [16:37] but that's maybe because I don't know how to debug locking issues [16:38] I confirm that reverting this commit (http://git.gnome.org/browse/gnome-control-center/commit/?id=e34e6b4eebbb957107e88334faef2ed8a02d5eea) workaround the lock issue [16:39] shrug [16:40] I still don't see why, we have one thread, not two… it's certainly a code path where a lock isn't freed before we try to get a new lock [16:40] didrocks: 'the lock issue' ? are you seeing deadlocks ? [16:41] mclasen, our "desktop effects" is an extra tab in the same capplet, and it locks when closing the dialog displayed after wm change now [16:41] it being the capplet [16:42] mclasen: the hang in selecting the desktop effect seems to be due to a deadlock [16:42] of course, removing the locking will 'prevent' the deadlocks [16:42] mclasen: it was for checking that the those locks were the one to blame there [16:42] not a solution, for sure [16:43] does your code ever take the gdk lock ? [16:44] no [16:48] mclasen, the code is basically the same as your desktop-effects one was some cyles ago [16:48] we didn't resync on what you did since but it was inspired of it [16:48] mclasen, we have a gtk_dialog_run() after selecting the option in the dialog [16:49] + a gtimeout for the default choice [16:49] and the capplet freezes when clicking on one of the buttons [16:52] if you need any help looking at this, then just let me know. i might have slightly more free cycles now ;) [16:53] seb128: our turn now, in case you want to join the meeting and bring up the thawing? [16:53] chrisccoulson, we do yes [16:54] neither me of didrocks have experience with those locking issues [16:54] pitti, ok [16:54] so, removing only the gdk_threads_{enter,leave} don't fix that gdk_threads_init (); has to be removed too [16:54] pitti, let me know when,if I should speak up there ;-) [16:54] chrisccoulson: ^ in capplets/appearance/appearance-main.c [16:54] seb128: the guys are just digesting my reports [16:55] didrocks - ok, thanks. i will take a look at that shortly and see if i can figure it out [16:55] chrisccoulson: I'll just give a quick look at the path we take from your patch to see if we recall the function making the gdk_threads_init call [16:56] chrisccoulson, https://bugzilla.gnome.org/show_bug.cgi?id=614256 too [16:56]