Version: 1.6.1 (using KDE 4.6.3) OS: Linux Dolphin is unable to umount/eject a filesystem if the contents of such filesystem are being shown in dolphin. Reproducible: Didn't try Steps to Reproduce: Insert a removable device (example: usb key Select open with dolphin in the notification dialog In dolphin, you are selecting the removable device (ake you are viewing the filesystem contents but no other program is accesing it) right click -> umount the filesystem error: org.freedesktop.UDISK[...]device is busy ok, dolphin does not release the filesystem. click home, and the RIGHT CLICK the previous filesystem to be removed and select umount, it is umounted correctly. Actual Results: to umount X filesystem, one needs to click Y filesystem and right click X filesystem and then umount/remove it. Expected Results: dolphin must release the filesystem which is to be umounted/ejcted prior to try to umount it. kdebase.x86_64 6:4.6.3-1.fc15 @updates kdebase-libs.x86_64 6:4.6.3-1.fc15 @updates kdebase-runtime.x86_64 4.6.3-1.fc15 @updates kdebase-runtime-flags.noarch 4.6.3-1.fc15 @updates kdebase-runtime-libs.x86_64 4.6.3-1.fc15 @updates kdebase-workspace.x86_64 4.6.3-5.fc15 @updates kdebase-workspace-libs.x86_64 4.6.3-5.fc15 @updates
Thanks for the bug report. Do you have the Terminal Panel open in the situation you describe? If that is the case, this is a duplicate of bug 158264.
> Do you have the Terminal Panel open in the situation you describe? > If that is the case, this is a duplicate of bug 158264. Yes, the 'terminal panel' was in some 'form' active. I did not notice it's existence until now, and it was nearly invisible, i saw the word "terminal" at the bottom of the dolphin window but no terminal. After removing it and testing (no problem) i could not manage to put in the same form it was... so maybe in the past it got 'semi-hidden' but now at least i can see a black line so it cannot completely be hidden (is it ok?).
Thanks for the quick reply. It is a duplicate of the other report then. *** This bug has been marked as a duplicate of bug 158264 ***