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.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.

  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:

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 
  ProcCmdline: /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- caja
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: sudo
   kill () from /lib/x86_64-linux-gnu/
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to