gsettings crashed with SIGSEGV in g_settings_schema_source_ref()

Bug #1102062 reported by steinhauser christian
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
New
Undecided
Unassigned

Bug Description

this is my test ubuntu laptop 01
after do-release-upgrade -d

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: libglib2.0-bin 2.35.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic i686
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Sun Jan 20 14:27:41 2013
ExecutablePath: /usr/bin/gsettings
ExecutableTimestamp: 1358419058
InstallationDate: Installed on 2013-01-19 (0 days ago)
InstallationMedia: Ubuntu-Studio 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
MarkForUpload: True
ProcCmdline: gsettings get org.gnome.desktop.interface toolkit-accessibility
ProcCwd: /home/test
ProcEnviron:
 LANGUAGE=fr:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb75585d4 <g_settings_schema_source_ref+4>: lock addl $0x1,0x8(%eax)
 PC (0xb75585d4) 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
StacktraceTop:
 g_settings_schema_source_ref () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: gsettings crashed with SIGSEGV in g_settings_schema_source_ref()
UpgradeStatus: Upgraded to raring on 2013-01-19 (0 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
steinhauser christian (steinhauserchristian) 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.

information type: 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.