Closing Dolphin doesn't kill the corresponding dolphin process (I can see it using "pgrep dolphin"). Since a new dolphin process is created every time I run Dolphin, running and closing Dolphin a few times will yield a bunch of dolphin processes that, apparently, will live until you manually kill them. Reproducible: Always Steps to Reproduce: 1. Launch Dolphin 2. Close Dolphin 3. Look for the dolphin process with pgrep Actual Results: A dolphin process is still running after closing Dolphin. Expected Results: No Dolphin process should be running. I think it's related with the settings...I tried deleting dolphinrc and also the dolphin directory under .kde4/share/apps/dolphin to get a Dolphin "fresh install" and it doesn't happen. Then I changed a few settings (e.g., no expandable folders in the detailed view) and it started to happen.
Thanks for the report, but I cannot reproduce. To find out where in the code it hangs, please run Dolphin in gdb: 1. In a terminal, enter 'gdb dolphin'. 2. At the gdb prompt, enter 'run'. 3. Close Dolphin (such that the process hangs according to your report). 4. Switch to the terminal, press Ctrl+Z. 5. At the gdb prompt, enter 'thread apply all backtrace'. Paste or attach the backtrace here. Thanks for your help.
Created attachment 78596 [details] Backtrace requested
Hi, and thanks for your fast reply. Another thing I just noticed: if I run Dolphin from the console, the command prompt never returns after closing Dolphin. I guess it's just natural according to what I reported earlier...but just in case. Cheers
Thanks for the quick reply. Pasting the backtrace below. Looks like it's still running the event loop normally. If you really did close Dolphin before you obtained this backtrace, I don't have any idea what the reason for this bug might be. Thread 3 (Thread 0x7fffdd41f700 (LWP 6165)): #0 0x00007ffff786dc63 in select () from /lib64/libc.so.6 #1 0x00007ffff35b9a8f in QProcessManager::run() () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007ffff34db1bc in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007ffff1b3cd96 in start_thread () from /lib64/libpthread.so.0 #4 0x00007ffff787442d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fffdf0f3700 (LWP 6163)): #0 0x00007ffff786b663 in poll () from /lib64/libc.so.6 #1 0x00007fffef3046e6 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fffef304804 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffff360af96 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007ffff35da942 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007ffff35dab97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007ffff34d8157 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff35ba41f in QInotifyFileSystemWatcherEngine::run() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007ffff34db1bc in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007ffff1b3cd96 in start_thread () from /lib64/libpthread.so.0 #10 0x00007ffff787442d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffff7f9b7c0 (LWP 6154)): #0 0x00007ffff786b663 in poll () from /lib64/libc.so.6 #1 0x00007fffef3046e6 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fffef304804 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffff360af2f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007ffff40a864e in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtGui.so.4 #5 0x00007ffff35da942 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007ffff35dab97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff35df9b5 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007ffff7b86bb7 in kdemain () from /usr/lib64/libkdeinit4_dolphin.so #9 0x00007ffff77ab4bd in __libc_start_main () from /lib64/libc.so.6 #10 0x0000000000400791 in _start ()
Reopening the report (even though I don't know what we can do about this issue).
Would it be possible that Dolphin is still running but not visible (in which case, it's probably not a Dolphin thing and the issue is caused by some other component)? It's just a wild guess since I don't really know about the internals of KDE... Just let me know I can do anything else to help...
(In reply to comment #6) > Would it be possible that Dolphin is still running but not visible It looks like that is the case, yes. > Just let me know I can do anything else to help... I'm afraid I don't know anything else you could do to help, but maybe someone else has an idea.
Can you still reproduce the problem with Dolphin 4.11.0 or later?
I'm still using Dolphin 4.10.5 (stable Gentoo) and I cannot reproduce it, so I'm guessing another KDE component was to blame...
Thanks for the feedback. If you see the problem again in Dolphin 4.11 or later, please let us know. Thanks for your help!
Thank you for the good work!! :) Sure, if it happens again when I update, I will report it. Cheers.