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

[mehor]

Binary package hint: gnome-settings-daemon

Since a similar bug was reported as fixed for previous versions of Ubuntu, I'm reporting it as a new bug.

Gnome-settings-daemon has a habit to crash not only at startup/login, as noted in bug #521766, but also randomly, usually when I close an application. After the crash theme is naturally messed up and, to be fully restored, it is required that not only gnome-settings-daemon be restarted, but Nautilus too.

Note: I didn't upgrade from 9.10, but did a fresh install of 10.04.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-settings-daemon 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sat Jun 19 23:12:12 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: gnome-settings-daemon
ProcEnviron:
 LC_TIME=custom.UTF-8
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f14c2763ffb: cmpq $0x0,0x8(%r12)
 PC (0x7f14c2763ffb) ok
 source "$0x0" ok
 destination "0x8(%r12)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 g_main_context_dispatch ()
Title: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 g_main_context_dispatch ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libtiff4: installed version 3.9.2-2, latest version: 3.9.2-2ubuntu0.3
libcups2: installed version 1.4.3-1ubuntu1, latest version: 1.4.3-1ubuntu1.2
libcairo2: installed version 1.9.6-6~mrw4, latest version: 1.8.10-2ubuntu1
libjson-glib-1.0-0: installed version 0.10.2-2ubuntu1~ppa0, latest version: 0.7.6-0ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[mehor (mehor)]

So, after any update a bug simply is marked as invalid? How any bug should be solved then?