problems with today's rawhide

[Marcus Schuetz]

Gerald Henriksen wrote:
> On Sun, 25 Jan 2004 21:23:25 -1000, you wrote:
> 
> 
>>The GNOME menus and logout is hosed in my clean install of rawhide from 
>>2 days ago.
> 
> 
> I believe the Gnome logout problem is a known issue with Gnome (I read
> about it back in late December).  The workaround if you desire is to
> disable the logout confirmation prompt.
> 
> 
Oh, it's worse than that: updating to gnome-vf2 2.5.5-3 and libgnome 
2.5.3-1 on 01/21 did not only make the menu disappear, but it also got 
rid of logout confirmation dialog and you dropped back to gdm when 
pressing logout. But now after updating to gnome-vfs2 2.5.5-4 pressing 
logout hangs gnome-session and you get this error in .xession-errors:


Gdk-ERROR **: The program 'gnome-session' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
   (Details: serial 1464 error_code 8 request_code 42 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() 
function.)
aborting...

which I guess is BAD (tm). The only way to recover is to press 
ctrl-alt-backspace and kill X which brings you back to gdm.

I also have the problem that esd is misbehaving, creating 60+ core files 
at startup (I guess because it tries to re-spawn) with the message :
Unable to connect to UNIX socket /tmp/.esd/socket in .xsession-errors
and of course I get no gtk-event sounds (sound from xmms, totem, etc. 
works, though). I've disabled esd for now.

So with the freeze in effect is there a chance to get this fixed anytime 
soon?

:: M a r c u s