systemd crashed with SIGABRT
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm Using Ubuntu GNOME 16.04. was trying to reboot the system but it wasn't responding, and told me time out!
I tried 'systemctl status halt.target', but told me that systemd wasn't working or something like that.
not the first time to happen, and each time I have to shut down using power button!
any idea what's going on?!
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: systemd 229-2ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 20 04:37:05 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2016-03-18 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1)
MachineType: Hewlett-Packard HP ProBook 4540s
ProcCmdline: /lib/systemd/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
SystemdDelta:
[EXTENDED] /etc/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
3 overridden configuration files found.
Title: systemd crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/15/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IRR Ver. F.60
dmi.board.name: 17F6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 58.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP ProBook 4540s
dmi.product.
dmi.sys.vendor: Hewlett-Packard

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