[kde-linux] KDED crashes on KDE 3.5.8

[M K]

So well, after harvesting through the whole Internet (this is how it feels like), I found something that seems REALLY to be related to my problem (duh, the thing that is most difficult to find is always lying directly in front of someone's nose, and I've already looked at bugzilla.redhat.com).

The buf seems not really to be fixed in the version 3.5.6, but just a month ago - a report about the same problem as mine is to find at https://bugzilla.novell.com/show_bug.cgi?id=336627#c332102. There is a patch, too - but I assume that to apply this patch, the source code of KDE is needed (after that it has to be compiled and installed, too). One of my pals (relatively new to Linux, too) has tried to compile the source of KDE 3.5.7.1 and got some weird errors about missing "make rules", so it doesn't seems to be as easy. And the patched RPM seems not to be there - when YUM with an enabled kde-repository upgrades everything, after that the bug is still at large...

So what now? Could anyone possibly try to compile a patched RPM before there's an official release? @david: maybe such a RPM could solve your problems, too...

Max






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

_________________________________________________________________
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/20080125/e8c447f7/attachment.html>