Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18531 - [samba] Problem resolving hostnames ('hosts: wins' in '/etc/nsswitch.conf')
Attached to Project:
Arch Linux
Opened by Bruno Mazotti (bmazotti) - Tuesday, 02 March 2010, 16:28 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 08 April 2010, 10:37 GMT
Opened by Bruno Mazotti (bmazotti) - Tuesday, 02 March 2010, 16:28 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 08 April 2010, 10:37 GMT
|
DetailsDescription:
I'm using the line: hosts: files dns wins in '/etc/nsswitch.conf' file. I'm starting the 'samba' daemon and I've changed the file '/etc/conf.d/samba' to use this line: SAMBA_DAEMONS=(smbd nmbd winbindd) When I try to resolve a hostname in a terminal with some command like 'ping', 'ssh', etc, with the package 'samba-3.5.0-1' ('/lib/libnss_wins.so' ?) the terminal just outputs 'Aborted'. I downgraded to the following packages: pacman -U samba-3.4.6-1-i686.pkg.tar.gz smbclient-3.4.6-1-i686.pkg.tar.gz And it started working nicely. Reverting to the lastest version of these packages the problem comes back. As a work around I'll be using the older version cited above. Please ask if more information is needed. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 08 April 2010, 10:37 GMT
Reason for closing: Fixed
Additional comments about closing: in samba 3.5.2-1
Thursday, 08 April 2010, 10:37 GMT
Reason for closing: Fixed
Additional comments about closing: in samba 3.5.2-1
FS#18537have a strace log from a ping command.https://bugzilla.samba.org/show_bug.cgi?id=7202
http://us1.samba.org/samba/ftp/stable/samba-3.5.1.tar.gz
And the problem persisted with this newer version.
gvfsd-smb[2864]: segfault at c35dec79 ip b7749068 sp b67e4b60 error 5 in libsmbclient.so.0[b72e1000+5a2000]
Force a downgrade to 3.4.6 solves the ping problem and the nautilus/dbus problem (making use of windows share possible again).
https://bugzilla.samba.org/attachment.cgi?id=5511
https://bugzilla.samba.org/attachment.cgi?id=5522
http://gitweb.samba.org/?p=samba.git;a=commit;h=09f270e748263f2fb02683a9376ae185a5534178
http://gitweb.samba.org/?p=samba.git;a=commit;h=fc80ff40025a35a61aa1a0c7666f98b4c0b78924
Still forcing downgrade to 3.4.6 works. (at least until a fix is available in repositories)
Workaround: delete "wins" parameter in /etc/nsswitch.conf
The net will be normal again, but you can't resolve windows names anymore, so some users (mostly users/admins that need compatibility with windows machines) are screwed if they update gnome or samba).