DebuggingCompiz

Revision 8 as of 2008-02-13 01:16:11

Clear message

Introduction

Bugs relating to Compiz typically fall into 3 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

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.

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.

Open

Bug

Summary

Symptom

[https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/147359 147359]

Intel - 3D artifacts when compiz enabled

When dragging 3D apps, glxgears for example, artifacts are left behind

Closed

Bug

Summary

Symptom

[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896]

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."

Non-bugs

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.

Also see


CategoryBugSquad CategoryDebugging