sudo crashed with SIGABRT in kill()

Bug #1579947 reported by William Geiger
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

sorry don't know what happened with this. Apport showed up on reboot. Have been doing some heavy playing with this system so it just may be a mucked up config issue.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: sudo 1.8.16-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
Uname: Linux 4.4.0-22-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu3
Architecture: amd64
Date: Sat May 7 23:59:57 2016
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2016-03-04 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229)
ProcCmdline: sudo /usr/bin/policytool -file /home/username/Domination_install_1.1.1.6.jarr
Signal: 6
SourcePackage: sudo
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 __libc_start_main (main=0x563468acea20, argc=4, argv=0x7ffe0d188cb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe0d188ca8) at ../csu/libc-start.c:291
 ?? ()
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
William Geiger (whgiii-q) wrote :
Revision history for this message
William Geiger (whgiii-q) wrote :

Just re-read the apport. Java 9 is NOT working on my system even after doing a purge and fresh install. Dropped back to Openjdk-8 and everything is working fine. I am not a big Java user but I do have a couple of apps that use it. If there is anything further to do to test things out let me know but for now I am back to running 8 on my system as nothing will run under 9.

hope this helps.

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.