Bug 328448 - "Safely removing" mass-storage devices doesn't work
Summary: "Safely removing" mass-storage devices doesn't work
Status: RESOLVED DUPLICATE of bug 158264
Alias: None
Product: dolphin
Classification: Applications
Component: panels: places (show other bugs)
Version: 4.11.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-05 12:11 UTC by Hans Überacher
Modified: 2013-12-05 13:09 UTC (History)
0 users

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 Hans Überacher 2013-12-05 12:11:19 UTC
I guess this isn't a bug in the technical sense, but it must seem like one for novice users. So it's more of a usability issue, but a serious and quite frustrating one for some people.

If you click "safely remove" on a device in dolphin, while having that same device open in dolphin, it won't work. It says "This device is currently busy". I remember I was quite puzzled by this years ago, until I figured out that, of course, dolphin itself was the one keeping the device busy.

It would be great if dolphin could just throw back to the home directory (or close a split screen) after being told to "safely remove" a device that is currently being viewed -- and only then try to unmount the device.

Reproducible: Always

Steps to Reproduce:
1. Insert USB stick or something
2. Open it in dolphin
3. Hit "safely remove" on the device entry in the panel
Actual Results:  
"This device is currently busy"

Expected Results:  
Dolphin should just close the view for the device and then unmount.
Comment 1 Frank Reininghaus 2013-12-05 12:39:54 UTC
Thanks for the bug report, but I cannot reproduce the problem.

Is the Terminal Panel being used?
Comment 2 Hans Überacher 2013-12-05 13:08:21 UTC
Ah... so THAT's what's really keeping the device busy then. Thanks, you can close the report. I don't suppose too many novices will be using the terminal panel.
Comment 3 Frank Reininghaus 2013-12-05 13:09:16 UTC

*** This bug has been marked as a duplicate of bug 158264 ***