FS#18908 - [nautilus] can't access windows/samba shares
Attached to Project:
Arch Linux
Opened by Jorge Ortega (stargeizer) - Thursday, 01 April 2010, 14:26 GMT
Last edited by Ionut Biru (wonder) - Monday, 31 May 2010, 19:28 GMT
Opened by Jorge Ortega (stargeizer) - Thursday, 01 April 2010, 14:26 GMT
Last edited by Ionut Biru (wonder) - Monday, 31 May 2010, 19:28 GMT
|
Details
Updating to gnome 2.30 and all related packages will break
the ability to browse all windows/samba shares.
Open nautilus and type smb://xx.xx.xx.xx (xx.xx.xx.xx is the ip address of any machine) and the operation will never end (error or anything)... wait... 5 minutes after i get the following message: "DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired or the network connection was broken" The share can be browsed from other machines. Trying to browse the "net" with nautilus gives the same results. Enabled all pertinent daemons (hal, dbus, samba). And tested (strange thing considering gnome is not in "testing" repository) with nsswitch.conf with "wins" parameter (gives a segfault and in the command line an "aborted" message) and without (only possible to browse using ip). I think there's another bug report about wins and nsswitch... |
Closed by Ionut Biru (wonder)
Monday, 31 May 2010, 19:28 GMT
Reason for closing: Fixed
Additional comments about closing: samba 3.5.3
Monday, 31 May 2010, 19:28 GMT
Reason for closing: Fixed
Additional comments about closing: samba 3.5.3
folks. I had this issue with gnome 2.28 as well and the only solution I know of is to downgrade smbclient to smbclient-3.4.6-1-i686.pkg.tar.gz
I am not sure if this is possible in gnome 2.30 due to other dependencies on smbclient >= 3.5
edit: if i remember well, sometimes accessing uses gvfs 90% processor and when i kill it i have your error
FS#18653Also, reported upstream to samba as well: https://bugzilla.samba.org/show_bug.cgi?id=7250
Using the current repo, i can at least go to smb://xx.xx.xx.xx and allows me to browse files and so... Good for one.. but i can't use the "Network" icon in the nautilus window... will just get an Dbus error 5 minutes later or so.... always something... but i can ping or call any samba machine by name, just by IP. (try to do a smb://this_machine will produce an error message (sometimes segfault, sometimes Dbus)... and pinging using the command line will give an "Aborted" message...
Well... using the testing repo, and doing a pacman -Syu, reboot (or else pacman will complain about libcrypto and libssl), i tested samba 3.5.2 and at least i recover the ability to browse the network using the command line. (ping works, command line samba tools works) But now i can't use gnome to display smb shares even if i try to do a smb://xx.xx.xx.xx. Doing so will produce a Dbus error after 5 minutoes or so...
Well... partially broken in current and partially broken in testing, diferent ways...
patch is here : https://bugzilla.gnome.org/show_bug.cgi?id=606902
for what i understand, the bug is in Dbus... now all we need is a developer that can apply the patch and put a testing package online...
(Still takes more CPU usage/time than the older versions (i mean gnome 2.28) but at least the windows shares/samba shares are browseable again without the CLI.
After updating, is needed to reboot though. (otherwise, dbus errors will appear))
Regards
J.
Connecting with windows shares is possible ONLY if anothes process(es) taking less than 50% CPU time (more or less)... having another process using more than 50% and try to browse a windows share often will produce a Dbus error. (timeout by message bus)
Connecting to linux shares via samba, will way often produce an Dbus timeout error, even if CPU usage is near 0%.
sigh... we'll have to report upstream again...
UPDATE: i got also this message of error in the logs:
kernel: gvfsd-smb[3269]: segfault at c35dec79 ip b75a9f68 sp b6533b50 error 5 in libsmbclient.so.0[b7141000+5a3000]
This happens when a Dbus timeout is triggered, both when connecting to windows and linux shares.
Regards
J.
PS. I also have such error in logs:
gvfsd-smb[7101]: segfault at c35dec79 ip b7606f68 sp b66ddb50 error 5 in libsmbclient.so.0[b719e000+5a3000]
FS#18653. i should close this as a duplicate to that.