Troubleshooting
4749
Comment: Shortened sect. text as stretched ToC.
|
← Revision 64 as of 2017-11-18 18:25:00 ⇥
4582
1) Mention xdiagnose install. 2) Reorder as folks may stop reading once reported. 3) RM general reporting as its distracting.
|
Deletions are marked like this. | Additions are marked like this. |
Line 48: | Line 48: |
First, one will want to familiarize themselves with how to report bugs effectively as per [[https://wiki.ubuntu.com/ReportingBugs|here]]. | First, please install the package xdiagnose. |
Line 50: | Line 50: |
Once this is reviewed, please file a new bug report with Ubuntu via a terminal: | Next, ensure you click the Yes button for attaching additional debugging information after running the following via a terminal: |
Line 53: | Line 53: |
}}} Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. | }}} |
Line 55: | Line 55: |
== Include developer information == | == Include developer information in your report == |
|
Identifying if the issue is a bug or not
If you aren't sure if you have encountered a software bug in Ubuntu, then you would want to seek help in determining if the issue is a bug or not from here.
If you have confirmed the issue is a bug, please read on.
Determining which type of bug you have
Not all bugs where X seems to be the root cause are in fact an X related bug. Hence, here is documentation on potential root causes:
Booting
Display Issues
i855 is Unsupported - Explanation of why i845, i855, i865, etc. chips aren't supported
General Issues
Glossary - Common error messages and terminology
X Transitions - Explanation for "installing xserver-xorg-core would break existing software"
Input Issues
Reporting a confirmed X bug to Launchpad
Initial filing of the report
First, please install the package xdiagnose.
Next, ensure you click the Yes button for attaching additional debugging information after running the following via a terminal:
ubuntu-bug xorg
Include developer information in your report
One will want to answer the following questions in order for a developer to address the issue:
- Does the report include debugging information from the relevant article relating to the reported issue?
- Is this a regression?
- Does this happen in the latest version of Ubuntu?
- Does this happen in the latest version available from upstream?
Debugging techniques
Non-Graphical Booting - Running X manually, without a display manager (like lightdm, kdm, gdm...)
Wireless Without X - How to get a wireless network connection without X.
Direct Wired Without WAP - How to connect two laptops with direct ethernet cord.
Crashes and Freezes
X Backtracing - How to collect a backtrace for an X crash
Interpreting GPU Dumps - Ringbuffers, batchbuffers, and the meaning of intel_gpu_dump output
Valgrind - Debugging memory leaks
Other Techniques
X Bisecting - Using bisection techniques to solve regressions or backport fixes
X/Testing/Touch - Touchscreen and multi-touch testing
Triaging and tagging X bugs
Please see here for more on triaging X bugs, and here for tagging.
Fixing an X crash
Other Resources
Video Resources at help.ubuntu.com
X/Troubleshooting (last edited 2017-11-18 18:25:00 by penalvch)