Every time I leave a Konqueror window open with a mount point (of Samba) I can't umount (as user) it without closing the Konqueror window first. Is there a trick to stop Konqueror from locking mount points?

The mount point is considered 'in use' by the kernel at this point. Konq doesn't lock anything, it just runs in the directory you asked it to go to.

It's not the kernel, it's Konqueror. Only when an instance of Konqueror is running I can't umount. I already had to prevent KDE from running a hidden background process of Konqueror to be able to umount Samba shares. This behaviour doesn't happen with Krusader, but I like to use both.

Anyone?

I believe Konquerer keeps its working directory in the directory being viewed, which causes the kernel to keep it locked.

I guess so. Is there a fix?

Define "a fix". This is the intended/designed behavior. I think the only way around it would be major source code changes.

I appreciate your efforts, but we're not talking about the same thing. It doens't happen with Krusader, so it must be a Konqueror thingy. Krusader is a file browser as well. It can't be the kernel.

I honestly don't know if it's intended design but it is most certainly bad design. Very bad design. In Mac OS when you unmount a removable volume all the finder windows that access that volume are automatically closed. Now _that's _ good design.

Moloko, I have the same problem which eventually prompted me to not use KDE any more (gnome had the same problem btw). I noticed though, that whenever a konqueror window was open it was not the konqueror process that locked the device but the fam daemon (file alteration monitor). Maybe there's a way to install konqueror without famd (might not be possible without breaking dependencies, though).
You can check which process is acessing the volume with lsof. If it indeed is famd try uninstalling/disabling that.

I have yet to find a solution for this. Cause fam is a nice idea: It let's gui apps (or any apps for that matter) display changes on the filesystem in real time. If only it worked... At the moment I've got more important things to fix so I'm just waiting for a major fam upgrade to go back to KDE (if at all).

demian > thx, clear answer. I'll look into famd soon and try the lsof tool. Although KDE isn't perfect I like it for the other 99% good parts , but I hardly use KDE apps. It's just the interface for me.

I do work on a Mac occasionally and it rocks Still I prefer Linux and will always have a console running on one of the virtual desktops.

I suppose you could consider it a bad design, but the flipside is this: if I am working on a file and accidentally unmount the wrong volume, I don't want it to close my editor. Same sort of thing applies. I personally like the "you're still using this volume" checking. Also, I believe you can override it with umount -f, though I'll admit I haven't tested that.