Differences between revisions 18 and 19
Revision 18 as of 2008-08-06 16:24:06
Size: 4219
Editor: localhost
Comment: converted to 1.6 markup
Revision 19 as of 2008-08-06 17:00:14
Size: 4199
Editor: localhost
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url(''); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url(''); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>||

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.


Bugs relating to Compiz typically fall into 4 categories:

  1. Integration bugs - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
  2. Crasher bugs - Log files from the crash incident are required to track down these.
  3. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help
  4. Plugin bugs - Sometimes bug reports about a specific plugin will be reported about compiz in general. However, plugins are provided by different packages and the bug should be moved to the right package. Plugins are provided by the packages compiz-plugins, compiz-fusion-plugins-main, and compiz-fusion-plugins-extra. A reporter may mention a plugin by name based off what it is called in Compiz Config Settings Manager however this doesn't tell you what file to look for in a package. You can determine the plugin name by searching the xml files in /usr/share/compiz/ for what the plugin is called and in that xml file you'll find the plugin name. Using that you can find the right package via dpkg -S <plugin-name>.xml i.e. switcher.

How to file

When reporting a bug about Compiz you should include your ~/.xsession-errors file, /var/log/Xorg.0.log and the output of lspci -vvnn as separate attachments to your bug report.

Additionally, it would be helpful to know if you can recreate the bug with the default preferences. You can reset the preferences by launching "compiz-config-manager" found in System -> Preferences and labelled Advanced Desktop Effects Settings. Click on the "Preferences" button and then on the "Reset to defaults" button.

Bug tags

Compiz provides a variety of plugins for modifying the behavior of your desktop. If the bug is related to a specific plugin it would be helpful to tag it with the plugin name.


Use case


This bug pertains to the shift-switcher plugin


This bug pertains to the application-switcher plugin

Debugging procedure

Make sure to always include ~/.xsession-errors, /var/log/Xorg.0.log, and the output of lspci -vvnn. The output of lspci will contain information about the video card, identified as "Display controller", that the reporter has which is useful because some bugs are hardware specific.

Also try to see if the bug happens with the default settings. To get the default settings, install "compiz-config-manager", launch it and then go to "Preferences" (left bottom corner) and click on the "Reset to defaults" button.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.






Intel - 3D artifacts when compiz enabled

When dragging 3D apps, glxgears for example, artifacts are left behind - not a compiz bug






This bug can be identified by ...

Mark as duplicate of 8896 with the comment "Thank you for reporting. This issue has already been reported as bug #8896. Marking as Duplicate."


How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.

CategoryBugSquad CategoryDebugging

DebuggingCompiz (last edited 2015-09-21 10:08:45 by 3v1n0)