[kde-linux] KDED crashes on KDE 3.5.8

M K overlord_3d at hotmail.com
Wed Jan 23 12:46:27 UTC 2008


Hello,

I've already seen in the bugzilla that (nearly) the same bug was patched in 
the KDE version 3.5.6.9 - but the version I'm talking about is 3.5.8.7 (on 
Fedora Core 7) or 3.5.8.9 (on FC8). So I really don't know ith it's "still" a 
bug or a config error.

After installing and configuring FC7 or FC8 with Kickstart and some 
post-install scripts, during logout from KDE every user gets the error 
message window "The application KDE Daemon (KDED) has crashed and caused 
abort signal 6". I don't see a way to read what is in the backtrace, because 
the window disappears at once. (Is there maybe an option to activate saving 
backtraces?) After that, the whole Xserver crashes, too - not every time, but 
randomly with probability of app. 1/4. So the user either sees the login 
screen again or he/she sees only a black screen with mouse pointer. It's not 
possible to restart X - after deleting the .X0-lock and typing "startx", the 
NVIDIA logo appears for one second and then there is the message ":0 Can't 
open display", pressing Crtl+Alt+Backspace just kicks the user to the text 
console, and even changing the init mode (init 3; init 5) doesn't do anyting, 
so the only way to get X back on air is to reboot.

Nothing above the error is displayed in the Xorg.0.log. The only (more or 
less) useful information is to find in the file .Xsession-errors of the user 
doing the login/logout:


================================================
..
startkde: Starting up...
...
ASSERT: "!name.isEmpty()" in kdirlister.cpp (969)
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1c00007
libpng error: Read Error
startkde: Shutting down...
klauncher: Exiting on signal 1
process 5279: arguments to dbus_message_new_method_call() were incorrect, 
assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c 
line 1074.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Last DCOP call before KDED crash was from application 'DCOPServer'
to object '', function 'applicationRemoved(QCString)'.
KCrash: Application 'kded' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
libpng error: Read Error
startkde: Running shutdown scripts...
startkde: Done.
================================================

...and because I'm relatively new to Linux, the information is not really 
helpful. Can anyone say what the error could be? Please help!

Thanks,

Max K.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-linux/attachments/20080123/faf6b2ba/attachment.html>


More information about the kde-linux mailing list