Bug 99138 - No unmounting with konqueror, because device is busy by konqueror itself
Summary: No unmounting with konqueror, because device is busy by konqueror itself
Status: RESOLVED DUPLICATE of bug 97725
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.3.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-11 17:46 UTC by Juergen Katins
Modified: 2005-02-15 22:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Katins 2005-02-11 17:46:15 UTC
Version:           3.3.2 (using KDE KDE 3.3.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I am using Debian Sarge, upgraded feb. 11th 2005. 
I have mounted a windows partition on /windowsC. 
When I open konqueror to try to unmount the device it is not unmounted due to "device is busy". The annoying fact is that the only program using /windowsC is konqueror itself! 
Konqueror trips itself up!
When I try to unmount with konsole (s:/# umount windowsC) I get 
"umount: /windowsC: device is busy
umount: /windowsC: device is busy"
(Yes there are two lines)

When I close konqueror and unmount by konsole it works. 

Expected behavior: 
Konqueror should be able to unmount devices, when no other program is using them.
Comment 1 Martin Koller 2005-02-15 22:33:14 UTC

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