Bug 1375 - konqueror unresponsive when samba 'device' goes away
konqueror unresponsive when samba 'device' goes away
Status: RESOLVED INVALID
Product: Samba 3.0
Classification: Unclassified
Component: smbmount (unmaintained)
3.0.2a
All Linux
: P1 normal
: none
Assigned To: Samba Bugzilla Account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-21 20:41 UTC by david gleba
Modified: 2005-02-07 19:14 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description david gleba 2004-05-21 20:41:57 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,
dmask=755,uid=500,gid=100,debug=0,workgroup=xx

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
root@redd0:/home/dg#

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
responding.

I would expect it to provide an error message stating
that the mount is gone and allow you to keep browsing
elsewhere.
Comment 1 Gerald (Jerry) Carter 2005-02-07 15:44:47 UTC
This is eierh an smbfs kernel bug or a KDE bug.  Not much we can do about it.
Comment 2 david gleba 2005-02-07 19:14:33 UTC
(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?