not-enough-info Not enough information has been provided to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues. Too little info provided to bother with Invalid apport-collect Thank you for taking the time to report this bug and helping to make PROJECTNAME better. Please execute the following command in a terminal after reproducing the issue, and it it will automatically gather debugging information needed for this bug: apport-collect BUGNUMBER (You may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.) Run apport-collect BUGNUMBER Incomplete lspci-vvnn Could you please also run `lspci -vvnn > lspci-vvnn.txt` and attach that file to this bug report? Thanks ahead of time. Needs lspci -vvnn Incomplete vague-desc Hi REPORTER, Hmm... I'm not sure I totally understand your description of the problem. Could you please elaborate and clarify? You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html or the Ubuntu-X bug reporting guidelines at http://wiki.ubuntu.com/X/Reporting . Incomplete file-new-bug-similar-symptoms while your symptoms sound similar, you're likely experiencing an unrelated issue. Please file a new bug for it using the command 'ubuntu-bug xorg' (and a photo if any corruption is seen). Similar symptoms, but probably an unrelated issue, so file a new bug report backtrace Are you able to reproduce this issue easily? If so, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions. If not, could you describe the conditions under which the crash tends to occur? If reproducible collect full backtrace Incomplete High BlankScreen-intel_reg_dumper REPORTER, Please install xserver-xorg-video-intel-dbg and run the tool intel_reg_dumper once when the screen is working correctly, and once with it showing the blank screen / out-of-range error, and attach both files. Comparing the register settings for them may highlight where the problem is. Black or blank screen issues, out-of-range issues need register dumps Incomplete BlankScreen-radeontool-pre-r5xx Hi REPORTER, radeontool can be used to assist in debugging this issue. To install it from the command line, use this command: sudo apt-get install radeontool After installing it, you run it like this: radeontool regmatch '*' > regdump_good.txt radeontool regmatch '*' > regdump_broke.txt Run it two times. Once when you have a working screen (for any driver), and once in the broken case (either from the tty console or logged into the sick box remotely). Attach both of those to this bug report, and we can then forward this issue upstream. Thanks ahead of time! Incomplete BlankScreen-avivotool-r5xx-and-newer Hi REPORTER, avivotool can be used to assist in debugging this issue. avivotool is provided with the radeontool package, so to install it run: sudo apt-get install radeontool After installing it, you run it like this: avivotool regs all > regdump_good.txt avivotool regs all > regdump_broke.txt Run it two times. Once when you have a working screen (for any driver), and once in the broken case (either from the tty console or logged into the sick box remotely). Attach both of those to this bug report, and we can then forward this issue upstream. Thanks ahead of time! Incomplete ati-agpmode Based on the description of the symptoms, it sort of sounds like this might be caused by an incorrect AGPMode setting, which is relevant when DRI is enabled. You should test if changing this makes the issue go away. In your /etc/X11/xorg.conf set AGPMode to various values like this: Section "Device" ... Option "AGPMode" "2" EndSection Possible values include 1, 2, 4, 8. You can see what it's currently set to by looking in /var/log/Xorg.0.log. It's worthwhile to test all four values even once you find one that works. If this takes care of it for you, we may be able to establish a quirk to set it for your hardware combo, if you can provide the following data: * AGPMode value(s) that work * Make/Model of laptop or motherboard * Output of lspci -vvnn * Is the system all factory hardware, or have any parts been replaced? * Is there an AGP Mode in the system BIOS? - If so, is it set to the factory default? For more details on this, please see the "ATI AGP Mode Quirk" section at https://wiki.ubuntu.com/X/Quirks Suggest testing different AGPMode settings. Suitable for -ati bugs with AGP hardware experiencing hangs or corruption. Incomplete needs-retest-on-karmic Well, next I'd like to forward this issue upstream, but first it must be retested on latest development version of Karmic to make sure the issue still happens there with the latest code. ISO images are available via http://www.ubuntu.com/testing/. If you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log and dmesg from this testing. Needs to be reproduced on the development release Incomplete retested-needs-upstreamed Thanks for testing; this should go upstream. Setting to Confirmed for now. Thanks for testing, set to confirmed to go upstream Confirmed upstreamed-subscribe REPORTER - I've forwarded this bug upstream to UPSTREAMBUG - please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time! Subscribe to upstream bug Triaged upstreamed I've forwarded this bug upstream to UPSTREAMBUG and subscribed you to it. Please follow up with them in case they need further information or wish you to test something. Subscribe to upstream bug Triaged CoC We understand that bugs like this one can be very frustrating, but it is important to keep the discussions civil and on a technical level. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . fixed Thanks for letting us know the issue is resolved. Thanks, Fix Released Fix Released expired We're closing this bug since it is has been some time with no response from REPORTER. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of PROJECTNAME, since this confirms the bug is one we may be able to pass upstream for help. Invalid retrace-failed Thanks for reporting this bug, however unfortunately the retracer failed to generate a useful symbolic stack trace this time. We're closing the bug as unable to analyze, but if you can still reproduce it on the development release, feel free to reopen the bug. In this case, please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/X/Backtracing and upload the backtrace (as an attachment) to the bug report. Close out as unable to analyze Invalid fglrx-hw-unsupported Thank you for reporting this bug about fglrx, however the video card mentioned in this bug report is no longer supported in fglrx. ATI only supports R600 and newer chips on the -fglrx driver. You'll want to focus on using the -ati driver instead for this hardware. Invalid hw-unavailable Since the hardware is no longer available for doing troubleshooting with, we'll have to close the bug for now. However please feel free to reopen if you or anyone else has the same HW and can reproduce this issue using the latest development version of PROJECTNAME and is willing to do some troubleshooting with it. Invalid