[lucid] gdm crashes at start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gdm
After today's update, gdm crashes at startup. Didn't happen with lucid upated 2 days back. With libglib2.0-0-dbg package installed, gdm spits out following backtrace (started manually, but the same happens if spawned from upstart or run from inside gdb); note that at #9 g_idle_dispatch receives dispatch=0, which is pointer to function that is called, obviously resulting in crash. Fell free to ask for more information.
gdm[2531]: ******************* START *******
gdm[2531]: [Thread debugging using libthread_db enabled]
gdm[2531]: 0x0053c422 in __kernel_vsyscall ()
gdm[2531]: #0 0x0053c422 in __kernel_vsyscall ()
gdm[2531]: #1 0x0025ad23 in __waitpid_nocancel () from /lib/tls/
gdm[2531]: #2 0x08066b19 in ?? ()
gdm[2531]: #3 0x08066c11 in ?? ()
gdm[2531]: #4 <signal handler called>
gdm[2531]: #5 0x0045c043 in strchr () from /lib/tls/
gdm[2531]: #6 0x08059472 in ?? ()
gdm[2531]: #7 0x0805bda2 in ?? ()
gdm[2531]: #8 0x0805c253 in ?? ()
gdm[2531]: #9 0x00369251 in g_idle_dispatch (source=0x90c4880, callback=0, user_data=
gdm[2531]: at /build/
gdm[2531]: #10 0x0036afd8 in g_main_dispatch (context=0x90b0b98) at /build/
gdm[2531]: #11 IA__g_main_
gdm[2531]: #12 0x0036e880 in g_main_
gdm[2531]: at /build/
gdm[2531]: #13 0x0036ecef in IA__g_main_loop_run (loop=0x90c7170) at /build/
gdm[2531]: #14 0x0804eb08 in ?? ()
gdm[2531]: #15 0x003ffbd6 in __libc_start_main () from /lib/tls/
gdm[2531]: #16 0x0804dd81 in ?? ()
gdm[2531]:
gdm[2531]: Thread 1 (Thread 0xb77b4720 (LWP 2524)):
gdm[2531]: #0 0x0053c422 in __kernel_vsyscall ()
gdm[2531]: No symbol table info available.
gdm[2531]: #1 0x0025ad23 in __waitpid_nocancel () from /lib/tls/
gdm[2531]: No symbol table info available.
gdm[2531]: #2 0x08066b19 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #3 0x08066c11 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #4 <signal handler called>
gdm[2531]: No symbol table info available.
gdm[2531]: #5 0x0045c043 in strchr () from /lib/tls/
gdm[2531]: No symbol table info available.
gdm[2531]: #6 0x08059472 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #7 0x0805bda2 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #8 0x0805c253 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #9 0x00369251 in g_idle_dispatch (source=0x90c4880, callback=0, user_data=
gdm[2531]: at /build/
gdm[2531]: No locals.
gdm[2531]: #10 0x0036afd8 in g_main_dispatch (context=0x90b0b98) at /build/
gdm[2531]: dispatch = 0x369230 <g_idle_dispatch>
gdm[2531]: user_data = 0x90b7430
gdm[2531]: callback = 0x805c240
gdm[2531]: cb_funcs = 0x3e831c
gdm[2531]: cb_data = 0x90c43e8
gdm[2531]: next = 0x0}
gdm[2531]: source = 0x52ebd4
gdm[2531]: current = 0x90c9208
gdm[2531]:
gdm[2531]: #11 IA__g_main_
gdm[2531]: No locals.
gdm[2531]: #12 0x0036e880 in g_main_
gdm[2531]: at /build/
gdm[2531]:
gdm[2531]:
gdm[2531]:
gdm[2531]: nfds = <value optimized out>
gdm[2531]: allocated_nfds = <value optimized out>
gdm[2531]: fds = <value optimized out>
gdm[2531]:
gdm[2531]: #13 0x0036ecef in IA__g_main_loop_run (loop=0x90c7170) at /build/
gdm[2531]: self = 0x90acad0
gdm[2531]:
gdm[2531]: #14 0x0804eb08 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: #15 0x003ffbd6 in __libc_start_main () from /lib/tls/
gdm[2531]: No symbol table info available.
gdm[2531]: #16 0x0804dd81 in ?? ()
gdm[2531]: No symbol table info available.
gdm[2531]: A debugging session is active.
gdm[2531]:
gdm[2531]: Inferior 1 [process 2524] will be detached.
gdm[2531]:
gdm[2531]: Quit anyway? (y or n) [answered Y; input not from terminal]
gdm[2531]: ******************* END *******
ProblemType: Bug
Architecture: i386
Date: Thu Jan 7 13:50:01 2010
DistroRelease: Ubuntu 10.04
Package: gdm 2.29.1-0ubuntu9
ProcEnviron:
PATH=(custom, no user)
LANG=cs_CZ.UTF-8
SHELL=/bin/zsh
ProcVersionSign
SourcePackage: gdm
Tags: lucid
Uname: Linux 2.6.32-9-generic i686
thank you for your bug report, it's probably due to bug #504198