FS#19077 - [samba] segfault when accessing samba shares with "share" security level

Attached to Project: Arch Linux
Opened by Benjamin Wild (honki) - Tuesday, 13 April 2010, 13:45 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 18 June 2011, 08:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Upstream bug in samba. If you try to access a samba share when the samba sever security level is set so "share", smbclient will segfault. This bug is related to  FS#18908 .

There's a fix in the current dev version of samba:
- https://bugzilla.samba.org/show_bug.cgi?id=7250
- http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=34f0cff0664f1c160ee7442461e9f875e8d8f4dc;hp=dc689827114c46b3ca2a75082421dc2d98001ce7

Arch BBS discussion related to this bug:
- http://bbs.archlinux.org/viewtopic.php?pid=742669

The patch also fixed the nautilus/dbus problems reported in  FS#18908  for me.

I attached an updated PKGBUILD which includes the patch mentioned above.
(application/x-gzip)    samba-3.5.2-2.src.tar.gz (3.6 KiB)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 18 June 2011, 08:34 GMT
Reason for closing:  No response
Comment by Benjamin Wild (honki) - Tuesday, 13 April 2010, 13:49 GMT
Ooops, summary should be: [samba] smbclient segfault when accessing samba shares with "share" security level
severity probably medium or high...
Comment by Mike Dill (Theoden) - Tuesday, 13 April 2010, 19:03 GMT
I have been having this problem consistently since the gnome-2.3.0 upgrade. I downloaded and rebuilt samba and smbclient using samba-3.5.2-2.src.tar.gz as referenced above. It did not work at all. I still cannot browse samba shares in nautilus. When I try I get the following error messages:

ERROR MSG 1:
"Opening "RINGWRAITH". You can stop this operation by clicking cancel."

ERROR MSG 2:
"Unable to mount location
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)"

After giving up and closing nautilus, if I run 'top' I see that a process called 'gvfsd-smb-brows' is running using 99% of my cpu - and 'nautilus' is still running.

So the fix suggested above by the reporter does not work.

--Theoden
Comment by Benjamin Wild (honki) - Tuesday, 13 April 2010, 20:36 GMT
Well that's weird. I tried it on two different machines running Arch and it fixed the problem on both of them. Before I applied the patch, I always got the same dbus error message you get, but never the "RINGWRAITH" one, so maybe this is more then one bug you're experiencing?

Regarding the gvfsd-smb-brows process: Someone mentioned in the arch bbs discussion thread that killing this process and restarting nautilus fixed the problem, so you could try if that works for you as well...
Comment by Mike Dill (Theoden) - Tuesday, 13 April 2010, 22:58 GMT
I tried killing the 'gvfsd-smb-brows' process and restarting nautilus - no go. I tried rebooting - shutting down and starting up again - and many other things. Nada. But samba is working ok - it was before. I have gnome-commander installed and I can browse samba shares all day there. In addition - I can manually mount samba shares. So the problem is most definately a dbus / nautilus problem as I see it.

Anyway - thanks for the input. :)

--Theoden
Comment by Benjamin Wild (honki) - Wednesday, 14 April 2010, 11:38 GMT
Than it's definitely a different problem. When I tried to manually access a share using smbclient before applying the patch smbclient always segfaulted...
Comment by Tobias Powalowski (tpowa) - Monday, 01 November 2010, 20:19 GMT
Is this still an issue with latest samba 3.5.6?
Comment by Greg (dolby) - Friday, 04 March 2011, 05:17 GMT
Has this been fixed?

Loading...