Bug 174963

Summary:	KDE Daemon - A Fatal Error Occurred
Product:	[Unmaintained] kdelibs	Reporter:	john3909 <jsynesio>
Component:	kded	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	christophe, finex, frank78ac
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description john3909 2008-11-12 17:58:30 UTC

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

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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb620c8d0 (LWP 20245)]
(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)
[KCrash handler]
#6  0xb752d2a4 in QString::operator== () from /usr/lib/libQtCore.so.4
#7  0xb7d519ed in ?? () from /usr/lib/libkio.so.5
#8  0xb7d51c9b in ?? () from /usr/lib/libkio.so.5
#9  0xb75f0a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb75f17e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb762b633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb75f6637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6b6e8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6b7676e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7aaa72d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb75dbe61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb760670a in ?? () from /usr/lib/libQtCore.so.4
#18 0xb659d6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb65a0da3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb65a0f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb7606478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0xb6c08ee5 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb75da52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb75da6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb75dcda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb6b6e767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0xb802d0a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#28 0x080485a2 in _start ()
#0  0xb8069430 in __kernel_vsyscall ()

Comment 1 FiNeX 2008-11-12 18:08:06 UTC

Hi! Could you explain how to reproduce the crash?

Moreover you should read this page for the instructions about posting an useful backtrace:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!

Comment 2 Frank Reininghaus 2008-11-12 19:52:06 UTC

Looks very much like a duplicate of bug 165548 which occurs during updates.

Comment 3 FiNeX 2008-11-12 20:22:57 UTC

The backtrace if very similar...

Comment 4 john3909 2008-11-12 20:47:22 UTC

Yes, I agree, my bug report is the same as bug 165548.

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