[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2014-07-25 Thread Bug Watch Updater
** 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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2014-07-23 Thread Bug Watch Updater
** 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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2011-02-04 Thread Bug Watch Updater
** 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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-10-18 Thread Bug Watch Updater
** 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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-05-20 Thread Peter
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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-18 Thread Thierry Carrez
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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-18 Thread Thierry Carrez
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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-18 Thread Thierry Carrez
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. --

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-18 Thread Jeremy Allison
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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-13 Thread Andrey Gusev
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. --

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-13 Thread Andrey Gusev
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

Re: [Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-13 Thread Mikhail Kshevetskiy
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

[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

2010-03-10 Thread Robert Garshaw
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