Differences between revisions 1 and 134 (spanning 133 versions)
Revision 1 as of 2007-06-01 00:50:10
Size: 1277
Editor: 71
Revision 134 as of 2012-04-13 23:48:21
Size: 3923
Editor: bryce
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page is to serve as a gathering point for various X-related specs, howtos, todo lists, and other assorted resources. #title Ubuntu-X Team
||<tablestyle="float:right; background: #FFFFFF; margin: 0 0 1em 1em;" style="padding:2.0em;"> {{https://launchpadlibrarian.net/10142846/xswat-192.png}} ||
Line 3: Line 5:
== Driver Info == === Basic Troubleshooting Resources ===
 * [[http://ubuntuforums.org/forumdisplay.php?f=326|Absolute Beginner Talk Forum]]
 * [[X/Reporting|X Reporting]] - How to create good X bug reports
 * [[http://ubuntuforums.org/forumdisplay.php?f=332|Hardware & Laptops Support Forum]]
Line 5: Line 10:
 * [http://nouveau.freedesktop.org/wiki/ nouveau] === Common Problems ===
 * [[X/Bugs]] - Analysis of collection of similar bugs
 * [[X/Bugs/Transitions]] - Explanation for "installing xserver-xorg-core would break existing software"
 * [[X/i8xxUnsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported
 * [[X/HybridGraphics]] - How to make the most of your system with hybrid graphics
 * [[X/CommonErrors]]
 * [[X/ErrorMessages]]
 * [[Bugs/AtiDriver]]
Line 7: Line 19:
== Teams == === Troubleshooting Techniques ===
<<Include(X/Troubleshooting, , from="#start")>>
Line 9: Line 22:
 * ["XSwat"] - Xorg bug triage team  * [[X/Troubleshooting|X Troubleshooting]] - How to analyze X bugs to make them solvable
 * [[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
 * [[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/BootOptions|BootOptions]]
   * [[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide|fglrx installation on Ubuntu]]
 * DebuggingUsplash
 * [[X/Dev/DeviceTreeHWDetection]]
Line 11: Line 38:
== Blueprints == === Configuration Tips ===
 * [[X/Config|Configuration]] - Configuring input devices, graphics, drivers, and more
 * [[X/KernelModeSetting]] - Configuring and using KMS (in Karmic)
 * [[X/Rootless]] - Running X as a user process, not as the root user
 * [[X/InputCoordinateTransformation]] - How to set the mapping of an input device to a display through X
 * [[https://launchpad.net/~xorg-edgers|XorgOnTheEdge]] - for bleeding edge packages
 * [[https://help.ubuntu.com/community/BinaryDriverHowto|Binary Driver Howto]]
 * [[https://help.ubuntu.com/community/HybridGraphics|Hybrid Graphics Howto]]
Line 13: Line 47:
=== Current Specifications ===

These specifications are likely to be included in an upcoming Ubuntu release.

 * ["Xorg7.3Integration"] - Integrate Xorg 7.3 components, adopt config autodetection
 * ["DisplayConfigGTK"] - New GUI utility for configuring Xorg
 * ["BulletProofX"] - Failsafe mode when X doesn't start, with displayconfig-gtk to configure
 * ["CompositeByDefault"] - Switch default window manager from Metacity to Compiz, use Beryl effects
 * ["XorgCtrlAltBackspace"] - Disable the Ctrl-Alt-Bksp shortcut

=== Pending Specifications ===

These specifications need further discussion and drafting, but are likely to be accepted for future Ubuntu releases if this work is done.

 * ["MouseExtraButtons"] - Enable extra buttons present on Microsoft Explorer mice

=== Historical Specifications ===

 * ["XRoadmap"] - Xorg 7.0, discusses the X modularization and XKB work (for Warty?)
 * ["XRoadmapDapper"] - Plans for continuing maintenance of X, Mesa packaging in Dapper
=== Development Foundations ===
 * [[X/SwatTeam]] - Joining the Ubuntu X.org team
 * [[X/Triaging|X Triaging]] - How to ensure new X bug reports have enough info to troubleshoot
 * [[X/Architecture]] - High level architectural overview of X.org
 * [[X/DriverDevelopment]] - Developing new Xorg drivers for Ubuntu
 * [[X/DriverBuilding]] - Building debs of upstream drivers
 * [[X/Glossary|X Glossary]] - Explanations for confusing terms often seen in logs and error messages
 * [[X/Blueprints]] - Specifications of interest for X
 * [[X/GitUsage]] - Instructions for using git
 * [[X/DesktopWishlist]] - Pending Xorg changes that would benefit Ubuntu Desktop
 * [[X/KernelWishlist]] - Pending/desired kernel changes that would benefit Xorg
 * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/?field.tag=xorg-needs-kernel-fix]] - Kernel fixes needed for xorg issues
 * [[X/BetaReviewChecklist]] - Things to do / stuff to consider reverting around -beta
 * [[http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/versions-current.html|Current Package Merge Status]]
 * [[X/Tagging]] - Bug tagging
 * [[X/PackageNotes]] - One of our packaging tools makes use of this


Basic Troubleshooting Resources

Common Problems

Troubleshooting Techniques

Include: Nothing found for "#start"!

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:


Display Issues

General Issues

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

Crashes and Freezes

Other Techniques

Triaging and tagging X bugs

Please see here for more on triaging X bugs, and here for tagging.

Fixing an X crash

  • For more on this, please see here.

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

Other Resources


Configuration Tips

Development Foundations

X (last edited 2016-01-10 21:04:44 by penalvch)