Bug 180955

Summary:	fatal error after kubuntu updates installation
Product:	[Unmaintained] kdelibs	Reporter:	Alessandro <alebar72>
Component:	kded	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alessandro 2009-01-16 12:05:35 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

This is the kded4.kcrash - kate:

Applicazione: Demone KDE (kded4), segnale 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 0x7f4e100a86f0 (LWP 5119)]
(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)
0x00007f4e0f9d45f0 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 5119)]

Thread 1 (Thread 0x7f4e100a86f0 (LWP 5119)):
#0  0x00007f4e0f9d45f0 in nanosleep () from /lib/libc.so.6
#1  0x00007f4e0f9d4447 in sleep () from /lib/libc.so.6
#2  0x00007f4e0f0f155f in ?? () from /usr/lib/libkdeui.so.5
#3  0x00007f4e0f0f1e9a in KCrash::setApplicationName ()
   from /usr/lib/libkdeui.so.5
#4  0x00007f4e0f1de052 in ?? () from /usr/lib/libkdeui.so.5
#5  0x00000000017f5b68 in ?? ()
#6  0x00007f4e0f1de05f in ?? () from /usr/lib/libkdeui.so.5
#7  0x00000000018086e8 in ?? ()
#8  0x00007f4e0f1de06d in ?? () from /usr/lib/libkdeui.so.5
#9  0x00000000017f59c8 in ?? ()
#10 0x00007f4e0f1de07a in ?? () from /usr/lib/libkdeui.so.5
#11 0x00007fff180ca2f0 in ?? ()
#12 0x0000000000000000 in ?? ()
#0  0x00007f4e0f9d45f0 in nanosleep () from /lib/libc.so.6

Comment 1 Dario Andres 2009-01-16 12:55:33 UTC

This may be related to bug 165548

Comment 2 David Faure 2009-01-16 13:49:03 UTC

The bug description sounds like 165548 indeed.
The backtrace says nothing.

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