gdm should not add to resolution switches

[Andreas Schildbach]

Binary package hint: gdm

I am using a dual screen setup: Dell Latitude X1 with an internal 1280 x 768 screen, and an external Dell 2405 monitor with 1920 x 1200.

With KMS now enabled, I am happy to say that the native resolution of my screens is used very early in the boot process. But wait - gdm switches back to ancient 800 x 600 resolution. Only to give way to native resolutions again after login. This nagging and time consuming resolution switches continue when logging out to login with another user.

I would expect the native resolutions to be used all the time. At least for the primary screen, which is always the internal screen if there is one. Please avoid resolution switching as often as possible! It severly degrades user experience.

ProblemType: Bug
Architecture: i386
Date: Fri Jul 31 19:06:30 2009
DistroRelease: Ubuntu 9.10
Package: gdm 2.27.4-0ubuntu6
ProcEnviron:
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SourcePackage: gdm
Uname: Linux 2.6.31-4-generic i686

[xtknight (xt-knight)]

I can confirm that gdm is putting its hand in the cookie jar. No res changing needed...

[Sebastien Bacher (seb128)]

the default screen resolution is a xorg thing

[FaberfoX (faberfox)]

There's a lot of talk about this in many bug reports(#446412, #394273, #286001), and as far as I can see, with kms enabled, gdm is the one switching resolutions, xsplash is right, gdm messes it and then once it's done X returns to the original res set at startup.
The ideal solution would be for gdm not to change resolution, as kms is setting both displays at their right value.
Attached are my dmesg and X.org.log

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Andreas,

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 407426

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 407426 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/407426

[Andreas Schildbach (schildbach)]

The bug is still present in Lucid final. "apport-bug" says "no additional information collected".

[penalvch (penalvch)]

Andreas Schildbach, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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