DebuggingCompiz

Revision 1 as of 2007-12-13 16: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

Debugging procedure

Make sure to always include ~/.xsession-errors and /var/log/Xorg.0.log

Known bugs

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

Open

Bug#

Description

Action

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

Closed

Bug#

Description

Action

[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