| Summary: | dolphin crashed (supposedly) when displaying folder in which files were created (and deleted?) by a script | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Oliver Putz <Regnaron> |
| Component: | general | Assignee: | Peter Penz <peter.penz19> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra |
| Priority: | NOR | ||
| Version: | 16.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Another of the weird crashes related to bug 208921. - Does Dolphin crash again if you repeat the same steps you described ? - Is Nepomuk enabled ? Thanks *** This bug has been marked as a duplicate of bug 208921 *** Hi! No, the crash was not reproducibly. I tried to repeat what I did after the crash but dolphin did not crash again. And yes, as said, Nepomuk was running and actually heavily working in the background to catch up with the changes in the folders that had files deleted and created by my script. |
Application that crashed: dolphin Version of the application: 1.3 KDE Version: 4.3.3 (KDE 4.3.3) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r4 x86_64 What I was doing when the application crashed: I used Dolphin to delete all files in a certain folder which was being displayed in dolphin. After that I started a script which created (and possibly removed) files in that folder. Midway though the script (supposedly when it modified the displayed folder) Dolphin crashed. Not sure if its of any interest, but nepomukservicesstub was also working pretty hard to catch up with the files in that folder having been deleted and recreated by the script. (the folder is being monitored by nepomuk) -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [Current thread is 0 (LWP 8333)] Thread 2 (Thread 0x7f20cad23950 (LWP 23543)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217 #1 0x00007f20c88e5fbe in metronom_sync_loop (this=0x18cca00) at metronom.c:870 #2 0x00007f20d5a83017 in start_thread (arg=<value optimized out>) at pthread_create.c:297 #3 0x00007f20d458448d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f20d9189750 (LWP 8333)): [KCrash Handler] #5 _dbus_connection_lock (connection=0x74005f006f0063) at dbus-connection.c:355 #6 0x00007f20cfea6c0d in _dbus_pending_call_get_connection_and_lock (pending=0x1e9a2c0) at dbus-pending-call.c:309 #7 0x00007f20cfe99cef in reply_handler_timeout (data=0x74005f006f0063) at dbus-connection.c:3116 #8 0x00007f20d60b47f6 in QDBusConnectionPrivate::timerEvent (this=0x9b3350, e=0x7fff8eaebaa0) at ./qdbus_symbols_p.h:172 #9 0x00007f20d5dd4153 in QObject::event (this=0x9b3350, e=0x22) at kernel/qobject.cpp:1066 #10 0x00007f20d514c8fd in QApplicationPrivate::notify_helper (this=0x9c7200, receiver=0x9b3350, e=0x7fff8eaebaa0) at kernel/qapplication.cpp:4065 #11 0x00007f20d51541ba in QApplication::notify (this=0x7fff8eaebde0, receiver=0x9b3350, e=0x7fff8eaebaa0) at kernel/qapplication.cpp:4030 #12 0x00007f20d6be1f8b in KApplication::notify (this=0x7fff8eaebde0, receiver=0x9b3350, event=0x7fff8eaebaa0) at /tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302 #13 0x00007f20d5dc5a5b in QCoreApplication::notifyInternal (this=0x7fff8eaebde0, receiver=0x9b3350, event=0x7fff8eaebaa0) at kernel/qcoreapplication.cpp:606 #14 0x00007f20d5ded656 in QTimerInfoList::activateTimers (this=0x9c2180) at kernel/qcoreapplication.h:213 #15 0x00007f20d5dea4fd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #16 0x00007f20d1881ce0 in IA__g_main_context_dispatch (context=0x9c1120) at gmain.c:1824 #17 0x00007f20d1885408 in g_main_context_iterate (context=0x9c1120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2455 #18 0x00007f20d18855cc in IA__g_main_context_iteration (context=0x9c1120, may_block=1) at gmain.c:2518 #19 0x00007f20d5dea45f in QEventDispatcherGlib::processEvents (this=0x999790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #20 0x00007f20d51d189f in QGuiEventDispatcherGlib::processEvents (this=0x74005f006f0063, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #21 0x00007f20d5dc4442 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1901150960}) at kernel/qeventloop.cpp:149 #22 0x00007f20d5dc45dc in QEventLoop::exec (this=0x7fff8eaebd50, flags={i = -1901150880}) at kernel/qeventloop.cpp:197 #23 0x00007f20d5dc661c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #24 0x0000000000439b0d in main (argc=5, argv=0x7fff8eaec2c8) at /tmp/portage/kde-base/dolphin-4.3.3/work/dolphin-4.3.3/dolphin/src/main.cpp:94 Reported using DrKonqi