Version: (using KDE KDE 3.2.0) Installed from: RedHat RPMs OS: Linux Fedora Core 1, KDE 3.2 This is the the same as other bug reports that are listed as resolved. I found that the preloaded instance of Konqueror pointed to the mount point for the device that I am unable to umount. For now, I have set the max. instances preloaded to 0...doesn't take that long to load. Would be nice to have this resolved, though.
Had thought that this problem only occured after navigating to the mount point and then closing Konqueror down, leaving an instance of konqueror running with the mount point appended to the process. Now I found that this problem occurs any time that Konqueror is open, even though I have it pointing to another directory in the file system. Close Konqueror and I can umount the device.
*** Bug 75641 has been marked as a duplicate of this bug. ***
KonqMainWindow::setPreloadedWindow() removes all views, so this is perhaps rather KIO bug.
Read on the Fedora site the Nautilus was having the same problem. Solution...disable sgi-fam. Konqueror works fine now, even with it being preloaded.
Forgot to mark as resolved.
*** Bug 78322 has been marked as a duplicate of this bug. ***
Obviously this bug is not even SOLVED in kde 3.3.2!!!!!!!!! It is still the same old story!!!!! Do something, please!!!! I have to close konqueror several times browse to other dirs, ... until the device is free for umount!!!! konqueror even blocks kde umount via icon context menu. elias
Too right! It most definitely isn't solved. Not only do I have to close all konqueror windows, but I also have to killall konqueror to get control of the dvd eject button back. And even then I sometimes have to umount /dev/dvd and then (re)mount /dev/dvd to get submount working again. I need submount to get fucntionality that mac and windows users take for granted. For something as important as the file manager to louse this up is very VERY bad. For goodness sake! All you have to do is put a warning in kcontrol that if you decide to preload instances of konqueror then you may have problems ejecting disks. Is that really too hard to do?
I have posted a rant about this as bug 101395 (the bug being that the bug handling system is losing touch with reality). Actually I've just noticed that the bug was marked as resolved by the person who originally reported it. Maybe the solution would be not to enable anyone, not even the person who reported it, to close an issue without the consent of a KDE developer.
Bug still exists in kde-3.5.0 under 2.6.14-gentoo-r5
Again, can anyone reopen this bug please, it's a very dull one.
*** Bug 120575 has been marked as a duplicate of this bug. ***
reopened
*** Bug 119055 has been marked as a duplicate of this bug. ***
I'm pretty sure this is a duplicate of bug #78322: "preloaded instances may prevent unmount of filesystems". *** This bug has been marked as a duplicate of 78322 ***