systemd crashed with SIGABRT in __GI_raise()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
THE SYSTEM GIVE ME THIS ERROR WHEN START IT
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: systemd 229-3ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Fri Mar 25 10:27:47 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-03-28 (363 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
Lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 13d3:5710 IMC Networks UVC VGA Webcam
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. U31SD
ProcCmdline: /sbin/init allow-discards splash
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__GI_raise (sig=sig@entry=6) at ../sysdeps/
__GI_abort () at abort.c:89
?? ()
?? ()
?? ()
SystemdDelta:
[EXTENDED] /etc/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
3 overridden configuration files found.
Title: systemd crashed with SIGABRT in __GI_raise()
UpgradeStatus: Upgraded to xenial on 2016-03-12 (14 days ago)
UserGroups:
dmi.bios.date: 03/07/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U31SD.202
dmi.board.
dmi.board.name: U31SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: U31SD
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.

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 #1546886, 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.