systemd crashed with SIGABRT in __GI_raise()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The prompt for a bug report occurred when the system was idle for a few minutes after a period of activities. I don't know why.
The system is still running, and I see no problems.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: systemd 229-3ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.370
Date: Wed Mar 30 19:04:38 2016
ExecutablePath: /lib/systemd/
LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160330)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcCmdline: /sbin/init 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] /lib/systemd/
[EXTENDED] /lib/systemd/
2 overridden configuration files found.
SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedeskto
Title: systemd crashed with SIGABRT in __GI_raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.
dmi.sys.vendor: TOSHIBA

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.