Version: (using KDE KDE 3.4.2) Installed from: Slackware Packages OS: Linux While attempting to write an 'autounmount' daemon for K, I needed to look at the /proc/{PID}/fd of random applications. I noticed that if you leave a directory in the file manager view of Konqy, it holds onto the file descriptor for that directory. This has caused me problems in the past, I realize - A Konqy window that, historically, had ventured into a removable disc will almost always need to be closed to unmount the drive. Quick test: go to a console and run 'konqueror &' Grab the PID bash returns and go to /proc/{PID}/fd. Now open a directory. Do an ls -l and you'll see the directory as a file descriptor link. Rinse and repeat, and you'll see both folders, not just the current one.
The only file handles opened are sockets, pipes and cache in trunk and 3.5.9
Works for me in svn trunk r807691 (20080507)
@Jaime: this is not true if you have preloaded istances of konqueror. In some cases you will not be able to umount. (tested on 3.5.9)
This behaviour should be well checked on KDE 4.
In fedora 9 (kde 4.0.3) with a preloaded konqueror, using lsof | grep kon I see the following files in use: cwd DIR /home/user rtd DIR / mem REG (a lot of libs in /lib and /usr/lib) mem REG /usr/share/fonts/* mem REG /var/cache/fontconfig/* 1w REG /home/user/.xession-errors 2w REG /home/user/.xession-errors 12u REG /var/tmp/kdecache-user/* 14u REG /tmp/kde-user/* pipes and unix sockets (Where are the unix sockets created? in /tmp?)
I can't reproduce the bug either on trunk r810280.
This bug is no more valid with KDE 4.4