This is believed to be fixed in karmic by the bug 374674 fix. Please
reopen if you can still reproduce it on current karmic.
** Package changed: samba (Ubuntu) = glibc (Ubuntu)
** Changed in: glibc (Ubuntu)
Status: New = Fix Released
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing
glibc was updated in karmic removing the problematic patch. Would be
good to confirm that the problem is gone on karmic now.
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
https://bugs.launchpad.net/bugs/329974
You received this bug notification because you are a
I was not able to see the printers. I updated the system with third
party canonical repositories on, and the bug disappeared.
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
https://bugs.launchpad.net/bugs/329974
You received this bug notification because you are a
@filozofio:
What do you mean by third-party canonical repositories ? Did you enable my
PPA as suggested in comment 20 ? In doubt please post the output of dpkg- l
libc6. Thanks !
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
https://bugs.launchpad.net/bugs/329974
The smbclient binary was already present, as I mentioned in my previous
message (smbclient -L server shows the correct info). However, after
some more digging it seems I had samba4 installed that that appeared to
be the problem.
I have downgraded to samba 3 and now everything works ok, I can add
I forgot to mention but I had the same problem, I put Samba4 on thinking
that would help but it did not, and I then did a complete removal of all the
samba4 and any other samba I could and then did a reinstall of samba via
synaptic. However this did NOT install the smbclient. I am puzzled by this
Smbclient is part of the standard Ubuntu or Xubuntu installation. If it
wasn't present you must have done something to cause its removal. While
SAMBA is not preinstalled as part of the standard Ubuntu or Xubuntu
installation, it is not necessary to browse Windows shares. Samba
enables Linux
Thanks but samba was installed when did my 8.01 install from the original
Ubuntu download...I am Ok now and I cannot seem to help anyone else, thanks
for all your help.. all of you. Also smbclient maked it possible to print on
my win box attached printer.
I am sure you are right, and I know next
I am running Ubuntu 9.04 AMD64 with the latest patches and in
Administration-Printing-New Printer-Network Printer I do not have any
Windows printer via SAMBA option. The printer I am trying to print is
valid and working (several other windows boxes print to it). smbclient
-L server also shows
I also run Ubuntu 9.04 AMD64 and have no problem at all, although it was
present on the same machine when I ran the i386 version. This problem
does not seem to exist in 64-bit Ubuntu. I suspect that you have a setup
problem. I recommend that you read the post at the following link:
just install smbclient .. you can do this in the command window, not
abslotuley sure but I think it is something like:
sudo apt-get install smbclient
Make sure that samba is not loaded when you do this. you need to do a stop
on samba if it is running.
This worked great fro me under Ubuntu 9.04
To anyone that can reproduce this precise bug on a Jaunty test system:
Could you test and install glibc 2.9-4ubuntu6.1~ppa1 from my PPA at
https://launchpad.net/~ttx/+archive/ppa and let me know if it fixes the problem
or not. You should upgrade the libc6 binary package (which should pull the
I do not know how to do a test without reloading 9.04 . I do not have a
problem now and can print fine with 9.04 and a 32 bit O/S. If you can give
me a safe way to check out your idea I will try but I am very concerned that
I will be back in the mess again. It took me nearly 35 hours to have a
Yes the printer does have the hand and it was working fine under 8.04.. I
also do not have ability to do the workaround as my GUI does not show
windows printer via Sambaunder networked printers in the
systemadminprinting GUI menu.. ( why not??)
The person who did the workaround used the 64 bit
motorman: I was the creator of the workaround on a 32-bit system. I have
since loaded a 64-bit system and, yes, it doesn't have this bug.
While it could be a Windows problem, possibly something isn't right with your
SAMBA setup. Even is SAMBA isn't installed, smbclient utilizes the samba.conf
Ed, Thanks , I did some checking and I have two other winxp systems each
with printers attached, both can print on the other machine.
I tried to follow someone who wrote about modifying smb.conf and messed it
up so badly that I downloaded a default version from ubuntu 8.4 as can't
find a default
9.04 seems to have a problem and cannot print to winxp although I could
with 8.4 . I can see all shared folders on winxp box but cannot see or
find the printer attached to winxp box. Also the GUI for selecting a
printer d0es not show Samba connected printers and I think it was
there for 8.4 . I
, then
this workaround will fix the printer issue.
--- On Fri, 5/29/09, the motorman rdoct...@gmail.com wrote:
From: the motorman rdoct...@gmail.com
Subject: [Bug 329974] Re: SIGSEGV in _nss_dns_gethostbyname2_r() browsing
Samba printers, i386 only
To: remocmail-1s...@yahoo.com
Date: Friday, May 29, 2009
Motorman:
Are you positive that the printer on Windows is set to SHARE? If so, the
printer shown in Windows' Printers and Faxes dialog should have a little hand
on it (see attachment).
** Attachment added: Windows Printer Dialog
http://launchpadlibrarian.net/27287417/printer.JPG
--
SIGSEGV
** Summary changed:
- system-config-printer.py SIGSEGV in _nss_dns_gethostbyname2_r(), adding a
printer, i386 only
+ SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
Hm, I am struggling with the root cause of this. It is a Jaunty-specific
issue, but the libsmbclient code shown in the trace didn't really change
since Intrepid... However the glibc code (where the SIGSEGV ultimately
occurs) did change. In particular sysdeps/posix/getaddrinfo.c. So maybe
it's a
Unfortunately I couldn't reproduce the issue. I can set up Samba-shared
printers on 9.04 / i386 without a crash. Maybe it's linked to Windows XP
shared printers...
@Ed Comer or other reproducers:
If the issue is linked to the glibc bug, then it should be fixed in Karmic (the
glibc patch was
Hm, that wouldn't work, Karmic glibc still has patches/any/local-
ipv6-lookup.diff so the test wouldn't prove anything. Please ignore what
I just said.
--
SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only
https://bugs.launchpad.net/bugs/329974
You received this bug
in _nss_dns_gethostbyname2_r() browsing Samba
printers, i386 only
To: remocmail-1s...@yahoo.com
Date: Friday, May 15, 2009, 11:59 AM
Unfortunately I couldn't reproduce the issue. I can set up Samba-shared
printers on 9.04 / i386 without a crash. Maybe it's linked to Windows XP
shared printers...
@Ed Comer or other
24 matches
Mail list logo
