sudo crashed with SIGABRT in kill()

Bug #1787585 reported by mlopesmartins
This bug report is a duplicate of:  Bug #1565332: sudo crashed with SIGABRT in kill(). Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
New
Undecided
Unassigned

Bug Description

Sudo crashed

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.5
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug 14 13:01:16 2018
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2017-10-27 (293 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: sudo umake android
Signal: 6
SourcePackage: sudo
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 __libc_start_main (main=0x55bb059b7a50, argc=3, argv=0x7fff58574bb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff58574ba8) at ../csu/libc-start.c:291
 ?? ()
Title: sudo crashed with SIGABRT in kill()
UpgradeStatus: Upgraded to xenial on 2017-10-27 (293 days ago)
UserGroups:

VisudoCheck:
 /etc/sudoers: análise OK
 /etc/sudoers.d/README: análise OK

Revision history for this message
mlopesmartins (martins-marcoslopes) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1565332, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.