gnome-session segfault during login

Downgrading to version 2.22.1.1-0ubuntu2 (from 8.04) enabled me to login as a workaround

Matt - I know this might sound like a silly question, but is Apport enabled? You can check by typing the following in a terminal:

cat /proc/sys/kernel/core_pattern

...it should look something like "|apport %p %s %c". If it reads "core", then Apport is not catching any crashes.

Thanks

On Tue, Aug 12, 2008 at 11:58:44AM -0000, Chris Coulson wrote:
> Matt - I know this might sound like a silly question, but is Apport
> enabled? You can check by typing the following in a terminal:
>
> cat /proc/sys/kernel/core_pattern
>
> ...it should look something like "|apport %p %s %c". If it reads "core",
> then Apport is not catching any crashes.

It is enabled, and has caught several other crashes around the same time, so
this is a bit of a mystery (which I'll take up in another bug report if I
can isolate the cause).

--
 - mdz

#0 0xb77c2263 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb778e826 in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7844f3a in __vasprintf_chk () from /lib/tls/i686/cmov/libc.so.6
#3 0xb79325df in IA__g_vasprintf (string=0xbf9c8194,
    format=0x8067098 "Unable to parse command '%s': %s", args=0xbf9c864c "")
    at /usr/include/bits/stdio2.h:199
#4 0xb791e466 in IA__g_strdup_vprintf (
    format=0x8067098 "Unable to parse command '%s': %s", args=0xbf9c864c "")
    at /build/buildd/glib2.0-2.17.6/glib/gstrfuncs.c:218
#5 0xb79056ba in IA__g_logv (
    log_domain=0x8cc0e80 "�a\212��a\212�re/locale/en_US.UTF-8/LC_MESSAGES/glib208", log_level=G_LOG_LEVEL_WARNING,
    format=0x8067098 "Unable to parse command '%s': %s", args1=0xbf9c864c "")
    at /build/buildd/glib2.0-2.17.6/glib/gmessages.c:472
#6 0xb7905a86 in IA__g_log (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING,
    format=0x8067098 "Unable to parse command '%s': %s")
    at /build/buildd/glib2.0-2.17.6/glib/gmessages.c:517
#7 0x08051546 in gsm_autostart_app_start (app=0x8c95000, error=0xbf9c86cc)
    at gsm-autostart-app.c:744
#8 0x0805f106 in _start_app (id=0x8c98058 "/org/gnome/SessionManager/App17",
    app=0x8c95000, manager=0x8c74c68) at gsm-manager.c:440
#9 0xb78ed29d in IA__g_hash_table_find (hash_table=0x8c60390,
    predicate=0x805f040 <_start_app>, user_data=0x8c74c68)
    at /build/buildd/glib2.0-2.17.6/glib/ghash.c:1118
#10 0x0805eb67 in start_phase (manager=0x8c74c68) at gsm-manager.c:471
#11 0xb7991b54 in IA__g_cclosure_marshal_VOID__VOID (closure=0x8cb6a40,
    return_value=0x0, n_param_values=1, param_values=0x8c9cc78,
    invocation_hint=0xbf9c88cc, marshal_data=0x805ef70)
    at /build/buildd/glib2.0-2.17.6/gobject/gmarshal.c:77
#12 0xb7983c73 in IA__g_closure_invoke (closure=0x8cb6a40, return_value=0x0,
    n_param_values=1, param_values=0x8c9cc78, invocation_hint=0xbf9c88cc)
    at /build/buildd/glib2.0-2.17.6/gobject/gclosure.c:767
#13 0xb799b4b5 in signal_emit_unlocked_R (node=0x8c89fe0, detail=0,
    instance=0x8c79e10, emission_return=0x0, instance_and_params=0x8c9cc78)
    at /build/buildd/glib2.0-2.17.6/gobject/gsignal.c:3244
#14 0xb799cbd6 in IA__g_signal_emit_valist (instance=0x8c79e10, signal_id=27,
    detail=0,
    var_args=0xbf9c8a6c "���\b�q�\b���\b�\212\234��'\006\b\020\236�\b�t\006\b\220\005\006\bhL�\b") at /build/buildd/glib2.0-2.17.6/gobject/gsignal.c:2977
#15 0xb799d086 in IA__g_signal_emit (instance=0x8c79e10, signal_id=27,
    detail=0) at /build/buildd/glib2.0-2.17.6/gobject/gsignal.c:3034
#16 0x0804ff51 in gsm_app_registered (app=0x8c79e10) at gsm-app.c:440
#17 0x080627ee in on_xsmp_client_register_request (client=0x8ca3110,
    id=0xbf9c8e08, manager=0x8c74c68) at gsm-manager.c:1362
#18 0x08056a06 in gsm_marshal_BOOLEAN__POINTER (closure=0x8c97fb8,
    return_value=0xbf9c8c60, n_param_values=2, param_values=0x8cad140,
    invocation_hint=0xbf9c8c4c, marshal_data=0x8062710) at gsm-marshal.c:83
#19 0xb7983c73 in IA__g_closure_invoke (closure=0x8c97fb8,
    return_value=0xbf9c8c60, n_param_values=2, param_values=0x8cad140,
    invocation_hint=0xbf9c8c4c)
    at /build/buildd/glib2.0-2.17.6/gobject/gclosure.c:7...

/etc/xdg/autostart/smart-notifier.desktop seems to trigger the segfault. Attaching it.

Changing "Terminal=False" to "Terminal=false" (lowercase "f") avoids the crash.

The bug and a patch have been sent on http://bugzilla.gnome.org/show_bug.cgi?id=547443

This bug was fixed in the package gnome-session - 2.23.6-0ubuntu2

---------------
gnome-session (2.23.6-0ubuntu2) intrepid; urgency=low

  * debian/patches/80_correct_gerror_use.patch:
    - correctly initialise gerror so using it doesn't lead to a crash
      (lp: #257250)

 -- Sebastien Bacher <email address hidden> Tue, 12 Aug 2008 17:11:39 +0200

reopening this bug as I was hit but it today.

(Just made an upload that fix /etc/xdg/autostart/smart-notifier.desktop)

Is it the same bug? Could you provide a backtrace? I think it probably would have been better to open a new report rather than resurrect an old one.

Setting back to FixReleased as there is no indication that the bug is not fixed.

the issue is fixed in karmic