display preferences and xrandr don't find proper resolutions

[Lars Oliver Hansen]

Problems in gnome-display-properties (g-d-p):
1. Resolutions bigger than the resolution Ubuntu defaults to on login are not available

Problems in xrandr:
2. same as 1.
3. maximum reported virtual resolution for a screen is ridiculously wrong (too small ie. 320x240 and can get too large)
4. 3. leads to xrandr not applying newly added modes

Problems in g-d-p:
5. after adding a new mode to xrandr, the mode becomes available in g-d-p and every supported less res but more res than in 1. mode becomes available
6. some writing of config files and a relogin becomes necessary. This seems unnecessary.

Problems in xrandr:
7. after choosing a mode with g-d-p the virtual resolution increases after every choosing of a extended display position in g-d-p (this leads to 3.)

Problems on external display:
8. the mouse navigates to an extended area and the complete screen can be used for windows etc., but half of the screen has drawn elements garbage.

9. Available refresh rates are as wrong as resolutions everywhere.

Background:

I have a laptop with a 1280x800 internal display and an iiyama Vision Master 510 Pro crt connected on VGA. At first the g-d-p showed every resolution and everything was selectable and settable to my likings in every combination of placements, resolutions and refresh rates. One week later above problems occured. Then I have a Samsung Syncmaster T200HD 1690x1050 tft also connected on the same VGA (when the other is not connected of course). At first g-d-p had above problems, but xrandr hadn't so I could use xrandr to set everything as I liked. Then xrandr got an update 5 weeks ago I think and now it has the same problems as g-d-p and as outlined above.

References:

http://ubuntuforums.org/showthread.php?t=1013209
http://ubuntuforums.org/showthread.php?t=1187965

Thanks

[Lars Oliver Hansen (lolh)]

any development here?

[Monkey (monkey-libre)]

I´ve assigned this bug to the xorg package.

Thank You for making Ubuntu better.

[Bryce Harrington (bryce)]

Hi lolh,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

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.

[A.J. (ashnur)]

I do have the same problem as the original reporter had. Also I have a different graphics card and the exactly same model of monitor. Although I am just a user, I do believe that the monitor is causing the problem, as it is not successfully recognized. Pls feel free to ask any data if you need.

[Monkey (monkey-libre)]

Please attach the output of `lspci -vvnn` and `dmesg` with the Terminal (Applications>Accesories>Terminal), and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[A.J. (ashnur)]

I solved a problem with a new graphics card and driver after I wrote here, but will remove it and reproduce the bug. Pls do not close the bug, yet. Thanks.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Lars,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 395732

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 395732 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/395732

[Lars Oliver Hansen (lolh)]

Hello,

I don't have the monitor anymore. I can't reproduce it with my current setup. Others having experienced the same issue are requested to file a new bug. Yet I still leave this one open if anyone wants to add something. This issue expires in 59 days automatically anyway. I thought I had replied to this topic once stating that I don't have the setup anymore to reproduce this issue. I wonder why this reply doesn't show here. Perhaps I only replied via the notification email erroneously.

Thanks

Lars

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]