systemd crashed with SIGABRT
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
No idea
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: systemd 229-2ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Mar 7 21:17:42 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-12-29 (69 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 6468AF4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
SystemdDelta:
[EXTENDED] /etc/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
3 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
UpgradeStatus: Upgraded to xenial on 2016-02-24 (11 days ago)
UserGroups: adm cdrom dip fax lpadmin plugdev sambashare sudo vboxusers www-data
dmi.bios.date: 02/27/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETD0WW (2.30 )
dmi.board.name: 6468AF4
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 6468AF4
dmi.product.
dmi.sys.vendor: LENOVO

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.