[hardy] [regression] gnome-settings-daemon update gives 400x300 resolution after login

xrandr

Screen 0: minimum 320 x 240, current 400 x 300, maximum 1024 x 768
default connected 400x300+0+0 0mm x 0mm
   1024x768 60.0
   800x600 60.0 56.0
   640x480 60.0
   640x384 60.0
   576x384 55.0
   512x384 60.0
   400x300 60.0* 56.0
   320x240 60.0

Running gnome failsafe the same resolution change happens after login. The gdm screen is fine, which makes me wonder if this is actually X.

Last xorg update was on 2008-02-28. 1:7.3+10ubuntu6

It looks like the messages in .xsession-errors are coming from randr (http://www.gnome.org/~ssp/randr/monitor-db.c)
http://www.redhat.com/archives/fedora-extras-commits/2008-February/msg03908.html

The xrandr changes I think date from gnome-desktop (1:2.21.92-0ubuntu2) hardy; urgency=low
upload redhat xrandr changes to hardy
http://changelogs.ubuntu.com/changelogs/pool/main/g/gnome-desktop/gnome-desktop_2.21.92-0ubuntu3/changelog

I've looked at dpkg.log on the affected machine and the only relevant looking updates during the time period are:

gnome-session 2.21.93-0ubuntu1
gnome-settings-daemon 2.21.92-0ubuntu 1
libgnomeui-0 2.21.93-0ubuntu1

There have been NO changes in X.

The change in resolution happens about half a second after the password is accepted. I get a 1024x768 brown screen (no wallpaper) and then the resolution changes. The rest of the desktop then loads in a 400x300 rectangle.

gnome-session (2.21.93-0ubuntu1) hardy; urgency=low

  * New upstream version:
    Misc
    - Remove hard dependency on esound, this is handled by
      gnome-settings-daemon now
    Session Manager
    - Don't start the sound server, and play the login sound when
      gnome-settings-daemon tells us the sound server has started
  * debian/patches/90_from_svn_gsd_starts_esd.patch:
    - dropped, fixed in the new version
  * debian/patches/70_autoreconf.patch:
    - new version update

 -- Sebastien Bacher <email address hidden> Sat, 08 Mar 2008 14:57:56 +0100

gnome-settings-daemon (2.21.92-0ubuntu1) hardy; urgency=low

  * New upstream version:
    - Only print debug messages if --debug is used
    - Only load plugins when requested not at every start
    - Fixed #515340, Add a way to prioritise plugin load
    - Fixed #515341, Signal when plugins finish loading
    - Fixed #517259, Escape hostname for use in gconf key
    - Fixed #517418, gnome-display-properties resolution change
      will not be used after logout or reboot (lp: #191878)
    - Fixed #518075, Sound plugin should start pulseaudio itself
  * debian/patches/90_from_svn_pulseaudio_correct_use.patch:
    - dropped, fixed in the new version
  * debian/patches/92_gsd-xrandr-version-check.patch:
    - fix type which was breaking the build

 -- Sebastien Bacher <email address hidden> Sat, 08 Mar 2008 14:13:51 +0100

I strongly think one of these two updates has caused this issue.

debian/patches/92_gsd-xrandr-version-check.patch

Would be the likely culprit there.

I am closing the Trident driver. Thanks for pointing it out. Could you please post your output of xrandr?

xrandr is attached above (as a comment as it's small)

Sorry I have read over it.
What happens if you change your resolution with System - Preferences - Screen Resolution? Does it still show the correct resolution after X logout and relogin?
Maybe your wrong resolution happens because of changes in the gnome-display-properties.

I can't actually change the settings in Screen Resolution as the
window is too small. Is there another way of altering it?

You can run "xrandr --auto" in Gnome console. This should change the resolution to 1024x768 so you can use the gnome-display-properties tool. xrandr changes aren't saved so the GUI tool have to be used afterwards.

That had no effect. I tried xrandr --fb 1024x768 as well. I restarted
X as well and no change.

My fault it should be "xrandr --output default --auto".

No effect.

What's with "xrandr --output --default --mode 1024x768" ? Of course you have to remove the " from the command.

Last command was wrong, please use:
xrandr --output default --mode 1024x768

That worked - thanks!

I've rebooted and it's all fine now :)

Closed according to user comment.