gsettings crashed with SIGSEGV in g_settings_schema_source_ref()

Bug #1059196 reported by joosteto
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)

Bug Description

Got this error while in SystemSettings/OnlineAccounts.
This may be the same as #919489, but that must have been for 12.04, while I've just installed beta2 for 12.10.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libglib2.0-bin 2.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
CheckboxSubmission: 42e6aa71273cb2b457f9be6196c8835b
CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b
Date: Sun Sep 30 20:15:04 2012
ExecutablePath: /usr/bin/gsettings
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gsettings get org.gnome.system.proxy mode
 PATH=(custom, no user)
 Segfault happened at: 0xb751e044 <g_settings_schema_source_ref+4>: lock addl $0x1,0x8(%eax)
 PC (0xb751e044) ok
 source "$0x1" ok
 destination "0x8(%eax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: glib2.0
 g_settings_schema_source_ref () from /usr/lib/i386-linux-gnu/
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/
 ?? ()
Title: gsettings crashed with SIGSEGV in g_settings_schema_source_ref()
UpgradeStatus: Upgraded to quantal on 2012-09-30 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
joosteto (joosteto) 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 this software better. This particular crash has already been reported and is a duplicate of bug #919489, 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