gdmsetup crashes immediately upon opening

Bug #46075 reported by Daniel Goldsmith
This bug report is a duplicate of:  Bug #42712: gdmsetup segfaults. Edit Remove
16
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

When I select gdmsetup (Login Window from System-->Administration) it crashes immediately (the window appears and then immediately disappears. When run with gdb I get this:

Starting program: /usr/sbin/gdmsetup
[Thread debugging using libthread_db enabled]
[New Thread -1220081984 (LWP 14465)]
[New Thread -1227646032 (LWP 14468)]
[New Thread -1259082832 (LWP 14479)]
[New Thread -1267872848 (LWP 14480)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220081984 (LWP 14465)]
0xb77c6719 in g_str_hash () from /usr/lib/libglib-2.0.so.0

I tried reinstalling libglib, but it still crashed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu and gdm do you use? Could you get a backtrace with libglib2.0-0-dbg installed by typing "thread apply all bt" on the gdb prompt?

Changed in gdm:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Daniel Goldsmith (goldsmitharmy) wrote :

Sorry, Ubuntu Dapper 6.06 and gdm 2.14.6-0ubuntu1.

With libglib2.0.0-dbg and thread apply all bt:

(gdb) thread apply all bt
(gdb) run
Starting program: /usr/sbin/gdmsetup
[Thread debugging using libthread_db enabled]
[New Thread -1220151616 (LWP 6860)]
[New Thread -1227441232 (LWP 6863)]
[New Thread -1258878032 (LWP 6874)]
[New Thread -1268778064 (LWP 6875)]
[New Thread -1277170768 (LWP 6876)]
[New Thread -1285563472 (LWP 6877)]
[New Thread -1293956176 (LWP 6878)]
[New Thread -1302348880 (LWP 6879)]
[New Thread -1310741584 (LWP 6880)]
[Thread -1258878032 (LWP 6874) exited]
[Thread -1268778064 (LWP 6875) exited]
[Thread -1277170768 (LWP 6876) exited]
[Thread -1293956176 (LWP 6878) exited]
[Thread -1310741584 (LWP 6880) exited]
[Thread -1302348880 (LWP 6879) exited]
[Thread -1285563472 (LWP 6877) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220151616 (LWP 6860)]
IA__g_str_hash (v=0x0) at gstring.c:95
95 gstring.c: No such file or directory.
        in gstring.c

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your effort, you need to type "thread apply all bt" after the crash though, could you try again?

Revision history for this message
Sannie Kwakman (kmantis-deactivatedaccount) wrote :
Download full text (9.6 KiB)

Hi there. I've got the same problem mentioned in the bug report. Here's my output from gdb:

Starting program: /usr/sbin/gdmsetup
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1218324800 (LWP 7983)]
[New Thread -1225892944 (LWP 7986)]
[New Thread -1238119504 (LWP 7997)]
[New Thread -1248203856 (LWP 7998)]
[Thread -1238119504 (LWP 7997) exited]
[Thread -1248203856 (LWP 7998) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1218324800 (LWP 7983)]
IA__g_str_hash (v=0x0) at gstring.c:95
95 gstring.c: Onbekend bestand of map. [edit by poster: this message is in Dutch, which translates to 'Unknown file or folder' or 'no such file or directory']
        in gstring.c
(gdb) thread apply all bt

Thread 2 (Thread -1225892944 (LWP 7986)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb76fe8c4 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb787d7d8 in g_main_context_iterate (context=0x8240a30, block=1, dispatch=1,
    self=0x8240fe8) at gmain.c:2849
#3 0xb787dca8 in IA__g_main_loop_run (loop=0x8226218) at gmain.c:2751
#4 0xb722470e in link_thread_io_context () from /usr/lib/libORBit-2.so.0
#5 0xb78965d2 in g_thread_create_proxy (data=0x8240fe8) at gthread.c:582
#6 0xb71cd341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb77084ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1218324800 (LWP 7983)):
#0 IA__g_str_hash (v=0x0) at gstring.c:95
#1 0xb786f73f in IA__g_hash_table_lookup (hash_table=0x8640d40, key=0x0)
    at ghash.c:242
#2 0x080639d0 in ve_config_get ()
#3 0x08050392 in gdm_setup_config_set_string ()
#4 0x08054f89 in gdm_setup_config_set_string ()
#5 0xb78f7423 in IA__g_cclosure_marshal_VOID__VOID (closure=0x8448e70,
    return_value=0x0, n_param_values=1, param_values=0xbffb15dc,
    invocation_hint=0xbffb14cc, marshal_data=0xb7919768) at gmarshal.c:77
#6 0xb78eb79f in IA__g_closure_invoke (closure=0x8448e70, return_value=0x0,
    n_param_values=0, param_values=0x0, invocation_hint=0x0) at gclosure.c:490
#7 0xb78fa2ea in signal_emit_unlocked_R (node=0x8210bb0, detail=0,
    instance=0x82be800, emission_return=0x0, instance_and_params=0xbffb15dc)
    at gsignal.c:2438
#8 0xb78fbb19 in IA__g_signal_emit_valist (instance=0x82be800, signal_id=146,
    detail=0, var_args=<value optimized out>) at gsignal.c:2197
#9 0xb78ff030 in IA__g_signal_emit_by_name (instance=0x82be800,
    detailed_signal=0xb7ed19e8 "selection-change...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

according to the backtrace that's a duplicate of bug #42712. Did you try xgl or played with you gdm.conf and gdm.conf-custom?

Changed in gdm:
status: Needs Info → Rejected
Revision history for this message
Sannie Kwakman (kmantis-deactivatedaccount) wrote :

Yes I did. After reading the comments on bug #42712, creating a new empty /etc/gdm/gdm.conf-custom and restarting gdm fixed the problems.

As mentioned in bug #42712, the advice of removing gdm.conf-custom came from a forum post on ubuntu-forums.org (http://www.ubuntuforums.org/showthread.php?t=131267). I've notified the poster, so that the post can be edited to prevent this from happening to other users.

Thanks for the help!

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.