Troubleshooting
Differences between revisions 50 and 64 (spanning 14 versions)
|
Size: 3089
Comment:
|
← Revision 64 as of 2017-11-18 18:25:00 ⇥
Size: 4582
Comment: 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 2: | Line 2: |
| For hard bugs the analysis phase is the most important, and most challenging part of bug work. Depending on how the bug is behaving, there are multiple directions to investigate the issue. Here's some different approaches: | ||<tablestyle="float:right; background: #FFFFFF; margin: 0 0 1em 1em;" style="padding:2.0em;"> {{https://launchpadlibrarian.net/10142846/xswat-192.png}} || ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 4: | Line 5: |
| === Common Problems === * [[X/Glossary]] - Common error messages and terminology |
= 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 [[https://help.ubuntu.com/community/ReportingBugs|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 * [[https://help.ubuntu.com/community/BootOptions|Boot Options]] * [[DebuggingKernelBoot|Debugging Kernel Boot Problems]] Display Issues * [[X/Troubleshooting/3D|3D / GLX corruption and other issues]] * [[Kernel/Debugging/Backlight|Backlight issues]] * [[X/Troubleshooting/BlankScreen|Blank Screen on startup issues]] * [[X/i8xxUnsupported|i855 is Unsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported * [[X/Troubleshooting/HugeFonts|Fonts displayed way too big]] * [[X/Troubleshooting/Freeze|Freeze issues]] * [[X/Troubleshooting/IntelPerformance|Intel graphics performance issues]] * [[X/MonitorDetection|Monitor detection]] * [[X/Troubleshooting/Resolution|Resolution detection]] * [[X/Troubleshooting/VideoDriverDetection|Video driver detection]] General Issues * [[X/Glossary|Glossary]] - Common error messages and terminology * [[X/Troubleshooting/HighCPU|High CPU usage issues]] * [[X/Troubleshooting/HighMemory|High memory usage issues]] |
| Line 7: | Line 36: |
| * [[X/i8xxUnsupported|i855 is Unsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported * [[X/HybridGraphics|Hybrid Graphics is Unsupported]] - Not officially supported, but the community has workarounds * [[X/Troubleshooting/Resolution|Resolution issues]] * [[X/Troubleshooting/HighCPU|High CPU issues]] * [[X/Troubleshooting/BlankScreen|Blank Screen on startup issues]] * [[X/Troubleshooting/Freeze|Freeze issues]] * [[X/Troubleshooting/SingleColorScreen|Single color (brown/blue/etc.) screen on startup]] * [[X/Troubleshooting/HugeFonts|Fonts displayed way too big]] * [[X/Troubleshooting/XServerCrashOnResume|xserver crash on resume]] * [[X/Troubleshooting/OnlyLoadsVesa|Only loads vesa instead of correct driver]] * [[X/Troubleshooting/IntelPerformance|Intel graphics performance issues]] * [[X/Troubleshooting/HalBreaksKeyboardAndMouse|Keyboard and mouse quit working]] |
* [[X/Troubleshooting/XError|Program received an X Window System error]] * [[DebuggingKernelSuspend|Suspend and Resume issues]] Input Issues * [[DebuggingKeyboardDetection|Keyboard detection]] |
| Line 20: | Line 42: |
| * [[X/Troubleshooting/XError|Program received an X Window System error]] * [[X/Troubleshooting/NvidiaDriverMissingKernelDriver]] * [[X/MonitorDetection|Monitor Detection problems]] * [[X/Troubleshooting/Other|Other common issues...]] |
* [[DebuggingTouchpadDetection|Touchpad detection]] |
| Line 25: | Line 44: |
| === Troubleshooting Techniques === * [[X/Backtracing|X Backtracing]] - How to collect a backtrace for an X crash * [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes * [[X/Testing/Touch]] - Touchscreen and multi-touch testing * [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues * [[X/FixingCrashes|X Crash Fixing]] - How to fix X crashes * [[X/InterpretingIntelGpuDump]] - Ringbuffers, batchbuffers, and the meaning of `intel_gpu_dump` output * [[X/DebuggingWithValgrind]] * [[X/NonGraphicalBoot]] - Running X manually, without gdm |
= 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 = * [[X/NonGraphicalBoot|Non-Graphical Booting]] - Running X manually, without a display manager (like lightdm, kdm, gdm...) |
| Line 36: | Line 68: |
| * [[https://help.ubuntu.com/community/BootOptions|BootOptions]] * [[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide|fglrx installation on Ubuntu]] * DebuggingUsplash * [[X/Dev/DeviceTreeHWDetection]] * [[X/Troubleshooting/FglrxInteferesWithRadeonDriver|Switching between -fglrx and -ati drivers]] * [[X/Troubleshooting/NvidiaDriverSwitching|Switching between -nvidia and -nouveau drivers]] * The {{{drm.debug=0x04}}} kernel option can be used to get additional debugging data included in your {{{dmesg}}} output. |
Crashes and Freezes * [[X/Backtracing|X Backtracing]] - How to collect a backtrace for an X crash * [[X/InterpretingIntelGpuDump|Interpreting GPU Dumps]] - Ringbuffers, batchbuffers, and the meaning of `intel_gpu_dump` output * [[X/DebuggingWithValgrind|Valgrind]] - Debugging memory leaks Other Techniques * [[X/Dev/DeviceTreeHWDetection|Device Tree]] * [[X/Bisecting|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 [[https://wiki.ubuntu.com/X/Triaging|here]] for more on triaging X bugs, and [[https://wiki.ubuntu.com/X/Tagging|here]] for tagging. = Fixing an X crash = * For more on this, please see [[https://wiki.ubuntu.com/X/FixingCrashes|here]]. * [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues. = Other Resources = * [[https://help.ubuntu.com/community/Video|Video Resources]] at help.ubuntu.com * For installing [[https://help.ubuntu.com/community/BinaryDriverHowto/AMD|fglrx]] or [[https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia|nvidia]] proprietary drivers. |
|
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)