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

2010-03-18 Thread Mikhail Kshevetskiy
ggy libsmbclient code from the rest of smbnetfs). It was done to get better performance and stability. Mikhail Kshevetskiy > -- > fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe > https://bugs.launchpad.net/bugs/198351 > You received this bug notification

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

[Bug 198351] Re: fusesmb - Not working properly - SIGABORT in getattr() - libsmbclient not thread safe

2009-04-23 Thread Mikhail Kshevetskiy
please update SMBNetFS package to latest git version. It does not contain the bug described here due to libsmbclient isolation in separate process. -- fusesmb - Not working properly - SIGABORT in getattr() - libsmbclient not thread safe https://bugs.launchpad.net/bugs/198351 You received this bu

[Bug 293233] Re: crashing with SIGABRT while scanning network or reading some files

2009-04-15 Thread Mikhail Kshevetskiy
*** This bug is a duplicate of bug 198351 *** https://bugs.launchpad.net/bugs/198351 Please update SMBNetFS to latest git/debian version. -- crashing with SIGABRT while scanning network or reading some files https://bugs.launchpad.net/bugs/293233 You received this bug notification because yo