Bug 183921

Summary:	Updating software then error
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Erik Schuhrke <nights>
Component:	kded	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Erik Schuhrke 2009-02-10 17:22:32 UTC

Version:           kded4 (using KDE 4.1.3)
OS:                Linux
Installed from:    I Don't Know

doing normal updates then at end of process recieved this error.

Application: KDE Daemon (kded4), signal SIGSEGV
(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 0x7fcc21a6d6f0 (LWP 6117)]
(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)
0x00007fcc2139f5f0 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 6117)]

Thread 1 (Thread 0x7fcc21a6d6f0 (LWP 6117)):
#0  0x00007fcc2139f5f0 in nanosleep () from /lib/libc.so.6
#1  0x00007fcc2139f447 in sleep () from /lib/libc.so.6
#2  0x00007fcc20abc55f in ?? () from /usr/lib/libkdeui.so.5
#3  0x00007fcc20abce9a in KCrash::setApplicationName ()
   from /usr/lib/libkdeui.so.5
#4  0x00007fcc20ba9052 in ?? () from /usr/lib/libkdeui.so.5
#5  0x00000000019e4b68 in ?? ()
#6  0x00007fcc20ba905f in ?? () from /usr/lib/libkdeui.so.5
#7  0x0000000001a847d8 in ?? ()
#8  0x00007fcc20ba906d in ?? () from /usr/lib/libkdeui.so.5
#9  0x00000000019e49c8 in ?? ()
#10 0x00007fcc20ba907a in ?? () from /usr/lib/libkdeui.so.5
#11 0x00007fff29a97c10 in ?? ()
#12 0x0000000000000000 in ?? ()
#0  0x00007fcc2139f5f0 in nanosleep () from /lib/libc.so.6

Comment 1 Dario Andres 2009-02-10 17:42:58 UTC

What GNU/Linux Distribution do you have?
Do you remember what packages were being updated ?
If you can reproduce the crash at will (or try to), may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)

Comment 2 David Faure 2009-02-18 01:35:05 UTC

Probably the kdirwatch crash.

*** This bug has been marked as a duplicate of bug 165548 ***