Public bug reported:

Crash occured on boot

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 17 21:41:53 2018
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2017-10-24 (144 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 autologin-user=skellat
 autologin-user-timeout=0
ProcCmdline: lightdm --session-child 12 15
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>:   mov    0x8(%rax),%r15
 PC (0x7f4cc21acb3a) ok
 source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region (needed 
readable region)!
 destination "%r15" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 _dl_fini () at dl-fini.c:134
 __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
 __GI_exit (status=<optimized out>) at exit.c:139
 ()
 <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
Title: lightdm crashed with SIGSEGV in _dl_fini()
UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago)
UserGroups:

** Affects: lightdm (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756632

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to