systemd-logind crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: systemd 229-2ubuntu1 [modified: usr/share/
ProcVersionSign
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 4 08:00:53 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-04-30 (309 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fe70d4edd9e <__strcmp_
PC (0x7fe70d4edd9e) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
SystemImageInfo: Error: command ['system-
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /etc/systemd/
[EXTENDED] /lib/systemd/
3 overridden configuration files found.
Title: systemd-logind crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.
dmi.board.name: 429149G
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: 429149G
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 #1553040, 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.