Collect it Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command in a terminal, 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.) Thanks in advance! Incomplete Vague Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. 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 . We'd be grateful if you would then provide a more complete description of the problem. Thanks ahead of time! Incomplete Unknown Fix This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. Invalid Release+1 Testing Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help. Incomplete Upstreamed Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: Triaged Retrace Failed Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace. 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. This will enable us to down your problem. Invalid 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/ . lspci-vvnn Could you please also run `lspci -vvnn > lspci-vvnn.txt` and attach that file to this bug report? Thanks ahead of time. backtrace Are you able to reproduce this issue? If so, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions. intel_reg_dumper 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. retested-needs-upstreamed Thanks for testing; this should go upstream. Setting to Triaged for now. xorg-log Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well. fixed Thanks for letting us know the issue is resolved. similar-symptoms while your symptoms sound similar, you're likely experiencing an unrelated issue. Please file a new bug for it, and see https://wiki.ubuntu.com/X/Debugging for what information to include in your report. upstreamed I've forwarded this bug upstream for you. Could you please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time! expired We're closing this bug since it is has been some time with no response from the original 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 Ubuntu, since this confirms the bug is one we may be able to pass upstream for help. 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 Ubuntu and is willing to do some troubleshooting with it. 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 not-enough-info Not enough information to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues. radeontool radeontool can be used to assist in debugging this issue. 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! 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 at http://cdimages.ubuntu.com/releases/karmic/. 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. Incomplete 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. You'll want to focus on using the -ati driver instead for this hardware. Invalid