The Samba-Bugzilla – Bug 1375
konqueror unresponsive when samba 'device' goes away
Last modified: 2005-02-07 19:14:33 UTC
When a samba mounted MS-windows partition is powered down
or unplugged, Konqueror becomes unresponsive. The window is just white
and tan coloured; nothing in it, and therefore no buttons to press.
I use linneighborhood, or smb4k to mount the windows drives, or
just a script such as:
smbmount //G7/c /mydata/mn/G7/c/ -o username=d7%xx,fmask=644,
I can't unmount the share. I get message: device or resource busy.
root@redd0:/home/dg# umount /mydata/mn/D8/m/
umount: /mydata/mn/D8/m: device is busy
It seems like if it is left alone for a minute sometimes it will
respond later. But, this is not very helpful.
It would be nice of konq was useable except for the item
that has gone away. Any suggestions?
To reproduce this:
I used Mepis 2004.05.b04, Libranet 2.8, and others,
I think most distros will do this.
mount a win drive. open a folder in konq.
On the windows machine unplug the network cable,
or shutdown the Windows PC. now attempt to browse
another folder on the windows PC.
After a few clicks and error messages, it stops
I would expect it to provide an error message stating
that the mount is gone and allow you to keep browsing
This is eierh an smbfs kernel bug or a KDE bug. Not much we can do about it.
(In reply to comment #1)
> This is eierh an smbfs kernel bug or a KDE bug. Not much we can do about it.
What is eierh? Do you mean either?
Should I read this as:
This is either an smbfs, kernel, or KDE bug?