Bug 227250 - dolphin crashed on quit, probably kdirwatch related
Summary: dolphin crashed on quit, probably kdirwatch related
Status: RESOLVED DUPLICATE of bug 226788
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 20:05 UTC by S. Burmeister
Modified: 2010-02-16 21:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2010-02-16 20:05:07 UTC
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

Dolphin crashed after I closed it via the close-button in the title-bar.


Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  detach (this=<value optimized out>) at /usr/include/QtCore/qlist.h:122
#6  begin (this=<value optimized out>) at /usr/include/QtCore/qlist.h:248
#7  KDirWatchPrivate::Entry::removeClient (this=<value optimized out>) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:456
#8  0x00007f17f8034007 in KDirWatchPrivate::removeEntry (this=0x940760, instance=0x0, e=0x0, sub_entry=0x0) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:890
#9  0x00007f17f80343ae in KDirWatchPrivate::slotRemoveDelayed (this=0x940760) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1313
#10 0x00007f17f804ff3c in KDirWatchPrivate::qt_metacall (this=0x940760, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1e9b9df0) at /usr/src/debug/kdelibs-4.4.0/build/kio/kdirwatch_p.moc:84
#11 0x00007f17f6e11bff in QMetaObject::activate (sender=0xd35d00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3275
#12 0x00007f17f6e1935f in QSingleShotTimer::timerEvent (this=0xd35d00) at kernel/qtimer.cpp:308
#13 0x00007f17f6e0e853 in QObject::event (this=0xd35d00, e=0x7fff1e9ba590) at kernel/qobject.cpp:1212
#14 0x00007f17f61bdc9c in QApplicationPrivate::notify_helper (this=0x6d28d0, receiver=0xd35d00, e=0x7fff1e9ba590) at kernel/qapplication.cpp:4298
#15 0x00007f17f61c427b in QApplication::notify (this=0x7fff1e9ba990, receiver=0xd35d00, e=0x7fff1e9ba590) at kernel/qapplication.cpp:4181
#16 0x00007f17f79d3456 in KApplication::notify (this=0x7fff1e9ba990, receiver=0xd35d00, event=0x7fff1e9ba590) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302
#17 0x00007f17f6dfedfc in QCoreApplication::notifyInternal (this=0x7fff1e9ba990, receiver=0xd35d00, event=0x7fff1e9ba590) at kernel/qcoreapplication.cpp:704
#18 0x00007f17f6e2bac5 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#20 0x00007f17f6e28634 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f17f148adee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f17f148e7b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f17f148e8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f17f6e28323 in QEventDispatcherGlib::processEvents (this=0x6a4e80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f17f626bdce in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f17f6dfd712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f17f6dfdaec in QEventLoop::exec (this=0x7fff1e9ba8e0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f17f6e0183b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#29 0x000000000043acb5 in _start ()
Comment 1 Dario Andres 2010-02-16 21:58:35 UTC
This should be fixed in KDE SC 4.4.1: bug 226788.
Regards

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