Bug 420713 - Dolphin unmounts external drive after failing to copy from it
Summary: Dolphin unmounts external drive after failing to copy from it
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-28 17:53 UTC by David
Modified: 2020-06-01 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2020-04-28 17:53:29 UTC
SUMMARY
If I try to copy files from an external USB hard disk to an ext4 partition in a laptop through dolphin's copy functionality, it will fail shortly after starting, and will unmount the drive along with it, usually crashing along. Happened on multiple attempts while other file managers succeeded at the first try.

STEPS TO REPRODUCE
1. Connect an external USB hard disk to a laptop.
2. Browse said drive with Dolphin.
3. Copy some files form the external disk to the local disk.

OBSERVED RESULT
Dolphin crashes, the drive is unmounted, and the operation fails.

EXPECTED RESULT
Should copy the files.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
Comment 1 Nate Graham 2020-05-01 13:39:32 UTC
That's odd. What exactly do you mean by "it will fail shortly after starting"? In what way? Also if you can get a backtrace of the crash, that would be helpful. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 David 2020-05-02 09:12:01 UTC
(In reply to Nate Graham from comment #1)
> That's odd. What exactly do you mean by "it will fail shortly after
> starting"? In what way? Also if you can get a backtrace of the crash, that
> would be helpful. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

I mean that it doesn't manage to reach any significant amount of the copy operation. And no, sorry, cannot provide more info, don't have any spare hardware to play with.
Comment 3 Bug Janitor Service 2020-05-17 04:33:11 UTC
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!
Comment 4 Bug Janitor Service 2020-06-01 04:33:12 UTC
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!