smbd crashed with SIGABRT in raise()

Bug #759711 reported by Jean on 2011-04-13
This bug affects 11 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)

Bug Description

Binary package hint: samba

session setup failed: NT_STATUS_LOGON_FAILURE

Description: Ubuntu Natty (development branch)
Release: 11.04

  Installé : 2:3.5.8~dfsg-1ubuntu2
  Candidat : 2:3.5.8~dfsg-1ubuntu2
 Table de version :
 *** 2:3.5.8~dfsg-1ubuntu2 0
        500 natty/main amd64 Packages
        100 /var/lib/dpkg/status

I just opened my session about 30 seconds before this bug appeared. I was not using samba...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: samba 2:3.5.8~dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Apr 12 16:59:13 2011
ExecutablePath: /usr/sbin/smbd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: smbd -F
ProcEnviron: PATH=(custom, no user)
SambaClientRegression: Yes
Signal: 6
SourcePackage: samba
 raise () from /lib/x86_64-linux-gnu/
 abort () from /lib/x86_64-linux-gnu/
 dump_core ()
 ?? ()
 exit_server ()
Title: smbd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)

Jean (jeangab37) wrote :

 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 dump_core () at lib/fault.c:337
 exit_server_common (how=<value optimized out>, reason=<value optimized out>) at smbd/server.c:902
 exit_server (explanation=0x24f2 <Address 0x24f2 out of bounds>) at smbd/server.c:926

Changed in samba (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Chuck Short (zulcss) wrote :

Thanks for the bug report I have submitted it upstream.


visibility: private → public
Changed in samba (Ubuntu):
status: New → Confirmed
Changed in samba:
importance: Unknown → Medium
status: Unknown → Confirmed
Antti Laiti (pulk) wrote :

I’ve seen this in 13.04 alpha too.

Hans Ginzel (hans-matfyz) wrote :

Me too in raring.

Hans Ginzel (hans-matfyz) wrote :

Could be related to bug #374589. At least in my case.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.