** Changed in: debian
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/198351
Title:
fusesmb/smbnetfs SIGABORT in getattr() because
** Changed in: debian
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/198351
Title:
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is
** Changed in: samba
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/198351
Title:
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not
** Changed in: samba
Status: Invalid = Unknown
--
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 a member of Ubuntu
Server Team, which is subscribed to samba in
For what it is worth I have been using smbnetfs on hardy jaunty and now lucid
without problems. When I started out, on hardy fusesmb was not working, which
is why I used smbnetfs. I have just revisited and tried fusesmb again. It does
not work on Lucid and I am seeing this.
Running in debug
Marking smbnetfs fixed in Lucid per comments 32 and 35
** Changed in: smbnetfs (Ubuntu)
Status: Confirmed = Fix Released
--
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you
Marking the samba part as wontfix since libsmbclient is not threadsafe
by design and upstream doesn't consider it a bug.
** Changed in: samba (Ubuntu)
Status: Confirmed = Won't Fix
--
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Anyone knows is fusesmb is still affected ?
--
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 a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Actually Samba upstream does consider the non-threadsafeness of
libsmbclient as a bug, it's just that it's going to take a while to fix
it :-).
We're slowly but surely moving towards getting a thread safe
libsmbclient, Can't promise when it will be done, but it is our intent
to get there.
So at
same problems in lucid-current
--
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 a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
adding -s parameter is a workaround for problem in lucid
--
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 a member of Ubuntu
Server Team, which is subscribed to samba in
On Wed, 10 Mar 2010 21:09:58 -
Robert Garshaw launch...@blaze.co.nz 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
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.
--
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
https://bugs.launchpad.net/bugs/198351
You received this bug
13 matches
Mail list logo