Ok, this actually is a bug in libpam-smbpass, not in swat.
When recompiling the packages with debug info, the backtrace from swat
is:
#0 0xb7217600 in ?? ()
#1 0xb7d7923c in _talloc_free () from /usr/lib/i386-linux-gnu/libtalloc.so.2
#2 0x8027fae1 in smb_iconv_close (cd=0x8081f768) at
*** This bug is a duplicate of bug 1015935 ***
https://bugs.launchpad.net/bugs/1015935
** This bug has been marked a duplicate of bug 1015935
SWAT segfaults when trying to view full configuration
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Right, our bug reporter investigated this a bit further, and it turns out that
removing libpam-smbpass fixes the crash, and reinstalling libpam-smbpass causes
the crash to happen again.
This also explains why starting swat without the authentication check doesn't
trigger the crash.
As a next
Public bug reported:
When running swat on a 32bit 12.04 install, swat segfaults when the user
clicks on the Full View button in the configuration menu. This only
happens on the 32bit install, the 64bit install seems fine.
This was reported to upstream under
** Bug watch added: Samba Bugzilla #8999
https://bugzilla.samba.org/show_bug.cgi?id=8999
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=8999
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server
Ok, my containers do start up again and seem to behave ok. I'm happy to
test this for a more extended period of time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
As of 2010-11-16, this bug is not yet confirmed to be fixed. If you want
to help, please test the bugfix on the corresponding Samba bug and
report your results on the Samba bugzilla.
--
ntlm_auth returns invalid NT_KEY
https://bugs.launchpad.net/bugs/623342
You received this bug notification
See http://lists.samba.org/archive/samba/2006-September/124961.html for
an explanation of the option
--
files incoming through nautilus-share should be created with user ownership,
instead of nobody
https://bugs.launchpad.net/bugs/268663
You received this bug notification because you are a
Being the person responsible for the Wine dependency, here's my take on this:
ntlm_auth without winbindd is technically useless for about every use case
besides the (still) limited way Wine uses it. Given that most package managers
go and install recommends, you'd then get (at best) Wine
Looks like the same bug. Does the patch from the upstream bugtracker fix
it for you?
--
firefox 3.0.3 crashes (no SIG) on most pages w/ images when using nss_wins:
8.10beta AMD64
https://bugs.launchpad.net/bugs/286119
You received this bug notification because you are a member of Ubuntu
Server
If you scroll up to the top of the page, you see an affects package
samba that links to the samba bugzilla (link is called samba-bugs). The
patch is in there.
--
firefox 3.0.3 crashes (no SIG) on most pages w/ images when using nss_wins:
8.10beta AMD64
https://bugs.launchpad.net/bugs/286119
You
Grobot, your smbclient problem is fixed with the fix to bug #264943.
--
[SRU] Intrepid: No Access to NAS (samba=2.2.x) shares any more
https://bugs.launchpad.net/bugs/282298
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
As requested by Christian, here's a patch for the v3-2-stable tree,
applies to both 3.2.5 and 3.2.6 without any problems.
** Attachment added: Complete patch for segfault, visibility issue and write
issue.
http://launchpadlibrarian.net/20795250/bug_5953_complete.patch
--
gvfsd-smb crashed
This is a bit tricky to fix, as we're basically not doing anything
wrong. It seems like the TCP/IP stack and/or the SMB server on the NAS
box doesn't cope with fragmentation. But that's one layer below of our
control, and perfectly valid in TCP networking.
However, Samba developer Volker Lendecke
I have to admit that the Nautilus error is all but helpful. Could you
try with smbclient as described by the initial reporter and check if
that works or give the error output from smbclient?
--
[SRU] Intrepid: No Access to NAS (samba=2.2.x) shares any more
https://bugs.launchpad.net/bugs/282298
Thanks for the traces, I'll have a look at them first thing tomorrow.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ok, it seems like we're misreporting the byte count in the WriteAndX
request, looking at a fix.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
The ls command in smbclient works just as expected against a Samba
server. I suspect that the server's handling of the list command is
broken, but I'd need a network trace of this. Ideally for a directory
that contains multiple files with multiple suffixes, running ls, ls
*.one of the suffixes ls
Well, you'd probably see the ERRHRD - 39 bug if you try to put a file
without doing an ls first, on a broken CIFS server. But anyway,
separate report for this, please. We can discuss if it's really
something that should be fixed in Samba that report ;)
A good way to get a working NAS box is to
Ok, seems like we're also tracking the write problem in the same Samba bug, so
I'd suggest we keep the discussion here after all. I can confirm that if this
worked with Samba 3.0 and works with Windows, there's a Samba bug we need to
fix. Could anyone get me a trace of Samba 3.2 trying to put a
As a short status update, especially for the Ubuntu packaging folks:
- A patch in Samba 3.2.6 fixes the crash bug, but does not correctly display
all the directories.
- The patch I posted, which fixes the display problem, has been pushed to the
v3-2-test branch and will be in the next 3.2.
Hm, our initial guess is that these NAS disks all run the same CIFS
server, which doesn't handle what our smbclient is sending and dies,
giving back a disk full error. It should be unrelated to the segfault
this bug is about, though. I'm still trying to contact the person who
initially added that
The pcap dump (i.e. the binary data, not the text file) was pretty much
what I needed. Thanks alot.
Could anyone try the attached patch on top of current v3-2-test git?
** Attachment added: Fix offset check in interpret_long_filename
http://launchpadlibrarian.net/20398252/bug_5953_fix.patch
This is tracked in a different Samba bug.
** Changed in: samba
Bugwatch: Samba Bugzilla #5942 = Samba Bugzilla #5953
Status: Invalid = Unknown
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a
Seems like Jeremy Allison pushed a fix for that to git on 2008-12-08
already.
However, the reporter of the samba bug is experiencing the same issues
as rossjenkins. I'll follow up on that.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug
I would be wary to remove the offset check. I'm not really into that
code, but removing it will break offsets when there actually is no name
in that Info1 struct. Can anybody provide a tcpdump/wireshark capture
file of a smb connection that causes mentioned segfault?
--
gvfsd-smb crashed with
I'll look into this some more tomorrow. This seems to be an issue
introduced in Samba 3.2.x. I should be able to write a test case using
the network trace.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a
Yes, that's because Samba disabled the old, insecure lanman auth
authentication scheme per default a couple of versions back. As you
said, it's easy to turn on from the config file. :)
--
[SRU] Intrepid: No Access to NAS (samba=2.2.x) shares any more
https://bugs.launchpad.net/bugs/282298
You
28 matches
Mail list logo