systemd-logind crashed with SIGSEGV in strlen()

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

Bug Description

Recently configured Kerberos / pam_sssd for authentication (configured to use either kerberos or local database for authentication because it's a laptop and is sometimes away from its home network).

Got this login after installing the host keytab and restarting the system.

Running Ubuntu 15.10 Wily Werewolf (last updated 2-3 days ago).

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
Date: Wed Oct 7 10:14:29 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-09-12 (25 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
MachineType: Acer Aspire V5-132
ProcCmdline: /lib/systemd/systemd-logind
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic.efi.signed root=UUID=0b14d4b3-4f10-43f7-a110-b93419cc7104 ro noprompt persistent quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f44fa1c16fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f44fa1c16fa) ok
 source "(%rax)" (0x55e5c6000000) 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=0x55e5c6000000 <error: Cannot access memory at address 0x55e5c6000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/04/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.05
dmi.board.name: Angel_CY
dmi.board.vendor: Acer
dmi.board.version: V2.05
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.05
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.05:bd09/04/2013:svnAcer:pnAspireV5-132:pvrV2.05:rvnAcer:rnAngel_CY:rvrV2.05:cvnAcer:ct9:cvrV2.05:
dmi.product.name: Aspire V5-132
dmi.product.version: V2.05
dmi.sys.vendor: Acer

Revision history for this message
Notavi (adam-luchjenbroers-gmail) 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 #1502626, 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.