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

Bug #637563 reported by Sergey
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

constantly hangs

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.31.91-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Sep 13 23:52:28 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ru_UA
 LANG=ru_UA.utf8
SegvAnalysis:
 Segfault happened at: 0x4ae99e <_IO_default_xsputn+14>: call 0x45ab1f
 PC (0x004ae99e) ok
 source "0x45ab1f" (0x0045ab1f) ok
 destination "(%esp)" (0xbf17ffec) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_return_if_fail_warning () from /lib/libglib-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
 ?? () from /usr/lib/gnome-settings-daemon-2.0/libubuntuone.so
Title: gnome-settings-daemon crashed with SIGSEGV in g_return_if_fail_warning()
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare vboxusers video www-data

Revision history for this message
Sergey (rozmetanyk) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #633167, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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