Ubuntu
gnome-settings-daemon package

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

Bug #660063 reported by Matt Zimmerman
This bug report is a duplicate of:  Bug #658777: Invalid reads in keyboard plugin. Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

gnome-settings-daemon has crashed a few times recently on this system. I notice it when I resume from suspend, because the gnome-screensaver dialog is not themed properly, but I'm not sure exactly when the crash happens.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Oct 13 17:05:33 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x7fd0f33ccc50 <__libc_free+64>: mov (%rax),%rbx
 PC (0x7fd0f33ccc50) ok
 source "(%rax)" (0x7fd0f4000000) in non-readable VMA region: 0x7fd0f3e1d000-0x7fd0f401c000 ---p /lib/libpthread-2.12.1.so
 destination "%rbx" ok
SegvReason: reading VMA /lib/libpthread-2.12.1.so
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 __libc_free (mem=0x7fd0f46b12e3) 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

Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0x7fd0f46b12e3)
 popup_menu_set_group (item=<value optimized out>,
 apply_xkb_settings () at gsd-keyboard-xkb.c:551
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matt Zimmerman (mdz)
visibility: private → public
Revision history for this message
Rajeev (rajeeja) wrote :

I have a program that uses some old libraries, this worked on 10.04, the problem seems to be with glibc / libstdc++...

The error message that my program gives:

Program received signal SIGSEGV, Segmentation fault.
0x0019ce39 in __libc_free (mem=0x80f4e20) at malloc.c:3724
 in malloc.c

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 660063] Re: gnome-settings-daemon crashed with SIGSEGV in __libc_free()

On Wed, Oct 20, 2010 at 10:00:01PM -0000, Rajeev wrote:
> I have a program that uses some old libraries, this worked on 10.04, the
> problem seems to be with glibc / libstdc++...
>
> The error message that my program gives:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0019ce39 in __libc_free (mem=0x80f4e20) at malloc.c:3724
> in malloc.c

You have a different problem than I am reporting, and it's most likely a bug
in that program.

--
 - mdz

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

Could be the same as bug #658777 which was fixed in 0ubuntu3, could you try with that version?

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

the stacktrace matches the valgrind log from the other bug #658777, I'm marking it as duplicate, feel free to reopen if you disagree

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.