gsettings crashed with SIGSEGV in g_settings_schema_source_ref()

Bug #919489 reported by Martin Albisetti on 2012-01-21
This bug affects 12 people
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)

Bug Description

Updated. rebooted, crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libglib2.0-bin 2.31.10-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Jan 20 20:04:53 2012
ExecutablePath: /usr/bin/gsettings
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111214)
ProcCmdline: gsettings get org.gnome.desktop.interface toolkit-accessibility
 PATH=(custom, no user)
 Segfault happened at: 0x7f5d433f84b3 <g_settings_schema_source_ref+3>: lock addl $0x1,0x10(%rdi)
 PC (0x7f5d433f84b3) 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
 g_settings_schema_source_ref () from /usr/lib/x86_64-linux-gnu/
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/
 ?? ()
 ?? ()
Title: gsettings crashed with SIGSEGV in g_settings_schema_source_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Martin Albisetti (beuno) wrote :

 g_settings_schema_source_ref (source=0x0) at /build/buildd/glib2.0-2.31.10/./gio/gsettingsschema.c:213
 main (argc=4, argv=0x7fffded9dd68) at /build/buildd/glib2.0-2.31.10/./gio/gsettings-tool.c:714

Changed in glib2.0 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glib2.0 (Ubuntu):
status: New → Confirmed
tags: added: raring
tags: added: quantal
tags: added: saucy
tags: added: bugpattern-needed
Tais P. Hansen (taisph) on 2016-03-26
tags: added: xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers