Settings crashes (core dumped, no traceback) when getting bad schema
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glib2.0 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
$ python
Python 2.7.4 (default, Apr 17 2013, 22:29:30)
[GCC 4.7.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from gi.repository import Gio
>>> Gio.Settings.
(process:2822): GLib-GIO-ERROR **: Settings schema 'com.canonical.
Trace/breakpoint trap (core dumped)
$
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: python-gi 3.8.0-2
ProcVersionSign
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Sat Apr 20 08:49:34 2013
InstallationDate: Installed on 2013-02-16 (62 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
SourcePackage: pygobject
UpgradeStatus: Upgraded to raring on 2013-04-19 (0 days ago)
This is due to glib asserting when you try to access a nonexisting schema. This has been discussed many times and is indeed a bit ugly, but an upstream design decision.