[Bug 123273] kded often crashes on launch

Robert Persson ireneshusband at yahoo.co.uk
Sat Jul 28 16:44:51 UTC 2007


You have been subscribed to a public bug:

Often kded will crash as kde starts up. More often than not it will
relaunch, but sometimes I find that it hasn't relaunched. I typically
find this out when something won't print and I have to restart kded from
the command line.

Unfortunately the backtrace when it crashes claims to be useless. If you
could tell me how to furnish you with some more useful information I
would be grateful.

I am also the reporter of #120893 (kded hogs cpu), just in case these
two bugs are connected. I haven't experienced #120893 in quite while.
However this crash bug occurs quite a lot—perhaps 30%-40% of the time.

One oddity that might be worth mentioning is that when the trash applet
launches I usually (but not always) see a box with a progress bar pop
up, hang at 0% for a good while, and then disappear. No further icons or
applets appear in the panel until this box has closed. Nor will any
icons appear on the desktop until it has done so. The kded crash
notification appears after this progress bar has appeared and
disappeared.

The backtrace, for what it is worth, is as follows:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233348384 (LWP 6446)]
[New Thread -1365247088 (LWP 6555)]
[New Thread -1352688752 (LWP 6554)]
[New Thread -1344296048 (LWP 6553)]
[New Thread -1335903344 (LWP 6552)]
[New Thread -1327510640 (LWP 6551)]
[New Thread -1319117936 (LWP 6550)]
[New Thread -1310725232 (LWP 6549)]
[New Thread -1302332528 (LWP 6548)]
[New Thread -1292592240 (LWP 6546)]
[New Thread -1284199536 (LWP 6545)]
[New Thread -1275806832 (LWP 6544)]
[New Thread -1267414128 (LWP 6543)]
[New Thread -1259021424 (LWP 6542)]
[New Thread -1242236016 (LWP 6541)]
[New Thread -1250628720 (LWP 6540)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7d1e05e in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7cad8fe in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

** Affects: kdelibs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
kded often crashes on launch
https://bugs.launchpad.net/bugs/123273




More information about the kubuntu-bugs mailing list