login crashed with SIGSEGV in dump_core()

Bug #278617 reported by Jonh Wendell
10
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
New
Undecided
Unassigned

Bug Description

I can't login anymore

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /bin/login
Package: login 1:4.1.1-1ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /bin/login --
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
Signal: 11
SourcePackage: shadow
StacktraceTop:
 dump_core () from /lib/security/pam_smbpass.so
 smb_panic () from /lib/security/pam_smbpass.so
 get_global_sam_sid () from /lib/security/pam_smbpass.so
 pdb_set_user_sid_from_rid ()
 init_sam_from_buffer_v3 () from /lib/security/pam_smbpass.so
Title: login crashed with SIGSEGV in dump_core()
Uname: Linux 2.6.27-4-generic i686
UserGroups:

Revision history for this message
Jonh Wendell (wendell) wrote :
Revision history for this message
Jonh Wendell (wendell) wrote :

my /var/log/messages: login[5847]: segfault at 0 ip b7c90abb sp bfbabcb0
error 4 in pam_smbpass.so[b7c34000+12a000]

In order to login, I had to reboot in recovery mode, get a root shell
and comment out the pam_smbpass.so in /etc/pam.d/common-[auth,password]

Revision history for this message
Nicolas François (nekral-lists) wrote :

The SIGSEGV occurs in /lib/security/pam_smbpass.so

Revision history for this message
Michael Gratton (mjog) wrote :

This can result from a user action using Nautilus:

- right-click a folder
- select "Sharing options"
- check "Share this folder"
- click "Create Share"
- wait for Samba will be downloaded an installed.

I then ended up uninstalling it because I found a better way to share the directory, but found after that I could not login or use `sudo'.

Running an strace on `login' when trying to debug this showed that the samba password file was being accessed shortly before the segfault, so it seems that the presence/non-presence of this file may have been the cause of the problem.

Note that this might be quite serious as any user that decides to share a folder might be affected, and they will likely not know how to fix it as it breaks sudo.

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

Other bug subscribers

Remote bug watches

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