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

Bug #629306 reported by Yura Tolstik
48
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Status tracked in Trunk
Stable-1-4
Fix Released
High
dobey
Trunk
Fix Released
High
dobey
ubuntuone-client (Ubuntu)
Fix Released
High
dobey
Maverick
Fix Released
High
dobey
Natty
Fix Released
High
dobey

Bug Description

Binary package hint: gnome-settings-daemon

ubutnu 10.10 with all updates

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-settings-daemon 2.30.2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Thu Sep 2 16:52:26 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x54599e <_IO_default_xsputn+14>: call 0x4f1b1f
 PC (0x0054599e) ok
 source "0x4f1b1f" (0x004f1b1f) ok
 destination "(%esp)" (0xbf1d3ffc) 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
 ?? ()
 ?? ()
 ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV in g_return_if_fail_warning()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Related branches

Revision history for this message
Yura Tolstik (yltsrc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_default_xsputn (f=0xbf1d45ec, data=0x351426, n=1) at genops.c:452
 _IO_vfprintf_internal (s=0xbf1d45ec,
 *__GI___vasprintf_chk (result_ptr=0xbf1d46fc, flags=1,
 ?? () from /lib/libglib-2.0.so.0
 g_string_overwrite_len () from /lib/libglib-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-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash is in libubuntuone-client, reassigning

visibility: private → public
affects: gnome-settings-daemon (Ubuntu) → ubuntuone-client (Ubuntu)
dobey (dobey)
Changed in ubuntuone-client (Ubuntu Maverick):
assignee: nobody → Rodney Dawes (dobey)
importance: Undecided → High
status: New → In Progress
Changed in ubuntuone-client (Ubuntu Natty):
assignee: nobody → Rodney Dawes (dobey)
importance: Medium → High
status: New → In Progress
dobey (dobey)
Changed in ubuntuone-client (Ubuntu Maverick):
status: In Progress → Fix Committed
dobey (dobey)
Changed in ubuntuone-client (Ubuntu Natty):
status: In Progress → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted ubuntuone-client into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntuone-client - 1.4.6-0ubuntu3

---------------
ubuntuone-client (1.4.6-0ubuntu3) maverick-proposed; urgency=low

  * 02_gsd-plugin-fixes.patch:
    - Fix crash looking up NULL string in hash table (LP: #744383)
    - Chain the dispose event up properly [Chris Coulson] (LP: #629306)
 -- Rodney Dawes <email address hidden> Tue, 05 Apr 2011 17:54:37 -0400

Changed in ubuntuone-client (Ubuntu Maverick):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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