| Summary: | dolphin crashing when trying to copy several GB from an external SSD | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | severin.kunz |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kfm-devel, mail |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
severin.kunz
2020-04-16 09:24:45 UTC
Hello Severin, sorry for the delay in responding to your bug report. Could you give us some more detail? Can you reproduce this crash if you copy the files again? If yes, we'd need a backtrace with debug symbols to be able to debug this problem. Thank you :) (In reply to Julian Schraner from comment #1) > backtrace with debug symbols How can I do that? When Dolphin crashes, you should usually see a dialog opening up shortly after that asks you whether you want to generate a backtrace. You'll then want to copy this backtrace and paste/upload it here. To get a complete backtrace, you will want to install kio-dbgsym and dolphin-dbgsym first. 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! Please ask for help in a forum of your distribution how to install debug symbols. Some generic information is available at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports 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! |