Debugging

Differences between revisions 59 and 60
⇤ ← Revision 59 as of 2009-12-15 16:27:21 →
Size: 1676
Editor: ip24-255-18-229
Comment:
← Revision 60 as of 2009-12-15 16:28:48 → ⇥
Size: 1674
Editor: ip24-255-18-229
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia
Line 22: Line 23:
 * [[https://launchpad.net/~xorg-edgers|XorgOnTheEdge]] - for bleeding edge packages
 * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia
Line 30: Line 29:
 * [[https://launchpad.net/~xorg-edgers|XorgOnTheEdge]] - for bleeding edge packages

The X Windows System is a critical component in the Ubuntu operating system. X is not without its bugs, but fortunately debugging X issues is not rocket science.

The vast majority of Ubuntu X issues fall into one of several distinct categories, and based on the way they manifest, there are several different tactics that can be employed in a nearly paint-by-numbers fashion to isolate them.

Contents

  1. X/Reporting - How to create good X bug reports

  2. X/Glossary - Explanations for commonly seen terms and error messages

  3. X/Backtracing - How to collect a backtrace for an X crash

  4. X/Triaging - How to ensure new X bug reports have enough info to troubleshoot

  5. X/Troubleshooting - How to analyze X bugs to make them solvable

  6. X/Bisecting - Using bisection techniques to solve regressions or backport fixes

  7. X/Quirks - Fixes for some common hardware-specific issues

  8. X/Upstreaming - Forwarding X bugs upstream

Other Resources

CategoryDebugging

X/Debugging (last edited 2016-01-10 22:13:08 by penalvch)