Compiz option -> Compizconfig GTK+ interactive mode fails autopilot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| compiz (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Discovered while running autopilot with the help of thomir: as of recently, when setting a Compiz option, Compizconfig attempts to put GTK+ into interactive mode, which breaks anything else running the GTK+ mainloop (autopilot, for one).
This stalls some testing work on Unity FWIW.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: python-compizconfig 1:0.9.8+
ProcVersionSign
Uname: Linux 3.5.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Sun Aug 19 18:32:05 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: compiz
UpgradeStatus: Upgraded to quantal on 2012-08-16 (3 days ago)
| Allan LeSage (allanlesage) wrote | #1 |
| tags: | added: compiz-0.9 |
| Sam Spilsbury (smspillaz) wrote | #2 |
This is probably a red herring for the original bug that saw it crash if you tried to look up a setting that didn't exist.