Debugging

Differences between revisions 45 and 74 (spanning 29 versions)
Revision 45 as of 2008-08-06 16:39:52
Size: 900
Editor: localhost
Comment: converted to 1.6 markup
Revision 74 as of 2013-11-12 03:51:50
Size: 2386
Editor: anthonywong
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<Include(Debugging/Header)>> <<Include(X/MenuBar)>>
Line 4: Line 4:
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.
## 20121030 https://launchpad.net/~penalvch Please note https://wiki.ubuntu.com/DebuggingProcedures links to this article URL via -> Debugging X (display problems etc.) . As per https://wiki.ubuntu.com/X/Debugging?action=diff&rev1=66&rev2=67 it looks like Bryce wants the new Debugging URL to be https://wiki.ubuntu.com/X ?!
Line 8: Line 6:
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.
The X Window 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.
Line 13: Line 8:
Even non-developers can help! The goal of this handbook is to give
folks a toolset for rendering these bugs easily solvable.
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.
Line 16: Line 10:
== Contents: == == Contents ==
Line 18: Line 12:
I. [[X/Reporting]] - How to properly report bugs in X    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
Line 20: Line 23:
II. [[X/Backtracing]] - Getting gdb backtraces of X

III. [[X/Triaging]] - Steps for processing newly reported bugs to make them ready for troubleshooting

IV. [[X/Troubleshooting]] - Tips for analyzing and troubleshooting bugs
== Other Resources ==
 * [[X/Debugging/WirelessWithoutX|Wireless Without X]] - How to get a wireless network connection without X.
 * [[X/Debugging/WiredWithoutRouter|Direct Wired Without WAP]] - How to connect two laptops with direct ethernet cord.
 * [[https://help.ubuntu.com/community/Video|Video Resources]] at help.ubuntu.com
 * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing [[https://help.ubuntu.com/community/BinaryDriverHowto/ATI|fglrx]] or nvidia
 * [[https://help.ubuntu.com/community/BootOptions|BootOptions]]
 * [[X/CommonErrors]]
 * [[X/DebuggingWithValgrind]]
 * [[https://launchpad.net/~xorg-edgers|XorgOnTheEdge]] - for bleeding edge packages
----
CategoryDebugging

The X Window 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)