lightdm crashed with SIGSEGV in _dl_fini()

Bug #1744450 reported by Kev Bowring
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

just a not noticed when it occurred crash

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Fri Jan 19 21:45:28 2018
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2017-09-02 (140 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
ProcCmdline: lightdm --session-child 12 19
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f85c813f179 <_dl_fini+777>: mov 0x8(%rax),%r12
 PC (0x7f85c813f179) ok
 source "0x8(%rax)" (0x7f85c2c549b8) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 _dl_fini () at dl-fini.c:231
 __run_exit_handlers (status=0, listp=0x7f85c6caf6f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
 __GI_exit (status=<optimised out>) at exit.c:105
 ()
 <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
Title: lightdm crashed with SIGSEGV in _dl_fini()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Kev Bowring (flocculant) 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.