[Bug 1016895] Re: smbd crashed with SIGABRT in dump_core()/setgroups being passed a -1 group is causing crashes.

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:3.6.3-2ubuntu2.4

---------------
samba (2:3.6.3-2ubuntu2.4) precise; urgency=low

  [ Olly Betts ]
  * Change "net share allowedusers" to use RPC call that works with
    Microsoft Windows 2008 r2.  (LP: #1061244)

  [ Louis Bouchard ]
  * Fix issue with Windows XP / 7 (LP: #967410) where a USB
    connected printer shared on Ubuntu cannot be added to Windows
    using the "Find a printer in the directory" functionalty.

  [ Adam Conrad ]
  * Cherrypick patch from upstream to resolve a SIGABRT when passing
    setgroups a -1 gid, fixing samba with 3.5 kernels (LP: #1016895)
 -- Adam Conrad <adconrad at ubuntu.com>   Tue, 19 Feb 2013 22:22:12 -0700

** Changed in: samba (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1016895

Title:
  smbd crashed with SIGABRT in dump_core()/setgroups being passed a -1
  group is causing crashes.

Status in Samba:
  Fix Released
Status in “samba” package in Ubuntu:
  Fix Released
Status in “samba” source package in Precise:
  Fix Released
Status in “samba” source package in Quantal:
  Fix Released

Bug description:
  [Impact]
  12.04.2 users cannot share dirs with Samba due to smbd crashing with "sys_setgroups failed".
  With 12.04.2 shipping linux-generic-lts-quantal, Samba is now completely unusable due to this bug, so an SRU is justified.
  The fix has been included upstream and is Fix-Released in the current development versions of Ubuntu (Quantal+).

  [Test Case]
  Right click on a folder, e.g. ~/share, from nautilus, and select to share it.
  If prompted to install Samba, do so, then logout/login and start over the test case.
  Then run `nautilus-connect-server`, select
  Type: Windows share,
  Server: localhost,
  Share: share,
  Domain name: WORKGROUP,
  User name: your unix username,
  Password: your unix password.

  and press the [Connect] button. It will fail, and /var/log/samba/log.hostname will contain an smbd crash with the following lines among others:
  [2013/02/18 12:51:16.500421,  0] lib/util.c:1117(smb_panic)
    PANIC (pid 7594): sys_setgroups failed

  [Regression Potential]
  Since the bug was fixed upstream, and since Samba is now completely unusable, regressions are not very likely.

  
  [Original bug description]
  Sorry for not being of any help here. I don't really know what happened. There was suddenly a report about a system problem. and apport started. just updated a few hours ago.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: samba 2:3.6.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
  Uname: Linux 3.5.0-1-generic i686
  ApportVersion: 2.2.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Jun 24 19:37:16 2012
  ExecutablePath: /usr/sbin/smbd
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120509)
  NmbdLog:

  ProcCmdline: smbd -F
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SambaServerRegression: Yes
  Signal: 6
  SmbConfIncluded: Yes
  SmbLog:

  SourcePackage: samba
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   dump_core ()
   smb_panic ()
   ?? ()
  Title: smbd crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  WindowsFailedConnect: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1016895/+subscriptions