Bug 175761 - KDE daemon error report
Summary: KDE daemon error report
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: needs_verification
: 176052 176189 176258 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-21 14:31 UTC by mahendra
Modified: 2008-12-19 14:14 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mahendra 2008-11-21 14:31:48 UTC
Version:            (using KDE 4.1.0)
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 0xb61fd8d0 (LWP 5285)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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  0xb751e2a4 in QString::operator== () from /usr/lib/libQtCore.so.4
#7  0xb7d429ed in ?? () from /usr/lib/libkio.so.5
#8  0xb7d42c9b in ?? () from /usr/lib/libkio.so.5
#9  0xb75e1a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb75e27e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb761c633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb75e7637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6b5f8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6b6776e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7a9b72d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb75cce61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb75f770a in ?? () from /usr/lib/libQtCore.so.4
#18 0xb658e6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb6591da3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb6591f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb75f7478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0xb6bf9ee5 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb75cb52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb75cb6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb75cdda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb6b5f767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0xb801e0a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#28 0x080485a2 in _start ()
#0  0xb804f430 in __kernel_vsyscall ()
Comment 1 mahendra 2008-11-21 14:32:32 UTC
I have pasted the carsh report as it is
Comment 2 FiNeX 2008-11-24 23:02:43 UTC
Can you explain if and how the bug is reproducible? What did you do for having this crash?

If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 3 Lorenzo 2008-11-25 13:09:56 UTC
Same bug.
Happened 3 times, always when running tasks related with kpackage-update.
The backtrace was void or poor, too poor to found usable infos... nothing too in logs... :-( sorry.
Still keep an eye on that, will try to get more verbosity in some way and will say back something.
Ciao.
Comment 4 FiNeX 2008-11-25 14:43:20 UTC
@Lorenzo: if you want, you can follow this guide in order to have more detailed backtrace.

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 5 Jordi Polo 2008-11-25 17:45:44 UTC
*** Bug 176052 has been marked as a duplicate of this bug. ***
Comment 6 Jordi Polo 2008-11-25 17:46:36 UTC
I have taken a look to downstream (launchpad), they don't have any bug about this.
Comment 7 Jordi Polo 2008-11-27 07:47:31 UTC
*** Bug 176189 has been marked as a duplicate of this bug. ***
Comment 8 Jordi Polo 2008-11-28 05:03:26 UTC
*** Bug 176258 has been marked as a duplicate of this bug. ***
Comment 9 Dario Andres 2008-12-19 14:14:34 UTC

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