systemd-logind crashed with SIGSEGV in strlen()
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
ProcVersionSign
Uname: Linux 4.2.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 8 17:39:35 2015
ExecutablePath: /lib/systemd/
ExecutableTimes
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/
ProcCwd: /
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
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/
__GI___strdup (s=0x55e5ee000000 <error: Cannot access memory at address 0x55e5ee000000>) at strdup.c:41
?? ()
?? ()
?? ()
SystemdDelta:
[EXTENDED] /etc/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
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.
dmi.product.name: OptiPlex 7010
dmi.product.
dmi.sys.vendor: Dell Inc.
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.