gnome-settings-daemon crashed with SIGSEGV in __libc_free()

[Matt Zimmerman]

Binary package hint: gnome-settings-daemon

This is a second attempt to report the problem I originally reported in bug 672124. The retracer wasn't able to give a complete stack trace on that one, so I'm trying again as Martin asked.

This might be related to bug 658777, but I can't tell until it's retraced.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.32.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Wed Nov 24 10:29:10 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f884edcdc50 <__libc_free+64>: mov (%rax),%rbx
 PC (0x7f884edcdc50) ok
 source "(%rax)" (0x7f8850000000) in non-readable VMA region: 0x7f884fe8b000-0x7f885008a000 ---p /usr/lib/libgmodule-2.0.so.0.2600.1
 destination "%rbx" ok
SegvReason: reading VMA /usr/lib/libgmodule-2.0.so.0.2600.1
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 __libc_free (mem=0x7f88500b22e3) at malloc.c:3724
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libkeyboard.so
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libkeyboard.so
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in __libc_free()
UserGroups: adm admin audio cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 *__GI___libc_free (mem=0x7f88500b22e3)
 popup_menu_set_group (item=<value optimized out>,
 apply_xkb_settings () at gsd-keyboard-xkb.c:546
 g_closure_invoke (closure=0x22616a0,
 signal_emit_unlocked_R (node=0x224c700,

[Matt Zimmerman (mdz)]

The retrace here doesn't seem any better, and it just happened again, so I went ahead and filed bug 685785 with a similar crash.

[Matt Zimmerman (mdz)]

I got a much better retrace over on bug 685785, so I've marked this one as a duplicate.