Bug 1750557

Summary: lightdm-gtk sometimes crashes on first login attempt
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: lightdm-gtkAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: christoph.wickert, dan, gp, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: armhfp   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 18:27:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
lightdm_backtrace none

Description Paul Whalen 2019-09-09 21:18:43 UTC
Description of problem:
Attempting to login to the ARM Xfce spin sometimes fails on the first login attempt, requiring password entry twice. 

Version-Release number of selected component (if applicable):
lightdm-1.30.0-2.fc31

How reproducible:
Roughly 50/50

Steps to Reproduce:
1. Boot Xfce spin, completing initial-setup then reboot
2. Enter password in the supplied field, enter, login dialog reappears.
3. Second login attempt works 100%


Additional info:
           PID: 1012 (lightdm-gtk-gre)
           UID: 989 (lightdm)
           GID: 985 (lightdm)
        Signal: 11 (SEGV)
     Timestamp: Mon 2019-09-09 17:01:23 EDT (11min ago)
  Command Line: /usr/sbin/lightdm-gtk-greeter
    Executable: /usr/sbin/lightdm-gtk-greeter
 Control Group: /user.slice/user-989.slice/session-c1.scope
          Unit: session-c1.scope
         Slice: user-989.slice
       Session: c1
     Owner UID: 989 (lightdm)
       Boot ID: a5cce266acaf451a87c10eec4734b67a
    Machine ID: 69d3916002784cefaaf940ea46fea120
      Hostname: rpi3-1
       Storage: /var/lib/systemd/coredump/core.lightdm-gtk-gre.989.a5cce266acaf451a87c10eec4734b67a.1012.1568062883000000000000.lz4
       Message: Process 1012 (lightdm-gtk-gre) of user 989 dumped core.
                
                Stack trace of thread 1012:
                #0  0x00000000b67579c4 cairo_surface_get_type (libcairo.so.2)

Comment 1 Paul Whalen 2019-09-09 21:39:17 UTC
Created attachment 1613349 [details]
lightdm_backtrace

Comment 2 Ben Cotton 2020-11-03 15:33:53 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-11-24 18:27:36 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Dan HorĂ¡k 2022-06-09 17:53:54 UTC
I think we have a new occurrence of this problem in bug 2095441