Bug 174598

Summary:	Application: KDE Daemon (kded4), signal SIGSEGV
Product:	[Unmaintained] kdelibs	Reporter:	paul <sp8sangel>
Component:	kded	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	finex, frank78ac, mboquien
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description paul 2008-11-08 07:50:04 UTC

Version:            (using KDE 4.1.2)
Installed from:    Debian stable 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 0xb61226c0 (LWP 1841)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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  0xb74442a4 in QString::operator== () from /usr/lib/libQtCore.so.4
#7  0xb7c689ed in ?? () from /usr/lib/libkio.so.5
#8  0xb7c68c9b in ?? () from /usr/lib/libkio.so.5
#9  0xb7507a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb75087e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7542633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb750d637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6a858ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6a8d76e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb79c172d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb74f2e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb751d70a in ?? () from /usr/lib/libQtCore.so.4
#18 0xb64b46f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb64b7da3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb64b7f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb751d478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0xb6b1fee5 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb74f152a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb74f16ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb74f3da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb6a85767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0xb7f430a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#28 0x080485a2 in _start ()
#0  0xb7f76430 in __kernel_vsyscall ()

Comment 1 FiNeX 2008-11-08 10:35:46 UTC

Hi Paul, you should explain better your crash, what did you doing and what can be do in order to reproduce the crash.

Moreover this type of backtrace is unuseful, you should follow the instructions on this site for learn how to provide 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:57:07 UTC

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

Comment 3 FiNeX 2008-11-19 11:16:44 UTC


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