Unmounting SMB shares on the desktop

Tom McLaughlin tmclaugh at sdf.lonestar.org
Mon Nov 22 16:04:18 PST 2004


On Sun, 2004-11-21 at 16:31 -0500, Joe Marcus Clarke wrote:
> On Sat, 2004-11-20 at 20:44 -0500, Tom McLaughlin wrote:
> > I've found a rather annoying bug involving nautilus and gnomevfs when
> > used with SMB shares.  I my had my remote mp3 and home shares mounted
> > simultaneously on my desktop.  When I unmounted my home share by right
> > clicking on the icon the share was unmounted but I also lost access to
> > mp3 share.  The song playing in rhythmbox (located on the share) stop
> > playing and I could no longer browse the directory from my desktop.  I
> > brought up the nautilus browser and tried to browse the host
> > (smb://straycat) but no shares will list.  I ran ethereal and I see that
> > while attempting to browse my mp3 share no network traffic is generated
> > between my machine and my server.  I end up having to fix this by
> > sending a SIGHUP to nautilus to regain functionality. 
> 
> I can't seem to reproduce this.
> 

I tailed .xsession-errors after logging in and I see the following line
starts to appear once I lose th ability to browse my mp3 shares:

** (nautilus:1091): CRITICAL **: file corba-env.c: line 149
(CORBA_exception_init): assertion `ev != NULL' failed



> >  
> > 
> > On another note, gnomevfs has some problems getting my workgroup right
> > when I connect to a share.  It's using the default of WORKGROUP.  I had
> > to set it manually through the gconf key /system/smb/workgroup to get it
> > correct.  From looking at recent release notes (2.8.1) it should be
> > picking up the workgroup name from my system's smb.conf but it does not
> > appear to be.  Thanks.
> 
> This is most likely a problem with samba-libsmbclient.  You might try
> creating a ~/.smb/smb.conf with your workgroup name, and see if that
> helps.  However, I think newer versions of the smb-method rely on
> samba-libsmbclient directly to get this information.
> 
> Joe
> 

This I think is mostly a problem with bad design on Gnome's part.  Use
Connect to Server to connect to a smb share and it bypasses
gnome-keyring-manager and the icon type shows up as a server.  Mount the
share through the network:/// location and select mount share and it
will use gnome-keyring-manager and show up as folder.  Gnoem treats
mounting SMB shares in two different ways depending on what path you
take to connect.  I don't get it.  If I can get some time I'll piss and
moan on one of their lists.  :)  

Now that I think of it, possibly these two different connect methods are
conflicting with one another and causing me to lose my SMB mounts?

Tom

> > 
> > Tom
> > 
-- 

BSD# Project - Porting Mono to FreeBSD
http://forge.novell.com/modules/xfmod/project/?bsd-sharp



More information about the freebsd-gnome mailing list