gsettings crashed with SIGSEGV in g_settings_schema_source_ref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glib2.0 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
this is my test-ubuntu-
after update
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: libglib2.0-bin 2.35.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 22 15:40:34 2013
ExecutablePath: /usr/bin/gsettings
InstallationDate: Installed on 2013-01-21 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130118)
MarkForUpload: True
ProcCmdline: gsettings get org.gnome.
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=fr_FR.UTF-8
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7ff7b6247e53 <g_settings_
PC (0x7ff7b6247e53) ok
source "$0x1" ok
destination "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: glib2.0
StacktraceTop:
g_settings_
?? ()
__libc_start_main (main=0x4019f0, argc=4, ubp_av=
?? ()
Title: gsettings crashed with SIGSEGV in g_settings_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.