Comment 35 for bug 198351

On Wed, 10 Mar 2010 21:09:58 -0000
Robert Garshaw <email address hidden> wrote:

> Smbnetfs has been fine for me since I upgraded to karmic. But I'm not
> sure if I still have any fixes in place. As far as I'm aware it's all
> stock.

This problem was fixed in smbnetfs-0.5.x.
Use smbnetfs-0.5.2 or latest git

Mikhail Kshevetskiy

> --
> fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
> https://bugs.launchpad.net/bugs/198351
> You received this bug notification because you are subscribed to
> smbnetfs in ubuntu.
>
> Status in Samba: Invalid
> Status in “fusesmb” package in Ubuntu: Confirmed
> Status in “samba” package in Ubuntu: Confirmed
> Status in “smbnetfs” package in Ubuntu: Confirmed
> Status in Debian GNU/Linux: New
>
> Bug description:
> Installed and enabled fusesmb Just like i have done in the past , following
> the FuseSmb wiki page. However no shares or workgroups are shown now under
> hardy. As the root user, a 'ls -l' of the Mounted fusesmb point gives the odd
> output of.
>
> ls -l
>
> drwxr-xr-x 2 willis willis 4096 2008-02-16 07:30 Music
> d????????? ? ? ? ? ? Network
>
> as a user ls -l gives .
>
> drwxr-xr-x 2 willis willis 4096 2008-02-16 07:30 Music
> drwxr-xr-x 3 willis willis 4096 2008-03-04 08:10 Network
>
>
> the fusesmb -d option (for debugging) is not really giving any info as to
> what is failing.
>
> Aparently related to
> https://bugs.launchpad.net/ubuntu/+source/fusesmb/+bug/157494
>
> fusesmb Installed: 0.8.7-1
>
>