Bug 1282278 - freeze after "New Login", crash in gnome-session-check-accelerated
freeze after "New Login", crash in gnome-session-check-accelerated
Product: Fedora
Classification: Fedora
Component: gnome-session (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-15 20:44 EST by Andrew Schultz
Modified: 2016-12-20 10:57 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 10:57:30 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Schultz 2015-11-15 20:44:14 EST
Description of problem:
If I lock the screen with xscreensaver and choose to "New Login" to login as a different user, the display freezes.  X launches and somewhere along the way, gnome-session-check-accelerated runs and crashes.

Stack looks like:
 XInternAtom (IntAtom.c:174)
 gdk_x11_atom_to_xatom_for_display (gdkproperty-x11.c:115)
 main (gnome-session-check-accelerated.c:126)

debugging in gdb indicates the crash is in IntAtom.c, _XInternAtoms:

74    if (!(atoms = dpy->atoms)) {
75        dpy->atoms = atoms = Xcalloc(1, sizeof(AtomTable));
76        dpy->free_funcs->atoms = _XFreeAtomTable;
77    }

dpy->free_funcs is 0x1

running gnome-session-check-accelerated in an already-running session works fine (free_funcs points to actual memory).

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1. lock screen with xscreensaver
2. Click "New Login"

Actual results:

Expected results:
A new login!

Additional info:
This all worked fine under Fedora 22.
If I replace gnome-session-check-accelerated with a shell script that "exit 0", then the whole "New Login" process works fine.
Comment 1 Fedora End Of Life 2016-11-24 08:28:15 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 2 Fedora End Of Life 2016-12-20 10:57:30 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

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

Note You need to log in before you can comment on or make changes to this bug.