systemd-logind crashed with SIGSEGV in strlen()

Bug #1505637 reported by Andi Chandler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Lots of problems caused after update from 15.04 to 15.10.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
Uname: Linux 4.2.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 8 17:39:35 2015
ExecutablePath: /lib/systemd/systemd-logind
ExecutableTimestamp: 1444057439
InstallationDate: Installed on 2014-08-26 (412 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140826)
MachineType: Dell Inc. OptiPlex 7010
ProcCmdline: /lib/systemd/systemd-logind
ProcCwd: /
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f8f7a9736fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f8f7a9736fa) ok
 source "(%rax)" (0x55e5ee000000) 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=0x55e5ee000000 <error: Cannot access memory at address 0x55e5ee000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
SystemdDelta:
 [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

 3 overridden configuration files found.
Title: systemd-logind crashed with SIGSEGV in strlen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0WR7PY
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/25/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Andi Chandler (bing) wrote :
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.