Debugging

Differences between revisions 60 and 62 (spanning 2 versions)
⇤ ← Revision 60 as of 2009-12-15 16:28:48 →
Size: 1674
Editor: ip24-255-18-229
Comment:
← Revision 62 as of 2010-03-01 22:07:29 → ⇥
Size: 1942
Editor: pool-74-107-129-37
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
   I. [[X/Reporting]] - How to create good X bug reports
   I. [[X/Glossary]] - Explanations for commonly seen terms and error messages
   I. [[X/Backtracing]] - How to collect a backtrace for an X crash
   I. [[X/Triaging]] - How to ensure new X bug reports have enough info to troubleshoot
   I. [[X/Troubleshooting]] - How to analyze X bugs to make them solvable
   I. [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes
   I. [[X/Quirks]] - Fixes for some common hardware-specific issues
   I. [[X/Upstreaming]] - Forwarding X bugs upstream		    I. [[X/Reporting|X Reporting]] - How to create good X bug reports
   I. [[X/Triaging|X Triaging]] - How to ensure new X bug reports have enough info to troubleshoot
   I. [[X/Tagging|X Symptom Tagging]] - Standard tags to use for flagging symptoms
   I. [[X/Backtracing|X Backtracing]] - How to collect a backtrace for an X crash
   I. [[X/Upstreaming|X Upstreaming]] - Forwarding X bugs to their upstream project
   I. [[X/Glossary|X Glossary]] - Explanations for confusing terms often seen in logs and error messages
   I. [[X/FixingCrashes|X Crash Fixing]] - How to fix X crashes
   I. [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues
   I. [[X/Troubleshooting|X Troubleshooting]] - How to analyze X bugs to make them solvable
   I. [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes

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 Triaging - How to ensure new X bug reports have enough info to troubleshoot

  3. X Symptom Tagging - Standard tags to use for flagging symptoms

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

  5. X Upstreaming - Forwarding X bugs to their upstream project

  6. X Glossary - Explanations for confusing terms often seen in logs and error messages

  7. X Crash Fixing - How to fix X crashes

  8. X Quirks - Fixes for some common hardware-specific issues

  9. X Troubleshooting - How to analyze X bugs to make them solvable

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

Other Resources

CategoryDebugging

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