After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 501010 - gdmsetup crashes when trying to "configure X"
gdmsetup crashes when trying to "configure X"
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.20.x
Other All
: Normal critical
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-02 11:04 UTC by Pacho Ramos
Modified: 2007-12-06 19:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Pacho Ramos 2007-12-02 11:04:56 UTC 
Steps to reproduce:
1.Launch "gdmsetup"
2.Go to "Security" tab
3.Click on "Configure X server"

gdmsetup crashes and gives the following segfault when following these steps:

gdmsetup[27911]: segfault at 00000000 eip 08056909 esp bff474e0 error 4

Stack trace:

+ Trace 180408

  • #0 gdm_load_displays
    at gdmsetup.c line 881
  • #1 xservers_get_displays
    at gdmsetup.c line 988
  • #2 init_servers_combobox
    at gdmsetup.c line 1112
  • #3 xserver_button_clicked
    at gdmsetup.c line 6295
  • #4 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
  • #6 ?? 


Other information:
Comment 1 Brian Cameron 2007-12-03 18:49:34 UTC 
The problem with the crashing is due to the fact that keys is NULL.  I fixed the function so that it just returns rather than crashing.  This is more graceful.

However, I think there are still bugs in this area of the code caused by the cleanup work that Jon McCann did.  Refer to bug #462613.  This is a known bug.

If you find more issues, then please file bugs, although don't file any duplicates of 462613.
Comment 2 Pacho Ramos 2007-12-05 22:14:59 UTC 
Thanks a lot for the fast fix :-O

Thanks :-)
Comment 3 Brian Cameron 2007-12-06 19:32:29 UTC 
*** Bug 502072 has been marked as a duplicate of this bug. ***