Ubuntu
sudo package

sudo crashed with SIGABRT in kill()

Bug #1565332 reported by Michael Dooley
220
This bug affects 31 people
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

crash appeared in less than a second after boot-up

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Fri Apr 1 15:23:06 2016
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2016-03-28 (4 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1)
ProcCmdline: /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- caja
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: sudo
StacktraceTop:
 kill () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: sudo crashed with SIGABRT in kill()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK

Revision history for this message
Michael Dooley (mdooley) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /build/sudo-g3ghsu/sudo-1.8.16/src/sudo.c:330

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in sudo (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sudo (Ubuntu):
status: New → Confirmed
Apport retracing service (apport)
tags: added: yakkety
Marc Deslauriers (mdeslaur)
information type: Private → Public
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Possible culprit:
https://www.sudo.ws/repos/sudo/rev/153f016db8f1

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Confirmed, this is caused by the following change in behaviour:

When the command sudo is running dies due to a signal, sudo will now send itself that same signal with the default signal handler installed instead of exiting. The bash shell appears to ignore some signals, e.g. SIGINT, unless the command being run is killed by that signal. This makes the behavior of commands run under sudo the same as without sudo when bash is the shell. Bug #722.

This makes a process receiving a SIGABRT cause sudo to exit with the same failure.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Is bug #1663453 also a duplicate of this bug? I raised two bugs yesterday that I thought were probably the same but one got marked as a duplicate of this bug and the other was marked as a duplicate of bug #1663453. My two bugs were bug #1678877 and bug #1679233.

Apport retracing service (apport)
tags: added: artful
Brian Murray (brian-murray)
tags: added: fls-aa-incoming
Norbert (nrbrtx)
tags: removed: artful yakkety
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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