@Andres:
About $script_security, yes, we also need it to be passed as an option.
And yes, something similar to what you propose just might take the best
of both worlds : use start-stop-daemon to avoid failure on start when a
PID file is not deleted, and still have our $script_security and boot-
Apparently this is the (successful) smbclient output you get once you edited
the smb.conf file so that bcast is tried before host. I need the smbclient
trace for a failure case... Could you restore the original smb.conf file (the
one that fails) temporarily and regenerate/attach the resulting
I think it's a hostname resolution issue on the client side, due to mismatch
between DNS hostname and NetBIOS name. Could you run:
smbclient -d 4 -N -L //servername
on the client in both cases and post the corresponding output ?
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
*** This bug is a duplicate of bug 330833 ***
https://bugs.launchpad.net/bugs/330833
** This bug has been marked a duplicate of bug 330833
NetworkManager always overwrites default route when connecting to OpenVPN
network
--
Enabling VPN connection in NetworkManager messes up routing
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
** This bug is no longer a duplicate of bug 368273
Jaunty 9.04 Blind to XP's Shared Network Printer
** This bug has been marked a duplicate of bug 329974
system-config-printer.py SIGSEGV in
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
** This bug is no longer a duplicate of bug 368273
Jaunty 9.04 Blind to XP's Shared Network Printer
** This bug has been marked a duplicate of bug 329974
system-config-printer.py SIGSEGV in
Reopening as this is not fixed in Jaunty, multiple reports show.
According to duplicate bug 368273 this seems to be hitting i386 but not
amd64, which might be the reason why Brian failed to reproduce it.
A workaround to be able to create printers (using IP address) is
described in
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
** This bug has been marked a duplicate of bug 329974
system-config-printer.py SIGSEGV in _nss_dns_gethostbyname2_r(), adding a
printer, i386 only
--
Jaunty 9.04 Blind to XP's Shared Network Printer
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
** This bug has been marked a duplicate of bug 329974
system-config-printer.py SIGSEGV in _nss_dns_gethostbyname2_r(), adding a
printer, i386 only
--
print configuration crashed while adding printer
** 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
A nearly identical crash in _nss_dns_gethostbyname2_r is tracked in bug
329974. I suspect it's coming from the same bug.
This seems to be affecting i386 only.
Opening a samba task since the crash is probably libsmbclient-related.
** Also affects: samba (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 359088 ***
https://bugs.launchpad.net/bugs/359088
** This bug has been marked a duplicate of bug 359088
system-config-printer.py crashed with SIGSEGV in
_nss_mdns4_minimal_gethostbyname2_r()
--
with trial cd, tried to browse for a windows xp printer
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
So it seems that local access (tux-tux) is working correctly. Could you
try to access tux with smbclient from another machine (or access another
machine from tux) and send the corresponding smbclient log ? (using the
original, failing name resolve order set on the client, please)
Also could you
Can't reproduce that on Jaunty. On my laptop, switching to VC1 before
logging into Gnome (and having NM connect to my wireless) smbd and nmbd
(default smb.conf) are running, listening to *.*
Could you tell me what version of Ubuntu you're running and attach your
smb.conf ?
** Changed in: samba
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
Samba update crashed
https://bugs.launchpad.net/bugs/314318
You received this bug notification because you are a member of Ubuntu
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Changed in: samba (Ubuntu)
Status: Incomplete = Invalid
--
Cant install samba
https://bugs.launchpad.net/bugs/314494
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
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Reproduced on Jaunty:
$ net usershare add My Shared Folder /home/user/My Shared Folder
$ net usershare list
my shared folder
Workaround:
$ mv /var/lib/samba/usershares/my shared folder /var/lib/samba/usershares/My
Shared Folder
$ net usershare list
My Shared Folder
** Changed in: samba
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
I can confirm the sad tale of woe with the OpenLdap tutorial on Jaunty.
It took me a while to figure out that pasting the syncrepl config text
into an ldif file didn't work. When I ran ldapmodify on that ldif, it
would skip over parts of the file. As a consequence, things like the
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
I switched to the amd64 version of 9.04 and can no longer reproduce the
bug since it isn't resident in the 64-bit version.
--- On Fri, 5/15/09, Thierry Carrez thierry.car...@ubuntu.com wrote:
From: Thierry Carrez thierry.car...@ubuntu.com
Subject: [Bug 329974] Re: SIGSEGV in
** Changed in: nagios-plugins (Debian)
Status: Unknown = Confirmed
--
[SRU] Buffer overflow in check_ntp_peer - Nagios can't check time servers in
Intrepid
https://bugs.launchpad.net/bugs/291265
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I set the smb.conf back to the default and here is the output of your 2
commands. These 2 commands take a while as it seems to time out after a
bit. If I run them with my modified smb.conf, they execute instantly
and show a lot of info on my network, with no apparent error messages.
Could you
The problem is apparently in your DNS resolution. Basically the master
browser says that UPSTAIRS exists. But when you browse it tries to
resolve UPSTAIRS to an IP address...
With the default resolve order, it tries DNS resolution before
broadcast. For some reason (I suspect a DNS that answers
unfortunately, I have the same bug (
Ubuntu 9.04.
I've found an another workaround:
- remove files with *.pub extension from ~.ssh folder
I don't have an idea, but may this issue is connected with seahorse agent?
Any help would be appreciated
--
openssh public key auth broken if one has many
ping upstairs does indeed try to resolve 67.63.55.3. This IP address is
nowhere in my network. ping does resolve it, but it takes about 23
ms. I have no idea why this should be. I have the exact same problem
on 2 different networks in 2 different towns using different brands of
routers. They
One last thought. If the default resolve order is using DNS before
broadcast, doesn't that slow down local network browsing? Since this
may turn out to be an ISP problem on my end, wouldn't it make sense to
change the default resolve order so it looks at the local network before
trying DNS?
** Also affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: New
--
View ast_sipfriends_gs anlegen auf Slave MySQL geht nicht
https://bugs.launchpad.net/bugs/351693
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Just forwarded it to Debian.
** Changed in: php5 (Ubuntu)
Status: New = Triaged
--
Please remove language bias from php5-cli package description
https://bugs.launchpad.net/bugs/329900
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: php5 (Debian)
Status: Unknown = New
--
Please remove language bias from php5-cli package description
https://bugs.launchpad.net/bugs/329900
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep
samba
libpam-smbpass 2:3.3.2-1ubuntu3 samba install ok installed
libsmbclient 2:3.3.2-1ubuntu3 samba install ok installed
libwbclient0 2:3.3.2-1ubuntu3 samba install ok installed
samba 2:3.3.2-1ubuntu3 install ok installed
35 matches
Mail list logo
