systemd-logind crashed with SIGSEGV in strlen()

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

Bug Description

this crash occurred when i launched

sudo shutdown -h +60

from the terminal

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
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Thu Sep 17 22:59:40 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-09-04 (13 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150903)
MachineType: TOSHIBA SATELLITE C855-2J5
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic.efi.signed root=UUID=5e7734dc-38f8-47bc-b5ce-6bee21ac47a1 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd14a4546fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7fd14a4546fa) ok
 source "(%rax)" (0x55f1c1000000) 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=0x55f1c1000000 <error: Cannot access memory at address 0x55f1c1000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/01/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC855-2J5:pvrPSCBYE-04F00RIT:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE C855-2J5
dmi.product.version: PSCBYE-04F00RIT
dmi.sys.vendor: TOSHIBA

Revision history for this message
Enrico (enricobe) 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.