systemd-logind crashed with SIGSEGV in strlen()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Really not sure what caused this crash except that the previous shutdown was unusual.
I've taken to do more use of terminal lately and when I ( sudo shutdown 2 min) last time got a message about "not being able to block"? System login failed three times today and finally booted me over to bug report.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSign
Uname: Linux 4.2.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Sep 11 23:28:39 2015
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-01-29 (225 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 10117
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f12e95876fa <strlen+42>: movdqu (%rax),%xmm12
PC (0x7f12e95876fa) ok
source "(%rax)" (0x561a80000000) not located in a known VMA region (needed readable region)!
destination "%xmm12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
strlen () at ../sysdeps/
__GI___strdup (s=0x561a80000000 <error: Cannot access memory at address 0x561a80000000>) at strdup.c:41
?? ()
?? ()
?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I7KT31AUS
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 STD
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 10117
dmi.product.
dmi.sys.vendor: LENOVO
This crash has the same stack trace characteristics as bug #1495178. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.