Version: (using KDE KDE 3.1) Installed from: SuSE RPMs OS: Linux First i mount a CD in a CD-ROM. That CD has a tar.gz file on it. I browse with konqueror in /media/cdrom and i click this file. After clicking this tar.gz file the embedded viewer appears. Everything is fine here. Then i press BACK from the konqueror toolbar to exit the viewer. I move around to my CD just to see what it has in it. Finally i try to Unmount or Eject the CD. A dialog reports that this device is busy... I do a 'ps -xa' on my Konsole and i see a process kdeinit: kio_tar tar .... ..... Only when i kill it i am able to unmount the CD.
I have this same probelm with 3.1.2 built from source. It happens with both kio_tar and kio_zip that I've seen and is a bit annoying. I guess the slaves are kept around for a certain time for reuse but they won't release the mounted filesystem until killed. I wouldn't say that this is a konqueror bug though.
*** Bug 54861 has been marked as a duplicate of this bug. ***
Idle kioslaves are killed by klauncher after 30 seconds of inactivity. But before that, the application only gives up an idle kioslave after 3 minutes. So if I list a kio_tar dir and immediately go to $HOME, I'll need 3 minutes 30 seconds before kio_tar gets killed. Since we don't want to reparse the tar file on every action, killing such slaves early (or changing the slave so it forgets about the file early), is no solution. Better would be to implement the "I'm about to unmount this dir, please forget about it if you can" solution, based on DCOP's findObject, as I discussed with Waldo some time ago (for #37780, but it turned out it wasn't necessary there). BUT.... slaves don't listen to DCOP. So the KIO scheduler, which is the only one that knows about slaves during the 3 minutes after the listDir, would have to do this?
Another option is to close and re-open the QIODevice used by KArchive in kio_tar. ArchiveProtocol::checkNewFile() already checks if the file is changed.
*** Bug 77453 has been marked as a duplicate of this bug. ***
Can this be still triggered? If yes, how? (There is code in the tar/zip KIO slave to "unload" the KIO slave.) Have a nice day!
Just tested here using: Qt: 4.5.2 (KDE-Qt git commit 46a247a2c9a8c0c4456a02f6a0922d859d88fe76 Date: Fri Jun 26 13:45:37 2009 +0200) KDE: 4.3.61 (KDE 4.3.61 (KDE 4.4 >= 20090717)) kdelibs svn rev. 999250 / kdebase svn rev. 999250 on ArchLinux i686 - Kernel 2.6.30.1 - Mounted a Usb drive - Copied a small tar.gz on it - Browsed to that tar.gz file (using "browse through archives" option in Dolphin) - Went back to the USB root (using "Back" button at Dolphin) - Tried to unmount the USB drive. The drive was unmounted properly without warning messages. There are no kio_tar process (only kio_archive ones). I guess a lot of code has changed Can anyone else check this ? Thanks
Not confirmed on KDE 4, closing. Please reopen if you can still experience this bug with KDE 4.5 or later.