Bug 377269 - dolphin hangs after opening a file
Summary: dolphin hangs after opening a file
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-06 07:08 UTC by Ingo Ebel
Modified: 2017-07-26 08:03 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 Ingo Ebel 2017-03-06 07:08:51 UTC
After fresh starting my plasma desktop the last dolphin sessions are started. 
In one of this dolphins I can klick on a file and it opens. after that this dolphin session is useles. I can't open anything else nor change directories.

A newly open dolphin is behaving corretly. just the ones started with plasma at login are the problem.

Steps to Reproduce:
1. Login to Plasma
2. Klick on a file (e.g. text, pdf or else)
3. Close the file
4. dolphin hangs and nothing is clickable

Version: dolphin 16.12.2-1
Comment 1 Elvis Angelaccio 2017-03-06 17:19:42 UTC
Hi, we need a backtrace to investigate where the freeze happens. You can try the following:

1. gdb -p `pidof dolphin` (You probably need to be root, also make sure that only one dolphin instance is running)
2. Press CTRL+C
3. Type 'bt'

Finally attach here the backtrace that gdb printed.
Comment 2 Ingo Ebel 2017-03-09 09:45:15 UTC
Strange.
The moment i start the degugger. Dolphin is not usable anymore. I tried it 2 times. So can't klick on anything. And the output not helping:

Attaching to process 7633
[New LWP 7635]
[New LWP 7641]
[New LWP 7712]
[New LWP 7713]
[New LWP 7714]
[New LWP 7715]
[New LWP 7716]
[New LWP 7754]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f3d22d3b48d in poll () from /usr/lib/libc.so.6
(gdb) 

Any suggestions?
Comment 3 Elvis Angelaccio 2017-03-09 10:18:05 UTC
@Ingo that's fine, just press CTRL+C from gdb and then type 'bt'
Comment 4 Ingo Ebel 2017-03-09 10:19:53 UTC
Ok.
Thats still not much output :(


(gdb) Quit
(gdb) bt
#0  0x00007f3d22d3b48d in poll () from /usr/lib/libc.so.6
#1  0x00007f3d15c987a6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f3d15c988bc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f3d1ceec04f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007f3d1ce9589a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007f3d1ce9dde4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007f3d23058177 in kdemain () from /usr/lib/libkdeinit5_dolphin.so
#7  0x00007f3d22c7c291 in __libc_start_main () from /usr/lib/libc.so.6
#8  0x000000000040065a in _start ()
Comment 5 Ingo Ebel 2017-07-26 08:03:57 UTC
With the last KDE Frameworks Release the bug is gone.