compiz crashed with signal 5 in g_settings_get_value()

Bug #1056113 reported by Jussi Pakkanen
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After upgrading to newest quantal packages, I get this when logging in. Respawning Compiz does not work so this bug makes Unity unusable.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 25 14:06:36 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120918.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 getVariantAtKey () from /usr/lib/libcompizconfig_gsettings_backend.so
 readOption () from /usr/lib/compizconfig/backends/libgsettings.so
Title: compiz crashed with signal 5 in g_settings_get_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_schema_get_value (schema=schema@entry=0x3d20500, key=key@entry=0x2b34f10 "devices-option") at /build/buildd/glib2.0-2.33.14/./gio/gsettingsschema.c:640
 g_settings_schema_key_init (key=key@entry=0x7fff7ab73ca0, schema=0x3d20500, name=name@entry=0x2b34f10 "devices-option") at /build/buildd/glib2.0-2.33.14/./gio/gsettingsschema.c:751
 g_settings_get_value (settings=0x2ffdf70, key=0x2b34f10 "devices-option") at /build/buildd/glib2.0-2.33.14/./gio/gsettings.c:1079
 getVariantAtKey (settings=<optimized out>, key=<optimized out>, pathName=0x2b34400 "/org/compiz/profiles/unity/plugins/unityshell/", type=TypeInt) at /build/buildd/compiz-0.9.8.2+bzr3377/compizconfig/gsettings/gsettings_backend_shared/gsettings_util.c:482
 getVariantForCCSSetting (backend=backend@entry=0x2177950, setting=setting@entry=0x3009ec0) at /build/buildd/compiz-0.9.8.2+bzr3377/compizconfig/gsettings/src/gsettings.c:49

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
description: updated
Revision history for this message
Omer Akram (om26er) wrote :

try this: dconf reset -f /org/compiz and then relogin, see if that helps.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1044662, so it 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. Feel free to continue to report any other bugs you may find.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the error here is: "Settings schema 'org.compiz.unityshell' does not contain a key named 'devices-option'"

it's weird though because there is no 'devices-option' used in the current unity's codebase ... what version of unity is installed (dpkg -l | grep unity)

visibility: private → public
Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

6.6.0-0ubuntu1

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

I tried recompiling the schemas with 'sudo glib-compile-schemas /usr/share/glib-2.0/schemas' but it did not help.

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

This has something to do with user configuration. If I create a new user account, login works for that account.

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

Deleting all compiz config directories in ~ and ~/.config fixes the problem. I expect this to bite many upgraders, though.

Revision history for this message
Omer Akram (om26er) wrote :

Jussi, just curious did you try reset -f /org/compiz (comment#6) when the issue was happened?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Why is this no longer a duplicate of the original bug 1044662?

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

@Omer Akram: dconf reset -f /org/compiz and relogin did not solve the problem, unity still doesn't start.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1044662, so it 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. Feel free to continue to report any other bugs you may find.

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.