© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Yuri,
Cool, thanks for the photo. I've just recently started looking into X bugs, so if you can point me to additional reports about this I would very much appreciate it.
Here's a few guesses, could you guys let me know what you think on them?
1. It could just be the monitor settings. If the monitor does have some manual controls on the front of them, that's the first thing to try. Yuri - I couldn't see if your monitor has H/V adjustment controls? Your monitor also looks like it could use some pincushion adjustment as well.
2. Xorg may have failed to detect hardware H/v rates and may be selecting a resolution that your monitor clips. A LOT of people have been reporting various issues related to improperly detected monitor H/V rates, resulting in misdetected resolutions. This shows up as a descrepancy between the /etc/X11/xorg.conf file and the /var/log/Xorg.0.log file. If those of you experiencing this problem find that #1 doesn't seem suitable, please upload these two files here in this bug, and we can take a look at them and see. For people that find running xvidtune fixes the issue temporarily, that makes this sound like a likely reason. The workaround for this is to make absolutely sure the hsync and v refresh rates exactly match your monitor's documentation (X ought to be able to detect your monitor settings, but it proves to be rather hit or miss).
3. Driver issue. Martins, you suspect a driver issue and you could very well be right. I'd like to rule out #2 first, especially since you notice it sometimes works and sometimes doesn't. If it's a driver issue then I'd expect it to not work all the time, but the monitor misdetection can sometimes have a random nature to it.
4. Something completely different. Possibly it's a known xorg bug, in which case we can check the freedesktop.org bug tracker. But first let's try ruling out the above.