[KDE 4] kded crashed

Bug #191804 reported by Alexander Rødseth
6
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
Fix Released
Low
Rich Johnson

Bug Description

I don't know how to reproduce this.
I was running the KDE4 "konsole" and "lastfm" (uses Qt), but the crash happened when I was on another desktop and in another application.

Here's the backtrace:
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb66166c0 (LWP 8438)]
[KCrash handler]
#6 0xb7d619c7 in QString::operator== () from /usr/lib/libQtCore.so.4
#7 0xb7709858 in KDirWatchPrivate::inotifyEventReceived (this=0x810c3e0)
    at /build/buildd/kde4libs-4.0.1/kio/kio/kdirwatch.cpp:291
#8 0xb770a0aa in KDirWatchPrivate::qt_metacall (this=0x810c3e0,
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfc01f3c)
    at /build/buildd/kde4libs-4.0.1/obj-i486-linux-gnu/kio/kdirwatch_p.moc:73
#9 0xb7df1cb4 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb7df2882 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7e0ffc3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb7df7f7f in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6f002ad in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6f03d07 in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb79bd293 in KApplication::notify (this=0xbfc025dc, receiver=0x80fb958,
    event=0xbfc02350)
    at /build/buildd/kde4libs-4.0.1/kdeui/kernel/kapplication.cpp:314
#16 0xb7ddeccb in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb7e03bdc in ?? () from /usr/lib/libQtCore.so.4
#18 0xbfc025dc in ?? ()
#19 0x080fb958 in ?? ()
#20 0xbfc02350 in ?? ()
#21 0xb6c4ec3b in g_thread_join () from /usr/lib/libglib-2.0.so.0
#22 0x00000001 in ?? ()
#23 0xbfc02350 in ?? ()
#24 0x00000000 in ?? ()
#0 0xb7fe3410 in __kernel_vsyscall ()

Tags: kde4
Daniel Hahler (blueyed)
Changed in kde4libs:
importance: Undecided → Medium
Revision history for this message
Rich Johnson (nixternal) wrote :

Has this occurred more than once at all? I will research upstream and other bug sites to see if there was anything similar reported. Thanks!

Changed in kde4libs:
assignee: nobody → nixternal
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Alexander Rødseth (alexanro) wrote :

AFAIK, this has only happened once. I get so many backtraces from KDE 4 that I'm unable to remember them all.

Revision history for this message
Alexander Rødseth (alexanro) wrote :

kded4 crashed again. The only KDE-application I was running was kmix. (kmix/kde4)

I was watching a video in Firefox when suddenly the crash-window appeared, telling me kded4 had crashed.
Seems like it's the same line of code as last time, even though this backtrace is different.

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6647ac0 (LWP 9197)]
[KCrash handler]
#6 0xb7d48997 in QString::operator== () from /usr/lib/libQtCore.so.4
#7 0xb76f0828 in KDirWatchPrivate::inotifyEventReceived (this=0x81012a0)
    at /build/buildd/kde4libs-4.0.2/kio/kio/kdirwatch.cpp:291
#8 0xb76f107a in KDirWatchPrivate::qt_metacall (this=0x81012a0,
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff47dbc)
    at /build/buildd/kde4libs-4.0.2/obj-i486-linux-gnu/kio/kdirwatch_p.moc:73
#9 0xb7dd8cf4 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb7dd98c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7df7003 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb7ddefbf in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6ef32ad in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6ef6d07 in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb79a4513 in KApplication::notify (this=0xbff4845c, receiver=0x810cda0,
    event=0xbff481d0)
    at /build/buildd/kde4libs-4.0.2/kdeui/kernel/kapplication.cpp:314
#16 0xb7dc5bfb in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb7deac1c in ?? () from /usr/lib/libQtCore.so.4
#18 0xbff4845c in ?? ()
#19 0x0810cda0 in ?? ()
#20 0xbff481d0 in ?? ()
#21 0xb6c4190b in g_static_private_get () from /usr/lib/libglib-2.0.so.0
#22 0xb6c19d16 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb6c1d0d3 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x0806ae40 in ?? ()
#25 0x00000000 in ?? ()
#0 0xb7fcd410 in __kernel_vsyscall ()

Changed in kde4libs:
status: Incomplete → New
Revision history for this message
Harald Sitter (apachelogger) wrote :

Looking at the code of kdirwatch.cpp I think the issue got fixed in 4.1.

Please reopen this report if the creash reappears.

Changed in kde4libs:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.