Ubuntu
gnome-settings-daemon package

gnome-settings-daemon crashed with SIGSEGV

Bug #725972 reported by Johannes Rohr on 2011-02-27

This bug report is a duplicate of: Bug #554280: gnome-settings-daemon crashed with SIGSEGV in g_str_hash(). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-settings-daemon (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

occurs every time on login, on a virtual machine within virtualbox

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-settings-daemon 2.32.1-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Sun Feb 27 12:18:30 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/false
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f7ac20acc10: movsbl (%rdi),%eax
PC (0x7f7ac20acc10) ok
source "(%rdi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV
UserGroups:

Tags:

Revision history for this message

Johannes Rohr (jorohr) wrote on 2011-02-27:

#1

Dependencies.txt Edit (5.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (603 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (43.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (762 bytes, text/plain; charset="utf-8")
Registers.txt Edit (674 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (4.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-28:

#2

StacktraceTop:
icon_name_hash (key=0x30) at /build/buildd/gtk+2.0-2.24.1/gtk/gtkiconcache.c:208
find_image_offset (icon_name=0x30 <Address 0x30 out of bounds>, directory_index=0, cache=<value optimized out>) at /build/buildd/gtk+2.0-2.24.1/gtk/gtkiconcache.c:241
_gtk_icon_cache_get_icon_flags (cache=0x2669fb0, icon_name=<value optimized out>, directory_index=<value optimized out>) at /build/buildd/gtk+2.0-2.24.1/gtk/gtkiconcache.c:283
theme_dir_get_icon_suffix (dir=<value optimized out>, icon_name=<value optimized out>, has_icon_file=0x0) at /build/buildd/gtk+2.0-2.24.1/gtk/gtkicontheme.c:2070
theme_lookup_icon (icon_theme=<value optimized out>, icon_names=0x260f700, size=24, flags=GTK_ICON_LOOKUP_USE_BUILTIN) at /build/buildd/gtk+2.0-2.24.1/gtk/gtkicontheme.c:2133

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-28: Stacktrace.txt

#3

Stacktrace.txt Edit (26.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-28: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (28.2 KiB, text/plain)

Changed in gnome-settings-daemon (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-02-28:

#5

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-settings-daemon (Ubuntu):
status:	New → Invalid
visibility:	private → public

Revision history for this message

Johannes Rohr (jorohr) wrote on 2011-02-28:

#6

Why did you mark this bug invalid? If it is a duplicate, you should mark it a duplicate. At present, this does not seem to be the case.

However another bug, namely bug #725903 is marked a duplicate of /this/ bug.

Changed in gnome-settings-daemon (Ubuntu):
status:	Invalid → New

Revision history for this message

Johannes Rohr (jorohr) wrote on 2011-02-28:

#7

Changed status back, because of what I said in comment #6

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-02-28:

#8

doing closing and reopening on duplicate bugs just because the exact numbers is not a really a win for anybody, it makes the bug list less practical and waste time, you should better search for the duplicate bug...

Revision history for this message

Johannes Rohr (jorohr) wrote on 2011-03-01:

#9

I objected to closing this bug as duplicate because another bug is marked a duplicate of this bug.

Which other bug report refers to the same issue? Is it #714088 which seems to be the only other recent high importance bug reported on gnome-settings-daemon?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-03-01:

#10

bug #554280 seems similar for example

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #554280 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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