Bug 180652 - sigsegv (with backtrace with symbols), circumstances unknown
Summary: sigsegv (with backtrace with symbols), circumstances unknown
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 13:05 UTC by Brian Foster
Modified: 2009-01-14 13:36 UTC (History)
0 users

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 Brian Foster 2009-01-14 13:05:13 UTC
Version:           Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) KDE Daemon: $Id: kded.cpp 825113 2008-06-27 13:30:46Z dfaure $  (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

kded4 (KDE 4.1.3) on Kubuntu 8.10 (fully up-to-date) sigsegv'd.
at the time several different things were happening, including
(but possibly not limited to), installing packages (openoffice
from the Kubuntu repositories using Adept), IRC (Konversation),
Kmail, and several Konsole shells (all idling?).

the stack backtrace (which I *just* noticed looks similar to
several other kded4 defect reports — sorry!  I thought it was
different ....  ;-\ ):

Application: KDE Daemon (kded4), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe96e7746f0 (LWP 20335)]
[KCrash handler]
#5  0x00007fe96dc73c78 in QString::operator== () from /usr/lib/libQtCore.so.4
#6  0x00007fe96cde6d33 in KDirWatchPrivate::inotifyEventReceived (
    this=0x79cbb0) at /build/buildd/kde4libs-4.1.3/kio/kio/kdirwatch.cpp:288
#7  0x00007fe96cdea848 in KDirWatchPrivate::qt_metacall (this=0x79cbb0, 
    _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, 
    _a=0x7fff767a83c0)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/kdirwatch_p.moc:74
#8  0x00007fe96dd32134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#9  0x00007fe96dd687de in QSocketNotifier::activated ()
   from /usr/lib/libQtCore.so.4
#10 0x00007fe96dd37c43 in QSocketNotifier::event ()
   from /usr/lib/libQtCore.so.4
#11 0x00007fe96bdb6c3d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#12 0x00007fe96bdbe9ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#13 0x00007fe96d399fcb in KApplication::notify (this=0x7fff767a8cc0, 
    receiver=0x79ca70, event=0x7fff767a8990)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#14 0x00007fe96dd1dd61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#15 0x00007fe96dd463d9 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007fe96b02dd3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#17 0x00007fe96b03150d in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007fe96b0316cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#19 0x00007fe96dd4615f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#20 0x00007fe96be48a6f in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007fe96dd1c682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0x00007fe96dd1c80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0x00007fe96dd1ecbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#24 0x00007fe96e384fd2 in kdemain (argc=1, argv=0x7fff767a91c8)
    at /build/buildd/kde4libs-4.1.3/kded/kded.cpp:847
#25 0x00007fe96e025466 in __libc_start_main () from /lib/libc.so.6
#26 0x0000000000400659 in _start ()
#0  0x00007fe96e0af5f0 in __nanosleep_nocancel () from /lib/libc.so.6
Comment 1 David Faure 2009-01-14 13:36:42 UTC
Yep, this is 165548.

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