On Tuesday 02 December 2003 17:09, Peter N. Spotts wrote:
Allen,
You've gotten a couple of high-tech answers...let me try a lower-tech approach. And pardon me if you've already considered the following...
Or another low tech approach. KDE has a setting to help speed up Konq. It loads at least one instance of Konq in the background, and holds it there so that when you do make a call to Konq it appears quicker... or so the theory goes. You'll find this setting buried in the KDE Control Centre. I've found that if you set this to zero, the problem you've described goes away. My theory is that somehow the mount to floppy or CDROM gets attached to this phantom preloaded background instance of Konq. When you try to unmount the device, you can't because when umount checks the device it sees that Konq is still connected to the device. When it sees this it bounces back the "Cannot unmount device. Device busy" message. C.
I've experienced the same problem on several distros -- Mandrake, Red Hat, and SuSE 9.0. In my case, it happens because:
a. I'm transferring large files or large numbers of files and the directory from which I'm transferring shows empty, while they appear in on the outboard drive. So I try to unmount, forgetting that the files may not have fully crossed to the outboard drive yet.
or
b. I have a minimized terminal window, file manager, or app that is set to the drive I'm trying to unmount, and I've either momentarily forgotten to shut the program down or >cd .. back up to a higher level directory.
Thus, when I get those kinds of unmount messages, those are the first two things I check.
Best,