lightdm crashed with SIGSEGV

Bug #1681616 reported by Rogério Theodoro de Brito
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just got this segfault after pressing Ctrl-Alt-F1 and switching to single user mode with "init 1".

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: lightdm 1.22.0-0ubuntu2
Uname: Linux 4.11.0-041100rc5-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
Date: Mon Apr 10 22:25:34 2017
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2015-11-23 (504 days ago)
InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 autologin-user=teste
 autologin-user-timeout=0
ProcCmdline: lightdm --session-child 13 16
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fbee2958f29: mov 0x8(%rax),%r12
 PC (0x7fbee2958f29) ok
 source "0x8(%rax)" (0x7fbee2b42a40) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
Title: lightdm crashed with SIGSEGV
UpgradeStatus: Upgraded to zesty on 2017-03-25 (16 days ago)
UserGroups:

upstart.lightdm.override: manual

Revision history for this message
Rogério Theodoro de Brito (rbrito) 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 #1675141, 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.