Summary: | Dolphin freezes at startup or during directory navigation | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Justin T. Frisch <bugs> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | grave | CC: | anton.latukha+reg, anton.latukha, hotmusicfan, justin.zobel, mail |
Priority: | NOR | ||
Version: | 15.12.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Hand of Dolphin |
Description
Justin T. Frisch
2016-01-04 12:50:33 UTC
It occurs on my system too. At every startup, on the first opening of Dolphin. openSUSE Leap 42.1/KDE Plasma 5.5.5 This issue is still existing in Plasma 5.8.3, probably 5.8.4 too! Tested on openSUSE Leap 42.2. The same issue. I have NFS share. When it was accessed long time - Dolphin staggers. And when NFS share not respond - Dolphin hangs. Here is the screenshot: Created attachment 107864 [details]
Hand of Dolphin
Sorry for typos. I'm sleepy. Arch Linux. 2017-09-15. dolphin 17.08.1-1 KDE Plasma desktop 5.10.5-1 Hello, and thanks for reporting this bug! First, please try to reproduce the crash again with the newest version possible (Arch should have 18.04.2). The current backtrace is sadly incomplete, so please install the debug packages needed and upload a new backtrace if you can still reproduce the issue. Thanks again! (In reply to Julian Schraner from comment #6) > Hello, and thanks for reporting this bug! First, please try to reproduce the > crash again with the newest version possible (Arch should have 18.04.2). The > current backtrace is sadly incomplete, so please install the debug packages > needed and upload a new backtrace if you can still reproduce the issue. > Thanks again! Hello. This hanging for a while in Dolphin is still existing. (Plasma 5.12 LTS, 17.12.3, openSUSE Leap 15). Okay, thanks for the confirmation. It'd be great if we could get a full backtrace. Simply install dolphin-debuginfo & generate a new backtrace, then attach it here. Thanks! Can you please provide a backtrace on the most current version in each of your respective distros. I've not had any crashes at all with Dolphin 20.08.1 so cannot reproduce. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Good that KDE started to close bugs automatically on the certain rules - it is definitely the right practice. For such a severe syndrome bug - 4 people involved - means it is a small rare thing. Especially when I bailed-out I know that NFS/SAMBA handling I wrote here because of - was solved. At least for me Dolphin hung because it synchronously engaged into NFS/SAMBA and waited for downtime, while share was simply offline, I imagine the same is on slow/dodgy connection. But I know that was radically improved in last couple of years, and hanging problem went away for me. IDK if the original bug report relates to network devices - but it was my case which is solved - so I bail-out of the report. Hope you all doing great. I think the bug resolved itself. Or it may be the people have some dodgy `dolphinrc` config file to reset, or some hardware issues, or problem in the other part of the system. Thank you. |