Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: kded --check crash_function: __GI_raise executable: /usr/bin/kded kernel: 3.1.4-1.fc16.x86_64 pid: 12944 pwd: /home/pasha/imus/fileSets/jar reason: Process /usr/bin/kded was killed by signal 6 (SIGABRT) time: Ср. 07 дек. 2011 15:27:01 uid: 1000 username: pasha backtrace: Text file, 22679 bytes dso_list: Text file, 3889 bytes environ: Text file, 5808 bytes event_log: Binary file, 1589 bytes maps: Text file, 17187 bytes smolt_data: Binary file, 3696 bytes xsession_errors: Binary file, 759 bytes comment: :Manual start after crash: :kded --check && kded --new-startup var_log_messages: :Dec 7 13:34:06 hubbitus dbus[1093]: [system] Rejected send message, 11 matched rules; type="error", sender=":1.42" (uid=1000 pid=1715 comm="kded4 ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.2" (uid=0 pid=1038 comm="/usr/sbin/NetworkManager --no-daemon ") :Dec 7 13:34:06 hubbitus dbus-daemon[1093]: dbus[1093]: [system] Rejected send message, 11 matched rules; type="error", sender=":1.42" (uid=1000 pid=1715 comm="kded4 ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.2" (uid=0 pid=1038 comm="/usr/sbin/NetworkManager --no-daemon ") :Dec 7 15:27:01 hubbitus abrt[12945]: Saved core dump of pid 12944 (/usr/bin/kded) to /var/spool/abrt/ccpp-2011-12-07-15:27:01-12944 (2433024 bytes) :Dec 7 15:27:19 hubbitus abrt[13011]: Not dumping repeating crash in '/usr/bin/kded'
Created attachment 541918 [details] File: environ
Created attachment 541919 [details] File: event_log
Created attachment 541920 [details] File: backtrace
Created attachment 541921 [details] File: smolt_data
Created attachment 541922 [details] File: coredump
Created attachment 541923 [details] File: xsession_errors
Created attachment 541924 [details] File: maps
Created attachment 541925 [details] File: dso_list
This chokes on: kdFatal() << "DCOP communication problem!" << endl; Your DCOP isn't working, just like your D-Bus (see bug #757073). Something must be seriously screwed up on your system.
May be. But I beleave I do nothing according to DCOP settings. How I can detect it? Why you close it as NOTABUG if it crashed??
It's crashing because dcopserver is not available (dcop is kde3's predecessor to dbus). Now, dcopserver itself being not available could be for a multitude of reasons, but as Kevin hinted at, it's seems likely there's something seriously wrong on your box (or your user settings or session), that's causing both dbus and dcop to fail similarly.
Rex, in any case, even if (I think it is not, but it is another speak) my system is misconfigured I think hard crash is not god fashion error handling in software??? And off course kde3 is not so interesting in nowadays, I'll not even reopen it.