[05:26] i need help with desktop sharing anyone here know about it?? === sabdfl1 is now known as sabdfl [07:05] Good morning [07:12] Guten Tag pitti [08:15] hello [08:16] lut seb128 [08:16] hey didrocks [08:16] seb128: did you have a restful night? [08:16] yes! [08:17] watched a movie and had almost 8 hours sleep yesterday [08:17] and you? [08:17] \o/ that's needed after a GNOME release ;) [08:17] hey MacSlow [08:17] didrocks: indeed! [08:17] yes, fine too. Thanks! [08:18] didrocks: [08:18] http://download.gnome.org/sources/deskbar-applet/2.26/deskbar-applet-2.26.0.tar.gz [08:18] seb128: I merged a contributor update of murrine. dholbach asks for an explicit FFe on bug #344154 ;) [08:18] Launchpad bug 344154 in gtk2-engines-murrine "Please, sponsor gtk2-engines-murrine 0.90.0 into jaunty" [Undecided,Triaged] https://launchpad.net/bugs/344154 [08:18] didrocks: if you want to do another update ;-) [08:19] pitti: ^ it's main, can you grant the exception? [08:19] seb128: of course. I will handle it in a couple of hours (my girlfriend wants to do some shopping first ;)) [08:19] didrocks: sure no hurry, enjoy the shopping! [08:19] shopping! [08:19] seb128, didrocks: any upstream changelog? does it have new features? [08:20] seb128: do you want to do the gnome-media sponsoring (it adds a new package) or is that all discussed and agreed upon? [08:20] pitti: the changelog is in the changelog file, no NEWS. There are some slightely changes [08:20] mvo, pitti: guten tag [08:21] pitti: we had a svn snaphost and upstream rolled a tarball with a special mention for jaunty, there was a blog post on planet.gnome.org [08:21] pitti: ie they fixed quite some bugs since and would like us to ship this stable version rather than a buggy snapshot [08:22] mvo: I asked chrisccoulson to do those changes, as discussed at distro sprint we use the intrepid capplet and make the new one available [08:22] mvo: you are welcome to review or sponsor or it or I can do it too today if you want, we are mostly done with 2.26 so I'm not too busy today [08:23] seb128: bbl, have a good morning and probably lunch too ;) [08:23] seb128: ok, thats fine then. I have a look and upload [08:23] * mvo hugs chrisccoulson [08:23] mvo: thanks! [08:23] seb128: sure, makes sense to me [08:23] didrocks: you too [08:23] seb128: thanks! [08:23] didrocks: did you test this on your box? [08:24] :) [08:25] pitti: the murrine update? Before the merge, yes. After removing quilt (Khashayar changes), I only rebuilt it. [08:25] didrocks: please test it in the current form; if it works, please go ahead [08:26] pitti: let me launch my jaunty's box [08:26] pitti: I'm looking to the indicator-applet update now if you didn't yet [08:28] seb128: no, I didn't; thanks [08:28] yay new usplash [08:33] hm, personally I find it a bit misleading that the package is named "gnome-volume-control" but the gnome-volume-control binary is in gnome-media and the gnome-volume-control one is called gnome-volume-control-settings - thoughts? [08:34] other than this nitpick the update looks fine [08:34] lut huats [08:35] mvo: call the binary gnome-volume-control-new? [08:35] the binary package I mean [08:35] hello everyone [08:35] sorry I got to run [08:38] seb128: ok, g-v-c-pulse does not make sense, or does it? [08:39] mvo: that would work too [08:39] mvo: yeah, use that naming [08:39] chrisccoulson: ^ opinion? [08:42] that sounds ok. the only reason i chose the name is because the new package ships g-v-c-settings and g-v-c-applet, and upstream call it gnome-volume-control too [08:43] which is really confusing when they also install gst-mix as gnome-volume-control [08:43] right [08:43] seb128: ah, saw the new indicator-applet merge request; please let me know if bzr bd DTRT for you now [08:43] pitti: it did thanks [08:43] seb128: if they released a new upstream tarball, it should Just Work (tm) [08:43] cool [08:43] pitti: not sure if launchpad did pick up the upload correctly though [08:44] pitti: the tarball download didn't work though [08:44] oh? worked for me on a different project yesterday [08:44] seb128: what happened? [08:44] thanks, I go with -pulse then [08:45] pitti: [08:45] http://launchpad.net/indicator-applet/+download failed: 501 Protocol scheme 'https' is not supported (Crypt::SSLeay not installed) [08:45] argh [08:45] pitti: I probably need to install something but dunno which one [08:45] seb128: I probably have that perl module installed [08:45] libcrypt-ssleay-perl [08:46] yes, I do [08:46] seb128: ^ try that [08:46] pitti: that works indeed ;-) [08:46] pitti: anyway update built, tested, uploaded and pushed to bzr [08:49] hey seb128, mvo, pitti [08:49] good morning [08:50] hey MacSlow [08:50] seb128: \o/ merci [08:50] lut crevette [08:55] salut seb128 [08:59] mvo - i think you forgot to rename debian/gnome-volume-control.install on the gnome-media upload [09:00] chrisccoulson: oh, bugger. thanks [09:00] that's ok ;) [09:00] it's just failed to build on lpia, but i haven't checked the build log yet [09:02] chrisccoulson: thanks, fixed locally now, I do a testbuild with that now and if its all good I upload it right away [09:03] the lpia build failure looks unrelated. i386 and ppc just finished successfully (albeit, with an empty package) [09:04] asac: gnome bug #571423 still on your list? [09:04] Gnome bug 571423 in ask dialog "grabbing the keyboard while a menu is open can lock the session" [Normal,Needinfo] http://bugzilla.gnome.org/show_bug.cgi?id=571423 [09:05] seb128: what is missing. just http://bugzilla.gnome.org/show_bug.cgi?id=571423#c8 ? [09:05] i will do that now [09:05] Gnome bug 571423 in ask dialog "grabbing the keyboard while a menu is open can lock the session" [Normal,Needinfo] [09:05] * asac gets the test sources [09:06] asac: the current commenter stated not having the issue with the test program but you did iirc? [09:07] asac: the comment you point has a question [09:07] yes [09:07] asac: "Could you duplicate the problem, and paste the output of the test program [09:07] attached?" [09:07] seb128: yes. that qusetion i saw. wondered if there is something else ;) [09:07] asac: if you do have the issue could you respond to that so we can get things moving again? [09:07] asac: that's all yes [09:08] 10:05 < asac> i will do that now [09:08] thanks ;-) [09:10] so on metacity it definitly doesnt happen ... let me boot laptop with compiz where i had this issue initially [09:11] I'm off for about two hours; I'm not feeling very well, and need some fresh air [09:11] I'll do some work in the evening to compensate [09:11] pitti: see you [09:11] pitti: you work enough there is no need to compensate ;-) [09:12] * seb128 hugs pitti [09:21] * seb128 hugs mvo [09:21] mvo: thanks for the sponsoring work! [09:21] get well pitti [09:22] seb128: np, doing it with bzr is really mostly fun :) [09:22] hiya [09:22] hey dholbach [09:22] dholbach: thanks for the sponsoring you are doing too [09:22] seb128: I tried to do the python-nautilus thing yesterday, but it FTBFS [09:22] seb128: something weird with gnomevfs / python-gnome* [09:24] seb128: I gave up in the end and just de-installed, so I could remove python2.5* [09:24] dholbach: ok [09:24] maybe http://cvs.fedoraproject.org/viewvc/devel/nautilus-python/nautilus-python-0.5.1-gnome-vfs.patch?revision=1.1&view=markup ? [09:24] do you have the build error? [09:25] hang on [09:25] could be [09:25] did you try this change? [09:25] no, just found it now [09:25] is anybody really using nautilus-python? [09:25] no idea [09:34] seb128: in any case the proper fix would be a port to gvfs, but there's not much activity upstream it seems [09:34] indeed [09:35] I've enough things in the desktop to not spend time on nautilus-python to be honest, I don't think it's very used or useful [09:37] seb128: that fixed it [09:37] seb128: uploaded [09:37] dholbach: danke [09:37] de rien [09:37] easy enough to do [09:37] seb128: gotta do something sometimes to justify my ~ubuntu-desktop membership :) [09:39] seb128: bzr-gtk recommends python-nautilus - that's why I had it installed [10:10] pitti, thanks and hugs for fixing bug 343618 [10:11] Launchpad bug 343618 in gnome-mount "New cache flush progress window misplaced and has truncated text" [Undecided,Fix released] https://launchpad.net/bugs/343618 [11:57] mdeslaur: hji [11:58] asac: so, as I was saying [11:58] mdeslaur: so if you select 10px its the same size? and for 10pt its flipped from what we expect? [11:58] asac: yes [11:59] asac: well, not flipped [11:59] mdeslaur: so for 96dpi vs. 135dpi we would expect 2/3 of actual size ... and now its 4/3 ? [11:59] asac: I would expect "pt" fonts to be dpi-adjusted once [11:59] asac: it's 1.5 times right now [11:59] asac: I would expect it to be 1/1 [11:59] mdeslaur: yeah makes sense [12:00] 40/96 ~ 0.5 [12:00] mdeslaur: please say good bye to the meta discussion. [12:00] mdeslaur: if you configure fonts with 10pt they will be different on screens [12:00] if the notion in the gnome appearence dialog actually tries to do "px" [12:01] and there is a calculation bug thats a different thing ;) [12:01] and that could be the case actually [12:02] mdeslaur: so please try the pango-view command on both [12:02] asac: pango-view command? [12:02] pango-view -t "Test Text 1" --font="Sans 10pt" [12:03] mdeslaur: sorry. remove the pt [12:03] just "Sans 10" [12:03] mdeslaur: please check how that behaves [12:03] mdeslaur: its in libpango*dev [12:04] good morning all [12:05] hi kenvandine_wk [12:05] hey asac [12:06] pitti: do you deal with the kde port of jockey too? [12:06] seb128: so what's the plan for ekiga, 3.2 or 3.0.2? [12:07] kenvandine_wk: your call I would say ;-) [12:07] i have the patches ported for 3.2, but the deps aren't available yet (or wasn't last night) [12:07] 3.2 depends on versions of opal and ptlib that haven't been released yet :) [12:07] * kenvandine_wk checks to see if they are now [12:10] kenvandine_wk: new opal an ptlib have been rolled since yesterday [12:10] * kenvandine_wk isn't seeing them [12:10] 2.6.1 and 3.6.1 [12:11] damn mirrors [12:11] ok, forced to use a different mirror and i am seeing it [12:11] * kenvandine_wk will build those [12:15] back; my head feels slightly better now [12:16] asac: ok, I'll drop this issue now. thanks to you and seb128 and pitti for hearing me out. [12:16] mpt: no problem; the label wrap bug is still on my radar, working on a small test case [12:16] davmor2: yes, I can fix grave breakages [12:16] mdeslaur: drop? [12:17] pitti: I'll let you guys handle it as you think it should be. [12:18] mdeslaur: I'm not entirely sure that I thoroughly understood the matter :) [12:18] pitti: well, me neither :) [12:20] pitti: not so much grave as graphically incorrect. the listing in Kubuntu for Nvidia looks like this http://www.davmor2.co.uk/jock.png [12:21] mdeslaur: can you please test the pango-view commands still? [12:21] people might automatically install the 173 driver due to it being the highlighted one rather than the 180 which is the recommended one [12:21] mdeslaur: and tell me if "Sans 10" vs. "Sans 10px" have the same behaviour that they have in gconf= [12:21] ? [12:22] asac: okay, one sec [12:29] asac: I need to reinstall jaunty on my netbook...I'll have the results a little later [12:30] lool: do you think you could have a look to the pango 1.24 update for debian (and ubuntu since we are in sync)? [12:35] mdeslaur: ok. no problem. let me know [12:35] mdeslaur: btw, your findings are much appreciated as i dont have a high dpi display here [12:39] davmor2: ah, you mean that the recommended one should come first? [12:39] davmor2: btw, does it actually work for you? Riddell mentioned the other day that it wouldn't work for him at all [12:40] pitti: Yes so it is the highlighted one which is correct in gnome but not kde [12:40] davmor2: I didn't upload the recent nvidia crash fix yet, though [12:40] ah, no, I did [12:40] pitti: I just installed it I was about to restart to check it :) [12:40] davmor2: if you came that far, it can't be so bad :) [12:41] * pitti tests it here, too [12:43] pitti: It's up and running here :) [12:43] yay [12:43] davmor2: thanks [12:44] pitti: how does the list get made up is it jsut random or do you set the list? [12:45] davmor2: it's more or less random right now [12:45] davmor2: well, 'random' in the "python dictionary key order" sense [12:46] pitti: Right. Okay just seems strange that it always seems to be in number order in gnome and not in kde is all :) [12:48] davmor2: btw, could you test something else, please? [12:48] Yeap [12:48] davmor2: if you currently have a kubuntu up and running? [12:48] yeap [12:48] davmor2: can you please install policykit-kde (if it's not already) and run "jockey-kde" from a Terminal, as normal user? [12:49] davmor2: using policykit-kde should work now, and I'd like to stop it running as root entirely [12:49] I tried it here, but under gnome it insists to use policykit-gnome [12:49] * pitti looks forward to getting DSL soon, so that he has enough bandwidth to get KDE CDs, too [12:50] pitti: I it not policykit-kde that kicked in and asked for the password just then? [12:50] davmor2: please try installing or uninstalling something [12:50] pitti: hehe... good :) [12:50] what speed is your new DSL connection pitti? [12:50] Is even [12:50] davmor2: in Kubuntu you should be asked for you password at program start (kdesu) [12:50] davmor2: while in GNOME you get asked when you install/remove a driver (with policykit) [12:50] davmor2: right now you should still see kdesu when you run it from the menu [12:51] pitti: Ah yes I'll try it now [12:51] chrisccoulson: well, "new"; it's the first time DSL is available here :) will be a 6000 one [12:51] fantastic! [12:51] mvo: around? [12:51] yes [12:51] my DSL connection dropped to 580B/s last night. notice the lack of the "k" ;) [12:51] mvo: do we have an easy way to grep the whole archive for something? [12:52] chrisccoulson: eek [12:52] seb128: source or binary? [12:52] mvo: I'm pondering splitting the gtksourceview1 python package since nothing in the default install seems to be using it [12:52] chrisccoulson: eww; well, I'm crossing fingers that it'll actually work [12:52] mine went really slow as soon as i told my ISP that i was leaving [12:52] pitti: seems to be working I'll just reboot after to double check [12:53] seb128, mvo: I usually run that on rookery's mirror, with http://people.ubuntu.com/~pitti/scripts/for-srcarchive [12:53] davmor2: rock, thanks [12:53] mvo: source, in fact the problem is easier than then, I just need to go through the rdepends of python-gnome2-desktop [12:53] pitti: policykit-kde is installed [12:53] I guess I could easy get the list and apt-get source everything [12:53] mvo: do you have tools for this sort of job? [12:53] davmor2: you should be asked for password as soon as you install/remove a driver [12:54] seb128: no, sorry. maybe the script that pitti has helps? [12:54] looking into that [12:54] I'm not sure what it does exactly [12:54] my script walks over an archive, unpacks everything, and runs a command in the source tree (such as grep) [12:54] pitti: yes it's working in the same way as gnome I'm just checking that the nvidia driver got removed then I'll reinstall it again [12:55] pitti: how many years does it take? ;-) [12:55] pitti: Right it's removed fine I'll reinstall it now [12:55] seb128: e. g. for-srcarchive /srv/archive.ubuntu.com/ubuntu dists/jaunty/main/source/Sources.gz "grep -r foobar" [12:55] seb128: about a day; run it in screen :) [12:56] seb128: it's quicker for main [12:56] I guess I will just do a for package in$ $list; apt-get source $package; and then grep [12:56] I just need the python-gnome2-desktop rdepends [12:56] seb128: for a small set of packages that'll work [12:56] seb128: you can still do that on rookery to use the mirror there [12:56] seb128: or an apport fakechroot [12:56] pitti: right thanks [12:58] seb128: Pango: I wish, but certainly not today and likely not this week, I'm blocking various work and need to make progress on my tasks ASAP, also I'm covering for davidm this week [12:59] seb128: I would like to though, especially since I have armel changes to do [13:01] lool: hum ok, thanks anyway [13:01] pitti: That's worked fine removing and installing :) [13:02] lool: I will see if slomo wants to do it, jaunty beta freeze is tomorrow [13:02] davmor2: thanks, much appreciated [13:02] davmor2: I'll change jockey-kde to use polkit-kde then [13:02] Urgh beta freeze is tomorrow already [13:02] indeed [13:03] pitti: pop-up for policykit appears after you have selected and hit activate [13:16] pitti: I reinstall a fresh jaunty box and there is no noticeable issue with murrine gtk engine. [13:17] didrocks: nice; then let's get it in [13:23] asac: pango-view renders a 10pt font at a sane size [13:23] asac: on a 135dpi screen [13:26] didrocks: they rolled a 0.90.1 since [13:27] asac: oh, weird, the pango-view titlebar says 96 dpi [13:27] pitti: ^ [13:27] mdeslaur: if you use "Sans 10" ? [13:27] mdeslaur: what is sane size? [13:27] seb128: sounds like bug-fix only, compared to 90? [13:28] pitti: yes [13:28] mdeslaur: you can use --dpi=135 [13:28] pitti: just pointing to didrocks that he might want to update to this one, doesn't hurt to get some extra bug fixing now [13:28] indeed [13:29] asac: by default, it assumes dpi=96, so it renders "Sans 10" the same size as "Sans 13.333px" [13:29] asac: if I specify --dpi=135, than "Sans 10" is bigger, like the desktop [13:29] seb128: ok, I will do it [13:35] mdeslaur: ok. so to summarize. with --dpi the point size is also physically larger on higher dpi screens when using pango-view? [13:35] and px has the same physical size? [13:36] asac: yes [13:36] asac: sidenote: weird, my firefox text isn't antialiased [13:36] good. i will check. but i guess that pango-view is right and point has really the opposite effect from what we would suspect [13:37] mdeslaur: thats because you use inferior fonts ;) [13:37] mdeslaur: you shouldnt allow websites to select their fonts [13:37] mdeslaur: also we have a regression: [13:37] mdeslaur: run: sudo ln -s /etc/fonts/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d/70-no-bitmaps.conf [13:38] asac: I wish the firefox preferences panel would fit in my screen so I could change it :) [13:38] mdeslaur: lol [13:38] mdeslaur: about:config, set browser.display.use_document_fonts to 0 [13:38] mdeslaur: the no-bitmaps font will be readded on next upload [13:38] s/font/link/ [13:39] but i would still suggest to prevent sites from selecting their own fonts [13:42] mdeslaur: oh. you could check if all backends have the same behaviour with pango-view ... e.g. --backend=cairo [13:42] --backend=xft [13:42] there is also ft2 and x [13:42] but i guess we shouldnt look after those [13:44] asac: xft backend gives the same results [13:44] pitti & seb128: new revision tested and pushed [13:45] didrocks: excellent [13:45] mdeslaur: ok. but 10px still does the right thing? with --dpi=xxx? [13:45] didrocks: do you have still some updates on your todolist? [13:45] right thing == same physical size ;) [13:45] asac: yes [13:45] mdeslaur: yeah. a bit odd though. size doesnt change here on the same screen regardless of what i use as --dpi [13:46] but maybe its because dpi is auto detected for px [13:46] seb128: I have to perform deskbar-applet: I will do it in few minutes, but I can take some if you wish [13:46] didrocks: no that's ok, enjoy the nice weather rather you are on holidays and already did a lot ;-) [13:47] asac: hmm...me either [13:47] seb128: yeah, what a great weather there! ;) [13:47] * asac needs a high dpi screen [13:48] asac: borrow a netbook [13:48] mdeslaur: does a mini 9 have high dpi? [13:48] asac: and try to install jaunty on it :) [13:48] asac: let me check, wife has one [13:48] i think i will try mini 9 ... i have that and it needs to be reinstalled anyway [13:48] * asac searches for UNR daily images [13:49] asac: UNR forces dpi to 96 [13:49] asac: install standard jaunty [13:49] mdeslaur: on what level? [13:49] asac: gnome i think, but I'd have to reinstall to make sure [13:51] mdeslaur: i will figure [13:51] * asac installs UNR regardless ;) [13:52] asac: yes, mini 9 is 135 dpi [13:52] great [13:52] so seems i have the hardware ;) [13:52] lets see if i have the time [13:52] asac: please try the standard jaunty desktop installer, just to see what my fuss is about [13:53] asac: don't install, just boot your mini 9 with it [13:53] mdeslaur: where can i download the usb image? [13:53] asac: download the iso and use the "USB Startup Disk Creator" to make a usb key [13:54] ok. i will do that after installing UNR ;) [13:54] asac: cool, thanks :) [14:02] hate hate hate g-s-d [14:03] "(gnome-settings-daemon:24832): GLib-GObject-WARNING **: cannot register existing type `GnomeSettingsPlugin' [14:03] (gnome-settings-daemon:24832): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed [14:03] (gnome-settings-daemon:24832): GLib-GObject-WARNING **: invalid cast from `GsdXrandrPlugin' to `' [14:03] " [14:06] seb128: two questions for you [14:07] seb128: if you have time after hating g-s-d :-) [14:07] kenvandine_wk: btw, planning to do foresight livecd/vm for 2.26.0? [14:08] vuntz: yup [14:09] vuntz: how close is it to announce? [14:09] i was up very late last night testing images :) [14:09] so i just need about an hour to refresh the latest packages and create images [14:09] kenvandine_wk: hrm, I'm doing some smoketesting, and then I'll work on preparing everything for the announcement [14:09] ok [14:09] * kenvandine_wk runs the script :) [14:10] vuntz: shoot [14:10] kenvandine_wk: but I guess this won't be before 6-7 hours (to give more time to translators for the release notes) [14:10] seb128: how is 2.26.0 looking for you? :-) [14:10] vuntz: any idea what could lead to those issues? I've that after applying a patch which has not a lot to do with it since g-s-d has been fixed to build correctly with -zdefs [14:10] vuntz: my live images last night worked well [14:10] vuntz: good! [14:11] seb128: no idea about the errors [14:12] my second question isn't actually just for you... It's a dumb user question: is it normal that security updates of hardy also contain version bumps? [14:13] * vuntz saw a new glib coming with a security bugfix... and tons of other changes [14:13] vuntz: GNOME glib or glibc? no it should not, are you sure you don't have -updates too? [14:13] seb128: glib, and we don't use -updates on the server [14:15] seb128: done, I overwrite and upgraded the repository format to latest bzr one. bug #344832 [14:15] Launchpad bug 344832 in deskbar-applet "Please, sponsor deskbar-applet 2.26.0 into jaunty" [Wishlist,Triaged] https://launchpad.net/bugs/344832 [14:15] seb128: glib2.0 (2.16.6-0ubuntu1.1) hardy-security; urgency=low ... Thu, 12 Mar 2009 16:46:11 -0500 [14:15] hey vuntz o/ [14:15] or maybe I'm misreading the apt-listchanges output [14:16] vuntz: what is written in the apt-listchanges log? [14:16] vuntz: https://edge.launchpad.net/ubuntu/hardy/+source/glib2.0/2.16.6-0ubuntu1.1 [14:17] seb128: sure, but hardy didn't contain 2.16.6 in the first place [14:17] it was something like 2.16.3 [14:17] hum [14:17] let me check [14:18] seb128: you uploaded 2.16.6 to hardy-proposed on Wed, 17 Sep 2008 13:54:46 +0200 [14:19] (not that I really care, I was just surprised) [14:20] vuntz: I'm asking for confirmation, 2.6.6 was in updates for a while but I'm not sure that's wanted or an error [14:20] to push it to security [14:20] vuntz: that's wanted, they do security on top of -updates [14:21] okay [14:21] sounds weird [14:21] but again, I don't care in my case ;-) [14:22] so 2.26.0 looks fine here. Good [14:22] yes [14:22] * vuntz goes to ask people from other distros [14:24] vuntz: they do that to avoid having a -updates-security or having to push all the fixes twice [14:25] slomo: hi, do you think you could do the librsvg libglade and pango updates for debian? [14:25] slomo: we are on syncs for those and that would be nice to keep it this way ;-) [14:27] seb128: yes, i can do them today or tomorrow i guess [14:27] seb128: oh, for librsvg i want to wait until it's in testing (http://packages.qa.debian.org/libr/librsvg.html) blocked by gtk [14:28] slomo: ok thanks [14:38] pulseaudio is crashing a lot for me today; E: cpulimit.c: Received request to terminate due to CPU overload. [14:41] lool - you need a bigger CPU ;) [14:42] One would hope that a dual core 2 GHz x86-64 would be enough these days :-/ [14:53] vuntz: any idea what could lead to gconf calls crashing in orbit when using autostart desktops? [14:54] vuntz: we have a small script to migrate some gnome-panel configuration [14:54] vuntz: when run using an autostart (ie letting gnome-session run it) setting a key using python gconf crashes in orbit code [14:55] oooh, that's nastily bad ;-) [14:55] no idea, sorry [14:56] hum ok [14:56] vuntz: and any idea why the error for this autostart don't show up in .xsession-errors? [15:02] * kenvandine_wk -> lunch [15:07] seb128: nope [15:08]