https://bugs.kde.org/show_bug.cgi?id=433611
--- Comment #5 from [email protected] ---
(In reply to TraceyC from comment #2)
> (In reply to Jens from comment #0)
>
> This is likely the same as bug 494224. We need a backtrace in order to find
> out for sure.
>
> Can you please attach a backtrace of the crash using the `coredumpctl`
> command-line program, as detailed in
> [https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl](
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl)?
>
> Thanks!
>
>
> (In reply to Jens from comment #1)
> Different crashes might have different causes, even if the symptoms look
> similar. You'll also need to get us a backtrace and we can see.
>
> Thanks again!
I've collected traces using both valgrind and gdb as described in the
Guidelines and Attached them.
To clarify, I did not observe an actual crash, but rather Dolphin becomes
completely unresponsive.
Here’s what I did in the traces:
1. I launched Dolphin and connected to the VPN.
2. I mounted the network shares defined in /etc/fstab.
3. I navigated to the network share folders, then to a local folder.
4. I disconnected the VPN connection, and Dolphin then froze while trying to
navigate to another local folder.
5. I waited a few minutes
6. I killed dolphin
Once the VPN was reconnected, Dolphin became responsive again almost
immediately.
So, the program does not crash, but freezes completely while trying to interact
with local directories after the VPN disconnects.
I hope this helps, and feel free to let me know if you need anything else.
--
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.