<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hello,<br><br>I've already seen in the bugzilla that (nearly) the same bug was patched in <br>the KDE version 3.5.6.9 - but the version I'm talking about is 3.5.8.7 (on <br>Fedora Core 7) or 3.5.8.9 (on FC8). So I really don't know ith it's "still" a <br>bug or a config error.<br><br>After installing and configuring FC7 or FC8 with Kickstart and some <br>post-install scripts, during logout from KDE every user gets the error <br>message window "The application KDE Daemon (KDED) has crashed and caused <br>abort signal 6". I don't see a way to read what is in the backtrace, because <br>the window disappears at once. (Is there maybe an option to activate saving <br>backtraces?) After that, the whole Xserver crashes, too - not every time, but <br>randomly with probability of app. 1/4. So the user either sees the login <br>screen again or he/she sees only a black screen with mouse pointer. It's not <br>possible to restart X - after deleting the .X0-lock and typing "startx", the <br>NVIDIA logo appears for one second and then there is the message ":0 Can't <br>open display", pressing Crtl+Alt+Backspace just kicks the user to the text <br>console, and even changing the init mode (init 3; init 5) doesn't do anyting, <br>so the only way to get X back on air is to reboot.<br><br>Nothing above the error is displayed in the Xorg.0.log. The only (more or <br>less) useful information is to find in the file .Xsession-errors of the user <br>doing the login/logout:<br><br><br>================================================<br>..<br>startkde: Starting up...<br>...<br>ASSERT: "!name.isEmpty()" in kdirlister.cpp (969)<br>X Error: BadWindow (invalid Window parameter) 3<br>Major opcode: 19<br>Minor opcode: 0<br>Resource id: 0x1c00007<br>libpng error: Read Error<br>startkde: Shutting down...<br>klauncher: Exiting on signal 1<br>process 5279: arguments to dbus_message_new_method_call() were incorrect, <br>assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c <br>line 1074.<br>This is normally a bug in some application using the D-Bus library.<br>D-Bus not built with -rdynamic so unable to print a backtrace<br>Last DCOP call before KDED crash was from application 'DCOPServer'<br>to object '', function 'applicationRemoved(QCString)'.<br>KCrash: Application 'kded' crashing...<br>Warning: connect() failed: : No such file or directory<br>KCrash cannot reach kdeinit, launching directly.<br>libpng error: Read Error<br>startkde: Running shutdown scripts...<br>startkde: Done.<br>================================================<br><br>...and because I'm relatively new to Linux, the information is not really <br>helpful. Can anyone say what the error could be? Please help!<br><br>Thanks,<br><br>Max K.<br><br /><hr />Express yourself instantly with MSN Messenger! <a href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'>MSN Messenger</a></body>
</html>