Debugging

Differences between revisions 56 and 57
⇤ ← Revision 56 as of 2009-04-25 09:00:13 →
Size: 1588
Editor: 84-72-178-203
Comment: remove dead and dup links
← Revision 57 as of 2009-12-10 19:23:48 → ⇥
Size: 1584
Editor: eth3
Comment: Fix BinaryDriverHowto link to not be ATI-specific
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * [[https://help.ubuntu.com/community/BinaryDriverHowto/ATI|BinaryDriverHowto]] - for installing fglrx or nvidia  * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia

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

  • I. X/Reporting - How to create good X bug reports

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

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

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

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

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

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

  • VIII. X/Upstreaming - Forwarding X bugs upstream

Other Resources

CategoryDebugging

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