smbnetfs has the same problem, and the developer already has a fix in
testing.
http://sourceforge.net/tracker/?func=detailatid=857137aid=2492545group_id=171223
** Bug watch added: SourceForge.net Tracker #2492545
http://sourceforge.net/support/tracker.php?aid=2492545
--
fusesmb - Not
** Changed in: fusesmb (Ubuntu)
Importance: Low = Medium
** Changed in: fusesmb (Ubuntu)
Status: New = Confirmed
** Changed in: smbnetfs (Ubuntu)
Importance: Undecided = Medium
** Changed in: samba (Ubuntu)
Importance: Low = Wishlist
--
fusesmb - Not working properly -
smbnetfs has the same problem, and the developer already has a fix in
testing.
http://sourceforge.net/tracker/?func=detailatid=857137aid=2492545group_id=171223
** Bug watch added: SourceForge.net Tracker #2492545
http://sourceforge.net/support/tracker.php?aid=2492545
--
fusesmb - Not
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
** Summary changed:
- fusesmb - Not working properly.
+ fusesmb - Not working properly - SIGABORT in getattr() - libsmbclient not
thread safe
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
Status: New = Confirmed
--
fusesmb - Not working properly - SIGABORT in getattr() -
** Summary changed:
- fusesmb - Not working properly.
+ fusesmb - Not working properly - SIGABORT in getattr() - libsmbclient not
thread safe
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
Status: New = Confirmed
--
fusesmb - Not working properly - SIGABORT in getattr() -
Quoting bigal50 (o...@charter.net):
From comments appear to be confirmed
Probably the same than Debian #497572, duplicated in #502129 which was
reported as upstream #5847:
https://bugzilla.samba.org/show_bug.cgi?id=5847
As mentioned in upstream #5847, software affected by such problem
should
From comments appear to be confirmed
New Confirmed
** Changed in: smbnetfs (Ubuntu)
Status: New = Confirmed
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
From comments appear to be confirmed
New Confirmed
** Changed in: smbnetfs (Ubuntu)
Status: New = Confirmed
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: debian
Status: Unknown = New
--
fusesmb - Not working properly.
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.
--
Ubuntu-server-bugs mailing list
** Changed in: debian
Status: Unknown = New
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ehm... Any chance this gets fixed any time soon? It's really starting to
piss me and all of my co-workers off... :(
Before each update we now have to run 'install -f' and afterwards re-
install the old libsmbclient package, since we don't want to override
the files in the base filesystem...
--
** Changed in: samba
Status: Unknown = Invalid
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Bug 293233 contains a SIGABRT backtrace which might be the same crash
we're seeing here.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a
** Bug watch added: Samba Bugzilla #5847
https://bugzilla.samba.org/show_bug.cgi?id=5847
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=5847
Importance: Unknown
Status: Unknown
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You
** Also affects: smbnetfs (Ubuntu)
Importance: Undecided
Status: New
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for the threading tip. I've just edited my startup file to
disable multi-threaded operation, with a command line like this:
smbnetfs /my/mountpoint -s
So far, it hasn't crashed using this mode. (I suspect I have lost some
performance, though.)
--
fusesmb - Not working properly.
Update: smbnetfs crashed again even when running with -s.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Bug 293233 contains a SIGABRT backtrace which might be the same crash
we're seeing here.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a
** Bug watch added: Samba Bugzilla #5847
https://bugzilla.samba.org/show_bug.cgi?id=5847
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=5847
Importance: Unknown
Status: Unknown
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You
Tying together more related bug reports...
(Debian 503038 and Samba 5847 contain some enlightening comments from
the smbnetfs and samba developers)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503038
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497572
Some more offtopic, JFYI: setting smb_open_files_max to 500 instead of
100 in .smb/smbnetfs.conf helped with smbnetfs and multithreaded access,
no errors any more. The complex build process is a really good stress
test for a FS.
--
fusesmb - Not working properly.
I can confirm that on Xubuntu 8.10, the workaround posted by Dmik works
for me. The SMB connection is stable while browsing the network with
Thunar.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Not actually related to the defect but I've just bumped into it.
Intensive multithreaded access to the same files on a share (in my case,
make command run in parallel mode using four threads) causes problems
(sporadic errors like 'no such file or directory' or 'file read error'
that disappear
Actually you can downgrade libsmbclient manually to prevent from braking
package dependencies. Just download a correct package from here
http://packages.ubuntu.com/hardy-updates/libsmbclient and unpack it to
somedir. Then do:
sudo mv /usr/lib/libsmbclient.so.0 /usr/lib/libsmbclient.so.0.bak
Errr, sudo ldconfig of course.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
And cp somedir/CONTENTS/usr/lib/libsmbclient.so.* /usr/lib/ :)
Sorry, but it's really sad that there is no preview/edit function for
comments...
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that downgrading manually to libsmbclient_3.0.28a-1ubuntu4
only fixes the described problem. It breaks the gfvs-backends package
though but it doesn't seem to have any negative effect so far other than
an annoying icon in the notification area and warnings from package
installation
Hmm, there is a more serious side effect after the reboot though: the
computer:/// protocol stops working in nautilus (and some other problems
like missing label names from local hard disk volume mounts) -- all due
to a broken gvfs-backends apparently.
--
fusesmb - Not working properly.
I noticed these problems with gvfs / nautilus as well. I wound up
switching my window manager to fluxbox and removing gvfs-backends and
nautilus*. Probably not the most elegant solution, but I need fusesmb
more than gnome, etc.
--
fusesmb - Not working properly.
FWIW, I downloaded and installed fusesmb_0.8.7-1_amd64.deb and
libsmbclient_3.0.28a-1ubuntu4.4_amd64.deb from Hardy and that seems to
eliminate the Transport endpoint is not connected errors I was getting
previously with 'fusesmb' mounted shares.
--
fusesmb - Not working properly.
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497572
Importance: Unknown
Status: Unknown
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the same problem with smbnetfs. It holds the network longer than fusesmb
but fails eventually.
I thought the problem is mostly in Thunar, but using the smb network through
CLI gives the same failure result.
It seems that the libsmbclient version in ubuntu 8.10 is the problem. 8.04
What is the relationship between this bug and
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/290673 ?
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
For comparison, the same shares mounted on the same machine with mount
-t cifs work perfectly and seem 100% stable.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Florian: I haven't tried smbnetfs on Ubuntu, but in parallel to testing
8.10 I was experiment with Arch Linux and decided to use smbnetfs. I
ran into a very similar bug. Could this be what you are finding?
Versions are probably similar.
http://bugs.archlinux.org/task/12032
--
fusesmb - Not
John Carlyle-Clarke: Yes, it sound similar to the archlinux bug. I saw
crashes in talloc_abort_double_free, but in fusesmb, not in smbnetfs. In
the meanwhile I really doubt that it is the applciation (smbnetfs,
fusesmb) but more the library libsmbclient.
I tried for both (smbnetfs and fusesmb)
Is there anybody out there who has the same problem with smbnetfs? I
have, both fusesmb and smbnetfs both tend to crash in the same way.
smbnetfs leaves no notice in it's logfile.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because
It's a known problem. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497572
meaning It's the new UNSTABLE version of fusesmb that is in Debian lenny
repositories.
It is inherited through Ubuntu repo.
I expirienced same problem in Thunar as the person above.
SOLUTION:
Untill fusesmb is
Seems this solution is still buggy. The connection is working much
longer but still fails eventually with same symptoms.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ubuntu should go to same version of fusesmb as in 8.04 untill fusesmb
team fixes the bug.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can reproduce this bug under two conditions.
1) If my network is not set up correctly, and it is impossible to
connect to a MS networking server even with smbclient, then any attempt
to use fusesmb (understandably) fails in exactly the way that Dr_Willis
reports
2) If my network is set up
Thank you for your bug report. This bug did not have a package
associated with it, which is important for ensuring that it gets looked
at by the proper developers. I have classified this bug as a bug in
fusesmb.
** Changed in: fusesmb (Ubuntu)
Sourcepackagename: None = fusesmb
Importance:
43 matches
Mail list logo
