Bug 200806 - Can't unmount removable storage device opened in dolphin while the terminal panel is opened
Summary: Can't unmount removable storage device opened in dolphin while the terminal p...
Status: RESOLVED DUPLICATE of bug 158264
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-19 22:36 UTC by Mehdi Salem
Modified: 2009-07-19 22:38 UTC (History)
1 user (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 Mehdi Salem 2009-07-19 22:36:07 UTC
Version:           1.2.1 (using KDE 4.2.4)
Compiler:          gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2 
OS:                Linux
Installed from:    Gentoo Packages

When you open a device via dolphin and you have configured dolphin to also show a terminal, the terminal automatically switches to the opened mount directory. The problem is that the device cannot be unmounted then since the device is busy hosting the shell. Another problem which is even worse is that by hiding the terminal and switching to another directory the terminal stays in the directory and does not follow the dolphin directory. In this case you can have nagivated out of the directory from within dolphin but the hidden terminal stays there and thus avoids the device from unmounting.

Upon unhiding the terminal it switches to the current directory and so makes unmounting the device possible again. This is a usability issue. The terminal should somehow be informed that one wants to unmount the device and switch to another directory automatically. If that is not viable/possible it should at least be programmed to follow the dolhin window actively even if hidden.

Thanks in advance
momesana
Comment 1 Dario Andres 2009-07-19 22:38:29 UTC
Marking as duplicate of bug 158264. Thanks

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