/srv/irclogs.ubuntu.com/2008/04/16/#ubuntu-desktop.txt

Karger1978hello03:39
Karger1978anyone here03:39
jaymani am03:39
e-uoaphysis this the gnome/xfce/kde desktop team, or just the gnome team?05:18
Amaranthe-uoaphys: gnome05:18
Amaranthseeing how the ubuntu desktop is gnome :)05:18
e-uoaphysoh05:19
e-uoaphysthere is no kubuntu-desktop chan tho :(05:19
Amaranthtry #kubuntu-devel05:19
Amaranththe only thing kubuntu has to deal with is the desktop :P05:19
Amaranthwell, almost the only thing05:19
e-uoaphysright on05:20
e-uoaphysthx05:20
=== asac_ is now known as asac
dholbachgood morning07:20
crevettehello dholbach07:25
dholbachhi crevette07:27
ajmitchhi dholbach08:08
dholbachhi ajmitch - how are you doing?08:08
ajmitchgood, how are you?08:08
dholbachgood too - thanks08:09
* ajmitch is just here due to hitting an annoying bug after a hardy upgrade :)08:09
dholbachwhat happened?08:09
ajmitchwhen I login, the desktop background & icons frequently don't appear08:09
dholbachugh08:10
ajmitchI haven't seen anything in ~/.xsession-errors that's useful yet08:10
dholbachanything in .xsession-errors?08:10
dholbachhm08:10
ajmitchjust starting up the laptop now to see if it happens again08:10
ajmitchhowever, if I start nautilus, then go to gconf-editor & toggle its 'show desktop' off & then on, it'll appear08:11
dholbachsounds like seb128 will be interested to hear it08:11
ajmitchhaven't filed a bug yet due ot lack of useful info08:11
ajmitchand of course, it didn't happen this time...08:12
crevettesalut les telepathistes08:12
* ajmitch hates bugs that randomly aren't reproducable08:12
dholbachhi Zdra, hi cassidy08:12
dholbachhi crevette08:12
crevette:)08:12
dholbachajmitch: I know what you mean :/08:12
ajmitchand there he is... :)08:13
crevettehey08:13
Zdrahi dholbach08:13
cassidymorning dholbach08:13
seb128hello everybody08:13
ajmitchhi seb12808:14
ajmitchbah, logout, come back in, and it's working fine still08:16
ajmitchit's only because I'm trying to reproduce it that it does this to me...08:16
seb128what bug?08:17
ajmitch03:09 < ajmitch> when I login, the desktop background & icons frequently don't appear08:17
ajmitch03:11 < ajmitch> however, if I start nautilus, then go to gconf-editor & toggle its 'show desktop' off & then on, it'll appear08:18
ajmitchtrying to get useful info before I file a bug08:18
ajmitchfrom a gutsy->hardy upgrade08:19
seb128_ups, being disconnected08:19
seb128_what is the bug?08:19
ajmitch03:17 < ajmitch> 03:09 < ajmitch> when I login, the desktop background & icons frequently don't appear08:19
ajmitch03:17 < ajmitch> 03:11 < ajmitch> however, if I start nautilus, then go to gconf-editor & toggle its 'show desktop' off & then on, it'll appear08:19
ajmitch03:18 < ajmitch> trying to get useful info before I file a bug08:19
ajmitch:)08:19
seb128_ah08:20
seb128_is nautilus running when you don't get the icons?08:20
ajmitchI'm trying to reproduce it now so that I can tell you08:20
ajmitchbut it's misbehaving & giving me a desktop each time, unlike this morning08:21
seb128_ok08:22
seb128_slomo_: your fix for the crash at exit thing didn't work08:23
ajmitchalright, I think I've got it now :)08:25
* ajmitch put the audio cd back in the drive...08:25
ajmitchand yes, nautilus is running08:26
seb128_do you get the context menu on the desktop etc?08:27
ajmitchno08:27
seb128_can you get a nautilus stracktrace?08:27
ajmitchno icons, context menu, or desktop wallpaper08:27
seb128_and do you have anything about nautilus in .xsession-errors,08:27
seb128_?08:27
ajmitch** (nautilus:13298): WARNING **: Unable to add monitor: Not supported08:28
ajmitchis the only thing there08:28
seb128_that's normal08:28
seb128_hum, k08:28
ajmitchI figured as much08:28
ajmitcha stacktrace, although nautilus hasn't crashed?08:29
seb128_yes08:31
seb128_just to know if some thread is stucked on something08:31
ajmitchwould you like me to kill -11 the running process then?08:31
seb128_or attach gdb to it and "thread apply all bt full" and attach that to paste.ubuntu.com08:32
ajmitchFWIW, nautilus  13298    ajmitch    3u     unix 0xeebe5380            56278 socket08:33
ajmitchstat64("/home/ajmitch/.recently-used.xbel", {st_mode=S_IFREG|0644, st_size=118622, ...}) = 008:33
ajmitchread(3, 0x819489c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)08:33
ajmitchgettimeofday({1208331188, 315370}, NULL) = 008:33
ajmitchpoll( <unfinished ...>08:33
ajmitchconstantly trying to read from a socket08:33
seb128_that is weird08:33
ajmitchI noticed that the only time it happened this evening was when I put the audio cd back in08:34
* ajmitch took it out because rhythmbox was loading every time I logged in08:34
seb128_right, known bug08:35
ajmitchargh, hit the data cap, downloading -dbg packages at 64kbps is painful08:35
=== seb128_ is now known as seb128
ajmitchI've used apport-cli to put in a bug for now, though it didn't appear to attach anything useful :)08:44
* ajmitch is forced to download at 1% of the usual ADSL speed, so it'll take awhile to get information08:45
seb128ajmitch: I think there is some other bug about the same issue08:49
ajmitchoh that's good08:49
seb128not really08:49
seb128those are likely incomplete or already closed08:50
ajmitchgood that I may be able to shed some light on someone else's problem then?08:50
seb128not sure what we can do without a way to trigger the issue, or somebody having the issue debugging the code08:50
seb128right08:50
seb128though I'm not sure what information would be useful08:50
ajmitchknowing what socket it's trying to read may be a help, I guess08:51
ajmitchif that's related to the issue08:51
seb128the socket reading is normal I think08:52
seb128it does that too here08:52
seb128what is weird is that it's trying to read the recently-used08:52
seb128does it do that in loop too?08:52
ajmitchyes08:53
ajmitchbut I'm not sure if that's just normal behaviour, it's not doing stat on it very often08:53
ajmitchhttp://paste.ubuntu.com/7178/ isn't useful, is it?08:58
slomo_seb128: hm? works for me, at least for the crashes i got... are there any current bugreports with backtrace?08:58
seb128is that the only thread?08:58
seb128and no, you need libglib2.0-0-dbgsym08:58
slomo_maybe there's more than one crash08:58
ajmitchgdb didn't show any more info, and I'm grabbing libglib2.0-0-dbgsym now08:59
seb128slomo_: I still have the bug on my box, what information do you need?08:59
slomo_seb128: you have new libgtk2.0-cil and new libgnome2.0-cil? can you reproduce it easily?08:59
seb128slomo_: yes, I've the current versions and it happens every time I close f-spot or tomboy09:00
slomo_hm hmm09:00
seb128dpkg -l libgtk2.0-cil libgnome2.0-cil09:00
seb128ii  libgnome2.0-cil      2.20.0-2ubuntu2      CLI binding for GNOME 2.2009:00
seb128ii  libgtk2.0-cil        2.12.0-2ubuntu2      CLI binding for the GTK+ toolkit 2.1209:00
slomo_let me install f-spot, one moment09:00
slomo_yes these are the correct versions09:00
seb128slomo_: what is useful for such crashes? the gdb stracktrace from the interpreter?09:02
slomo_yes, i can reproduce it with f-spot here09:03
seb128ok09:03
slomo_so there's more than one crasher on exit *sigh*09:03
seb128:-(09:03
slomo_i'll care for that09:03
seb128thanks09:04
seb128do you have any idea about the issue?09:04
slomo_not yet09:04
seb128you might want to try tomboy too and see if that's the same bug09:04
slomo_yes09:04
ajmitchseb128: new gdb paste at http://paste.ubuntu.com/7179/09:04
seb128ajmitch: ok, it seems to not be stucked on anything then09:05
slomo_seb128: looks like the same crash that i fixed09:05
slomo_seb128: might be that f-spot does stuff different from my test cases09:05
* ajmitch is logging out to see if it'll happen again09:05
ajmitchor not, I hit logout & it's just not happening...09:06
ajmitchhm09:07
slomo_seb128: yeah, problem is that f-spot does "exit()" instead of stopping the main loop first09:07
seb128_slomo_: ah, so application bug now?09:08
slomo_seb128: only f-spot and tomboy?09:08
seb128_slomo_: that I noticed, I'm not using other mono applications09:09
slomo_seb128: no, the fix in gtk# was not enough... but i see no solution for f-spot's behaviour in gtk#09:09
slomo_seb128: it's just that libgnome is very unfriendly to bindings :)09:09
seb128_bug #21709109:09
ubotuLaunchpad bug 217091 in gnome-subtitles "gnome-subtitles.exe crashed on exit (dup-of: 199496)" [Undecided,Invalid] https://launchpad.net/bugs/21709109:09
ubotuLaunchpad bug 199496 in gtk-sharp2 "Tomboy.exe crashed with SIGSEGV in exit()" [High,Fix released] https://launchpad.net/bugs/19949609:09
seb128_slomo_: that one is about gnome-subtitles09:09
slomo_is there a pygtk irc channel somewhere?09:09
slomo_would be nice to know how they handle that09:10
seb128_#pygtk on gimpnet09:10
slomo_or maybe no python appliction uses GnomeProgram :)09:10
slomo_seb128: tomboy does the same as f-spot *sigh*09:11
slomo_might be possible to fix for those two though09:12
slomo_yep, f-spot fix is a one-liner09:12
slomo_seb128: i'll give you a diff, can you care for the upload? i'm busy with other stuff atm09:13
slomo_seb128: http://pastebin.ca/98714909:13
seb128_slomo_: ok09:14
seb128_slomo_: thanks09:14
slomo_that's not the only place where f-spot does things wrong but should be the only one giving that behaviour09:14
seb128_bah, pastebin.ca is sloooow09:15
dholbachpaste.ubuntu.com? :)09:15
slomo_hmm09:16
seb128_slomo_: the website doesn't want to show your change09:16
slomo_i might have a better fix09:16
seb128_ok09:16
slomo_http://paste.ubuntu.com/7180/09:17
slomo_that's the old one09:17
seb128_thanks09:17
seb128_slomo_: the comment before seems to indicate they didn't use this call for a reason09:18
slomo_seb128: just the call alone wouldn't exit the application because there are still other threads running, quitting the main loop and exit works in every case09:18
slomo_(unless something blocks the main loop which would be a bug)09:18
seb128_ok09:21
slomo_whatever, i might find a better solution09:21
ajmitchargh09:24
ajmitchscreen #0: dimensions:    1280x800 pixels (289x21 millimeters) resolution:    112x968 dots per inch09:24
ajmitchno wonder gdm has 3 inch fonts09:25
mvoseb128_: have  you seen reports aobut scrollkeeper crashing with double-linked lists failures?10:14
seb128_mvo: look at the scrollkeeper list of bugs, plenty of those10:15
mvoI wonder if #218049 might be something like bad memory or so10:15
* mvo nods10:15
YokoZarajmitch: it seems like there was a regression in the last gdm update10:15
YokoZarsince that's also when it started being the wrong resolution for me10:15
seb128_mvo: I've had no luck to trigger the issue or get an error when running it under valgrind though, I tried again some days ago10:15
ajmitchYokoZar: it's an intel driver thing10:16
ajmitchbug 10732010:16
ubotuLaunchpad bug 107320 in xorg-server "Large font in the GDM login text field after installing xserver-xorg-video-intel which report monitor having 289x21 millimiters (dup-of: 151311)" [High,Confirmed] https://launchpad.net/bugs/10732010:16
ubotuLaunchpad bug 151311 in xserver-xorg-video-intel "DDC report some ridiculous physical screen size (Mostly on Intel driver, and some ATI)" [High,In progress] https://launchpad.net/bugs/15131110:16
YokoZarajmitch: that's odd, I don't have intel video...10:26
YokoZarThough I do have the package installed10:27
ajmitchyeah, I misspoke, it's really hardware at fault, and newer drivers believing the dimensions passed to it10:27
mvoseb128_: ok, thanks10:27
ajmitch(from what I've read so far about buggy EDID values)10:27
dholbachmvo, seb128_: shall we change the breaks of evolution-data-server on evolution-scalix to a conflicts for hardy? this will fix upgrades and slangasek just removed evo-scalix from hardy10:33
dholbachbug 19376410:33
ubotuLaunchpad bug 193764 in evolution-scalix "evolution-scalix FTBFS with current evolution" [High,Fix released] https://launchpad.net/bugs/19376410:33
seb128_dholbach: why is the breaks not correct?10:33
dholbachsee comment 5 on that bug10:34
dholbachmvo is the best person to answer10:34
seb128_ok10:34
seb128_I've no opinion about that, did you try asking gicmo about fixing the build?10:35
dholbachseb128_: yes, he was in the bug conversation10:35
seb128_anyway feel free to do the change but ask mvo, I think there is a replaces which is required too10:35
seb128_not sure if he still has a pending upload for this one10:35
dholbachyes, best if mvo does it10:36
dholbachthanks guys10:37
mvodholbach: yes10:37
seb128_brb, trying gvfs changes10:37
mvoseb128_: the breaks implementation is not that great in the resolver, its mostly designed around the case when it can upgrade a package, if it can't it easily falls flat on its face10:38
loolseb128: Will you continue sponsoring the cheese upload?12:00
crevettehello lool12:00
loolHi crevette12:04
pcjc2Hi, I guess people are busy getting last minute fixes for Hardy... I've prepared a couple of patches (epiphany and nautilus) for some annoying usability issues12:14
seb128lool: you are welcome to do the upload if you want12:14
seb128hey pcjc212:14
pcjc2I'm not a developer12:14
seb128pcjc2: what issues do those fix?12:14
pcjc2Bug #181128 (marked as fix-comitted, but isn't fixed)12:15
ubotuLaunchpad bug 181128 in epiphany-browser "clicking on a link to a document does not open it" [Medium,Fix committed] https://launchpad.net/bugs/18112812:15
pcjc2The patch backports changes from epiphany's SVN repository, and "works nicely for me"12:15
pcjc2This requires more thought, but I have a fix which works for me... bug #21799712:16
ubotuLaunchpad bug 217997 in nautilus "Incorrect icons displayed for mimetypes installed in hicolor theme only" [Undecided,New] https://launchpad.net/bugs/21799712:16
seb128pcjc2: are you sure all those changes are required? only one of the commit mention the issue12:17
pcjc2The first one mentions that it is part of the right bug#12:18
pcjc2 Add a kung fu death grip to keep us alive. Part of bug #51383712:18
seb128I doubt we will spend efforts now to fix this issue, that's not the default browser and we got only one bug about that12:18
seb128we will likely update to the new bug fix version in hardy-updates rather12:19
pcjc2The second (committed right after), adds another, the third is the bugfix. The fourth labeled "Cleanup" was comitted right after, in the same file12:19
pcjc2that last one might not be necessary12:19
pcjc2sure, the debdiff is there when it is needed. I just wasn't sure how much extra pain was required for hardy-updates CF. getting the fix in before the release12:20
seb128it's late now to get changes accepted12:21
seb128and I don't think this one is worth going through freeze exception, testing, etc12:21
pcjc2The nautilus bug took a little bit of tracking down, there are various similar, but not quite the same bug reports - mostly relating to incomplete icon themes12:21
seb128as said it's not the default browser and we got only one bug about it12:21
pcjc2seb128: I think I agree with you, given that its not default - I forget that, since its always one of the first apps I install12:21
seb128and I don't think many people use the autoopen thing12:22
seb128but thanks for your work, we will consider the change12:22
pcjc2the symptom is that clicking on a .pdf (something I do regularly as an Engineer surfing for datasheets), the pdf downloads somewhere anonymous, probably with a name like 328784.pdf (whatever it was called on RS / Farnell's server), and you get no notification. It used to just open in evince12:24
seb128right, I understand the bug12:25
seb128when clicking on a pdf I get the "download or open" dialog12:25
seb128not sure what option is the default one12:25
pcjc2in Epiphany?12:25
seb128anyway as said we will get it to hardy or hardy-updates12:25
seb128yes12:25
pcjc2Until applying that patch, I got silence from it!12:25
seb128that's because you use the preferences option to automatically download and open12:26
pcjc2After the patch, I got the download or open dialog12:26
pcjc2Ah - its buried somewhere, I'll look for it, thanks12:26
seb128it's not, it's on the first tab in the preferences dialog12:26
* pcjc2 hides12:27
pcjc2it would appear that the patch just makes it show the SaveAs / Open dialog and isn't a full fix then.12:28
seb128ok, don't bother too much12:29
seb128upstream said he would roll a new tarball soon to fix issues12:29
seb128and we will get it in hardy or hardy-updates12:29
pcjc2thats good to know. I see they dropped Mozillla support in trunk anyway12:30
seb128pcjc2: can you send the nautilus patch on the upstream mailing list? I'm not sure it's correct, gtk should be doing the right thing there12:35
pcjc2I sent it already12:37
seb128ok, I'll read comments there then12:38
seb128thanks12:38
pcjc2none-so far, I think the majority of bugs I opened on bugzilla.gnome.org are still unconfirmed ;) (Perhaps that says something about me - not sure!)12:38
seb128depends of the product, but the nautilus upstream hackers get too many bugs to really read bugzilla12:39
seb128they reply on the list usually though12:39
pcjc2ok, perhaps I'll take it up there12:39
seb128you just say you already did?12:40
pcjc2maiiling list12:40
pcjc2http://bugzilla.gnome.org/show_bug.cgi?id=52832012:40
ubotuGnome bug 528320 in View as (Icons or List) "Incorrect icons displayed for apps installing icons in hicolor theme" [Normal,Unconfirmed]12:40
seb128right12:40
pcjc2sorry, I'm tired... I see you suggested mailing list above, not bugzilla12:41
seb128I specifically asked if you can send it on the mailing list12:41
seb128and you said you already did?12:41
pcjc2I misread, I will do it now12:41
seb128ok, that's alright12:41
seb128just send it on the list if you want to get a reply ;-)12:41
kwwiiseb128: I have a fix for the screensaver (the filename was wrong in the desktop file)12:42
seb128kwwii: url?12:52
kwwiiseb128: http://sinecera.de/human-theme_0.17.dsc13:02
seb128kwwii: ok13:04
seb128hey pedro_13:04
* seb128 looks at mvo13:04
seb128bug #21583913:04
ubotuLaunchpad bug 215839 in python-central "hardy upgrade fails with python-central crash and gedit segfault" [High,Confirmed] https://launchpad.net/bugs/21583913:04
pedro_hello seb12813:04
seb128mvo: something in the gedit postinst crash, but there is no gedit specific calls there13:04
seb128ok, doing some cd testing again13:09
seb128could somebody sponsor the human-theme update listed before? dholbach? I'll do it otherwise after this round of testing13:09
dholbachkwwii: are all the changes in bzr already?13:10
kwwiidholbach: yes13:15
kwwiiall I did was add "-screensaver" to a file name in the dekstop file for the screensaver13:15
dholbachkwwii: OK, uploaded13:16
dholbachkwwii: might be sitting in the archive admin's queue now13:16
* mvo looks back at seb12813:18
kwwiidholbach: cool, thanks13:25
seb128re14:00
seb128did anybody do the sponsoring?14:00
seb128pitti: any opinion on http://bugzilla.gnome.org/show_bug.cgi?id=526308?14:01
ubotuGnome bug 526308 in programs "nautilus cannot eject ipod while eject(1) does" [Major,New]14:01
pittiseb128: icky14:02
pittiseb128: I think our eject(1) still has the 'unmount all partitions before' patch, which would make that work14:02
seb128pitti: well, I've opened the bug because I've the issue on hardy, I can't eject my ipod from nautilus14:03
pittiseb128: I think when I had my father's ipod here, I only ejected from RB14:03
seb128pitti: the icon is removed but the ipod is still displaying the "do not unplug" screen14:03
seb128right, from rhythmbox works14:04
pittidoes that make a difference for you?14:04
pittiah14:04
seb128gnome-mount -e /dev/sdn doesn't14:04
pittiOdd, I had expected RB to use the same call14:04
seb128lemme check14:05
seb128pitti: execve("/usr/bin/gnome-eject", ["/usr/bin/gnome-eject", "--hal-udi", "/org/freedesktop/Hal/devices/vol"...], [/* 26 vars */]) = 014:06
seb128that's what rhythmbox does14:06
seb128pitti: execve("/usr/bin/gnome-mount", ["gnome-mount", "-e", "-b", "-d", "/dev/sdc"], [/* 25 vars */]) = 014:07
pittihm, gnome-mount -e just calls eject, too14:07
seb128that's nautilus14:07
pittiso RB calls it on a volume, and nautilus on a drive14:08
seb128right14:08
pittiseb128: do you get the same when using eject /dev/sdc1 vs. sdc?14:10
seb128no14:11
seb128sudo eject /dev/sdc works correctly14:11
seb128as do sudo eject /dev/sdc<n>14:12
pittiseb128: can you strace -e execve -f what RB and nautilus call eject with?14:17
seb128that's what I did before14:17
seb128ah, eject14:18
seb128not gnome-mount14:18
seb128ok14:18
seb128is gnome-mount calling eject? I though it was using hal for those14:18
pittioh, sorry, misread the code14:19
pittiit's only called if the device is in fstab14:19
seb128which is not the case14:19
pittiright14:19
seb128the fstab parsing code seems broken btw14:20
seb128strace shows it tries to stat UUID=numbers14:20
seb128but that's an another issue14:20
pittiargh, I wish dbus-monitor wouldn't be so terribly useless14:21
pittiseb128: hal --verbose=yes --daemon=no should display which kind of eject call is done; maybe that gives some enlightenment?14:21
seb128trying14:23
seb128brb, I managed to put my system in a state where the ipod is no detected, I hope the database didn't get corrupted because I unplugged it incorrectly after the failed eject14:24
jcastroseb128: need those desktop topics for openweek rsn!15:58
seb128jcastro: I'm pondering passing for this one, just too much to do15:59
jcastroseb128: no one else on the -desktop team?15:59
seb128well, you asked on the change and nobody stepped so apparently not ;-)16:00
jcastroheh16:00
mvopitti: could you have a quick look at #63450 ? my comment 21? it looks like hal restart fails, I wonder if you have a idea about it16:38
* mvo needs to leave now for ~1h but will read backlog16:38
pittimvo: ok, will have a look at it16:47
=== Mez is now known as fishfinder
=== fishfinder is now known as Mez
loolseb128: Do you recall that pygtk python wakeupfd thing?17:10
loolhttp://bugzilla.gnome.org/show_bug.cgi?id=48156917:10
ubotuGnome bug 481569 in gtk "Calling gobject.threads_init() causes a lot of wakeups" [Normal,Reopened]17:10
loolseb128: The patch is now ready, just replace the read(..., 1) with , 017:10
loolseb128: What do you think?17:10
seb128lool: it's late for hardy17:14
seb128it took us several day to notice the issue previous time17:15
loolseb128: It's useful to save power though17:15
seb128rather for hardy-updates17:15
loolHmm ok I thought it was safer to have in hardy than in hardy-updates17:17
seb128there is very few room for hardy now, every change means new CD builds and do the entire test grid again17:17
seb128maybe ask to slangasek if he's ok to get that between the rc and hardy images17:18
loolOk17:18
seb128uploads go to hardy-proposed, get testing there and are moved to hardy-updates17:18
seb128so it's usually ok to upload such changes to proposed and to give them enough testing before moving to updates17:19
seb128we will do that for GNOME 2.22.n updates too17:19
=== mvo_ is now known as mvo
mvopitti: thanks for your thoughts on the acpid thing, I have no idea why hald is hanging with it though, so I'm I can not currently sposnor it19:19
seb128_slomo: did you figure a patch for the crash on closing issue?21:44
slomoseb128_: not yet, talking with upstream now... the one i gave to you is correct though21:45
bhalehi slomo21:46
slomohi bhale21:46
kwwiiseb128_: have you seen bug #9950822:07
ubotuLaunchpad bug 99508 in compiz "Window titlebar displayed not right with compiz enabled" [Medium,Confirmed] https://launchpad.net/bugs/9950822:07
kwwiiseb128_: it seems there is an easy fix but it seems so simple I wonder22:08
seb128_kwwii: that's rather a question for amaranth or mvo, I don't really know about compiz22:09
Amaranthkwwii: please fix it :)22:09
Amaranthno more <tint> :)22:09
kwwiiseb128_: is it too late to add such a fix?22:09
kwwiiAmaranth: no, it is simpler than that it seems22:10
Amaranthoh, change that 0 to a 1 for left_width or whatever22:10
seb128_kwwii: there is some room between rc and hardy for easy changes22:10
kwwiiexactly22:10
seb128_but that seems a compiz bug, not a theme one22:10
Amaranthseems to fix it here22:11
Amaranthseb128_: it's a "wtf is going on here?" bug22:11
kwwiiseb128_: I'll test the change on my system without the error and if it does not change anything radically I can submit it...I was worried about submitting it and then b0rking everyone's system which works now22:12
Amaranthit seems to be a bad interaction between gtk-window-decorator, libmetacity, and the theme22:12
Amaranthand no one knows how to fix it anywhere except in the theme22:12
kwwiilol, the best reason to get a new theme...otherwise I will end up having to support ubuntulooks22:13
kwwiiI'll fix it, but not until tomorrow, just got home tonight, need a few hours of private time :-)22:14
seb128__re22:14
seb128__<seb128_> but that seems a compiz bug, not a theme one22:14
kwwiiright, but if this fixes it, so be it22:15
Amaranth<Amaranth> it seems to be a bad interaction between gtk-window-decorator, libmetacity, and the theme22:15
Amaranth<Amaranth> and no one knows how to fix it anywhere except in the theme22:15
=== seb128__ is now known as seb128
seb128changing the theme should be no issue22:17
seb128bug having compiz guys fixing the bug would be better ;-)22:17
Amaranthif there is an easier way to workaround the problem i have no interest in wasting my time22:19
Amaranthi could be using that time to read slashdot :P22:19
kwwii:-)22:19
seb128slomo: your gnome-user-share update in debian is still not good22:49
seb128"Syntax error on line 17 of /usr/share/gnome-user-share/dav_user.conf:22:49
seb128Invalid command 'TypesConfig', perhaps misspelled or defined by a module not included in the server configuration22:49
seb128spawning httpd failed22:49
seb128"22:49
seb128slomo: and you need to clean the old debian specific autostart on upgrade since that's a conffile22:50
mvoseb128: still here?23:27
seb128mvo: yes23:27
mvoseb128: could you please have a look at the last comment in bug #63450 ?23:27
ubotuLaunchpad bug 63450 in acpid "acpid install fails (because of hal running)" [High,In progress] https://launchpad.net/bugs/6345023:27
mvolooks like something funny with policykit23:28
seb128mvo: no idea, is that still the old dbus version running? maybe it doesn't support some new format or something23:30
mvohm, maybe pitti has a idea about #63450 (last comment)23:31
mvoseb128: yeah, could be. I wonder if some dependencies needs fixing23:31
seb128mvo: I think he's away for the night23:31
seb128mvo: well, the issue is not dependencies if that's the case but dbus needing to be restarted and not reloaded23:32
seb128but restarting dbus on upgrades is not a good idea usually23:32
seb128maybe walters has an idea about the warning ;-)23:32
mvoseb128: ok, yeah - if its the dbus restart problem, then there is nothing we can do and we can not apply the patch as it is23:33
mvo(nothing we can do for now :)23:33
mvoseb128: but thanks for your help, I updated the bug, I think I should leave for bed now23:35
seb128mvo: yeah, me too, you are welcome23:35
pochuseb128: do you think we will have WebKit in main for Intrepid?23:36
seb128pochu: depends on what in GNOME is using it, but that's likely yes23:37
pochuseb128: because Liferea has a WebKit backend for some time, and I'll look at it to see if it's feasible a switch to it23:37
pochuslomo: ^-- what would you think about that?23:38
seb128what does it bring over the current version?23:39
walterslaunchpad is not responding for me23:39
seb128walters: weird23:39
seb128walters: "Error org.freedesktop.DBus.Error.Failed: Element <standard_system_servicedirs> not allowed inside <busconfig> in configuration file^M" is the warning23:40
seb128rather error23:40
seb128while reloading the system message bus config23:41
waltersis this on a major distro upgrade?23:42
waltersdist-upgrade?23:42
seb128yes23:42
seb128that's a dapper to hardy upgrade23:42
waltersyeah, not much we can do about that...the new config file is on disk, the old daemon doesn't grok it23:42
seb128oh, no, the error is gutsy to hardy apparently23:42
waltersyou guys might want to look at what fedora is doing with preupgrade, it's generally a much more reliable way of upgrading the OS23:43
seb128ok, that's what I though23:43
seb128this "doesn't restart dbus" is somewhat annoying23:44
seb128walters: right, we are not likely to do major changes before hardy now though ;-)23:44
waltersyep, i understand23:44
waltersi'm not sure what the best approach would be; if there is a way to suppress the postinst script on dist-upgrade that might be a workaround23:46
waltersdoes the daemon die after that?23:46
seb128well, mvo left now, but reading the bug they try to restart hal apparently and hal hangs after this error23:47
seb128the easy workaround is to not do the restart in the postinst23:49
seb128we should probably just recommend people to restart the box after the upgrade to get everything running correctly anyway23:50
waltershm, new hal may need some feature from the newer dbus23:50
waltersyeah, you've always had to restart anyways though23:50
waltersglibc23:50
=== MacSlow_ is now known as MacSlow

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!