Screen resolution does not change in live cd

[Graham Flett]

Binary package hint: xorg

When using the Live CD, it automatically selects the highest resolution available, which is not always useful when using a CRT. Changing the resolution via System->Preferences->Screen Resolution does not change the resolution but still shows the revert/keep resolution message box.

Screen resolution did change correctly in VMWare workstation 6, but did not work on Athlon system with GeForce 7600GT graphics card and iiyama S900MT1 monitor.

[Rune K. Svendsen (runeks)]

I have the same problem. The resolution of my screen defaults to 2048x1536@60 Hz when using the Live CD. Going to "System->Preferences->Screen Resolution", choosing another resolution and clicking Apply does nothing. A dialog appears asking me if I want to keep this new resolution, pressing Keep makes no difference and when I enter the Screen Resolution dialog again it is 2048x1536@60 Hz. It doesn't matter which resolution I try changing it to.

Output of "uname -a":

Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Rune K. Svendsen (runeks)]

And I disagree with this bug being a duplicate of bug #68654.

Bug #68654 is about the default resolution of the Live CD being too high. This bug is about not being able to change the resolution.

[David Balažic (xerces8)]

Timo, did you just change this bug as nvidia related ?
I see it all the time on ATI hardware: Radeon 8500, radeon 9500, FireGL 5200

(as also reported in the duplicate bug 159750)

[Timo Aaltonen (tjaalton)]

right, lets change it to xorg-server for now. I'm not sure where the bug lies.

[David Balažic (xerces8)]

I tried 8.04 alpha3 and there it works. (radeon8500 system)
But 7.10 also worked in some cases, so that does not prove the bug fixed.

[Bryce Harrington (bryce)]

The server should be selecting the correct preferred resolution now (it was known to be a bit buggy in Gutsy), so esp. with comment #9 I think this can be closed. Please re-test against Hardy, and if the issue still exists please reopen this bug.