[Hardy] GDM starts with wrong display resolution

Bug #194552 reported by Johannes Langlotz
10
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs
libxrandr (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hardy always starts with 1280 x 1024 pixels resolution. But the monitor has 1680 x 1050 pixels. I can set the resolution to 1680 x 1050 with gnome-display-properties but after the next boot the resolution is 1280 x 1024 again. xrandr detects the correct resolutions but why doesn't select it the highest one?

xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1920 x 1200
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected (normal left inverted right x axis y axis)
   1440x900 60.0 + 50.0
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
TMDS-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
   1680x1050 59.9*+
   1280x1024 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
TV disconnected (normal left inverted right x axis y axis)

Revision history for this message
Matthew Woerly (nattgew) wrote :

Seems like this is an issue of the display properties not saving to xorg.conf to be persistent. Changing to gnome-control-center for package.
What video card do you have?

Revision history for this message
Johannes Langlotz (johannes-langlotz) wrote :

I have the Intel chipset 965gm with X3100 graphics core.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-control-center:
status: Incomplete → Invalid
Changed in gnome-settings-daemon:
assignee: nobody → desktop-bugs
importance: Undecided → Low
assignee: desktop-bugs → nobody
assignee: nobody → desktop-bugs
Revision history for this message
Johannes Langlotz (johannes-langlotz) wrote :

OK, not saving the settings is one problem. But not detecting/selecting the display's native resolution is another bug.

Revision history for this message
Florent Mertens (givre) wrote :

Is it only GDM that start with the wrong resolution or even gnome ?
If it's only GDM, gnome-display-properties will not help (at least for now)
as it only set the resolution for gnome.

Revision history for this message
Johannes Langlotz (johannes-langlotz) wrote :

Both started with the wrong resolution. I changed the resolution with gnome-display-properties. The GNOME resolution is correct now. But like you said GDM still starts still with wrong detected resolution.

It is a DELL 2007wfp display and I don't know why xrandr does not use the display's native resolution.

Revision history for this message
Florent Mertens (givre) wrote :

Wrong resolution in gnome after restart was fixed by #191878.
Wrong resolution in GDM is not a bug because gnome-display-properties only set resolution for gnome.
If you want to change it, you'll have to change it manually in xorg.conf.

Changed in libxrandr:
status: New → Invalid
Revision history for this message
Johannes Langlotz (johannes-langlotz) wrote :

Yes it is not a bug in gnome-display-properties but it is a bug in libxrandr.

Changed in libxrandr:
status: Invalid → New
Revision history for this message
onli (onli) wrote :

Wanted to add that this is a serious bug (think it's the same, correct me if not) if you want to use a small windowmanager like icewm, cause there is no gnome-display-properties. So you have to run xrandr manually to fix this - not everyone knows this, not every windowmanager likes it. Using Modelines and deleting unwanted Modes, which was in the past the best method, has no effect on the startup of the XServer anymore, even if the Modeline is later available via xrandr.

Revision history for this message
Matthew Koyle (mgkoyle) wrote :

It may not be helpful at all, but I was having a similar problem and had to change a line in xorg.conf which you may or may not have. Honestly, I don't know how the line got there (I suspect it appeared during the Hardy install, but I am not sure).

Anyway, my GDM resolution should have been 1280x1024 but my greeters did not appear properly. Rather, it looked as though the greeter was stretched to 1600x1200 and I could not see the bottom and right sides of the greeter. In my xorg.conf I had a line in the screen section:

 virtual 1600 1200

Changing that line to 1280 1024 fixed the GDM greeter resolution problem for me. Is there any possibility these are related? Good luck.

Do you have a modified xorg.conf? If you don't, another solution which appears to fix the gdm greeter problem is to generate a new generic xorg.conf using

sudo dpkg-reconfigure -phigh xserver-xorg

Sorry if this isn't at all related. It seems similar to my problem, though so I thought I would chime in. Good luck.

Revision history for this message
Jakub (buufy) wrote :

I have a similar problem. I'm using external monitor (native res. 1280x1024) connected via DVI to my laptop (native res. 1280x800).

When I start GDM and login to the X without external monitor connected, everything is ok (both screens have their native resolution).
When I start GDM, when the external monitor is plugged in, GDM detects wrong resolution (1152x864) and when I log to the X, the resolution is still 1152x864.

xrandr -q detects my external monitor correctly, but sets the resolution to 1152x864 instead of 1280x1024.
Running xrandr --output TMDS-1 --fb 1280x1024 doesn't help. The same goes for setting virtual 1600 1200 in xorg.conf.

The only workaround I found is to unplug the external monitor before GDM starts and plug in the monitor after I log in to the X.

I don't use dual screen, laptop lid is closed when I use external monitor.

Any ideas how to fix this? Should I provide some more information (like xrandr -q or xorg.conf listing)?

Revision history for this message
Jakub (buufy) wrote :

I have realized, that my issue is not related to GDM, rather with X detection of my monitor. But it should be related to libxrandr (if I understand it well).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.