systemd-logind crashed with SIGSEGV in strlen()

Bug #1495130 reported by David Oxland
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Sep 11 23:28:39 2015
ExecutablePath: /lib/systemd/systemd-logind
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/systemd-logind
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
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/x86_64/strlen.S:106
 __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:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
dmi.product.name: 10117
dmi.product.version: Lenovo H535
dmi.sys.vendor: LENOVO

Revision history for this message
David Oxland (doxland) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

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.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.