Screen resolution settings lost after reboot

[Martin Handl]

By default after installation, the screen resolution on Radeon 8500 with 17"
minitor is 1200x1024@60Hz.
I modified resolution to 1152x867@75hz and also checked option Make Default for
this computer.
After reboot of PC the resolution is defaulted back to 1200x1024@60Hz and change
is lost.

Kernel used by default 2.6.10-4-386
Reproduced on 2.6.10-4-k7.

HW Config:
MB: ASUS A7V8X-X
RAM: 1GB DDR 266
CPU: Athlon XP 1800
VGA: ATI Radeon 8500 64 MB

http://bugzilla.gnome.org/show_bug.cgi?id=310358: http://bugzilla.gnome.org/show_bug.cgi?id=310358

[Sebastien Bacher (seb128)]

are you using warty or hoary ? how do you change the setting ? how do you reboot ?

[Martin Handl (handl)]

(In reply to comment #1)
> are you using warty or hoary ? how do you change the setting ? how do you reboot ?

I'm using latest Hoary 5.04.
I used the "Screen Resolution" utility from the menu.
I use "Logout" from the menu with restart by default,
and I tried "sudo init 6" couple of times.

[Sebastien Bacher (seb128)]

what do you have in gconf-editor, /desktop/gnome/screen ?

[Martin Handl (handl)]

The sub-tree desktop->gnome->screen->merlin->0
contains these two fields:
rate:75
resolution:1152x864

note: merlin is name of the PC.

however the real resolution is 1280x1024@60Hz.

[Sebastien Bacher (seb128)]

what resolution is displayed in the dialog to change the screen resolution
(system, preferences, screen resolution) ? does changing it here works ? does it
update the gconf settings ?

[Martin Handl (handl)]

When I modify the settings via screen resolution utility.
The change seems to be propagated correctly into the gconf settings.

Right after the change, the screen resolution is set to what I selected from the
offered choices.
After system restarts, the values within gconf settings are set to whatever I
choosed before,
but screen resolution is still 1280x1024@60Hz.

[Matthew Lenz (matthew-nocturnal)]

please don't let this bug make it into the final release. I'm still
experiencing this with Hoary 5.04 RC (fully dist-upgrade as of tonight). The
installer sets your default resolution to the absolute max the monitor supports.
 In my case this is in the 1900+xwhatever and thats freakin high, makes the
fonts impossible to read. I went in and changed the setting to 1280x1024 and it
made the change immediately. rebooting (or restarting the xserver) and it goes
right back to the highest res.

[TM (junkmail-media)]

I think I'm seeing the same bug in a different form. My screen resolution was
fine until about two weeks after an upgrade, at which point it dropped down to
1024x768. System->Preferences->Screen Resolution still has all my usual screen
resolutions listed, but switching to any of those higher than 1024x768 causes
the screen to wrap around itself. My /etc/X11/xorg.conf file seemed to have
been replaced with a new one during an upgrade. The new xorg.conf file didn't
carry over my previous screen resolutions, but the System->Preferences->Screen
Resolution application remembered them. I manually added screen resolution
settings to xorg.conf and rebooted. This seems to have fixed the problem.

[Martijn Brouwer (e-a-m-brouwer)]

I have the same problem as the original poster.

When X is started (gdm)
Gconf setting: resolution: 1400x1050, rate: 85
actual setting: resolution 1600x1200, rate: 75

When I correct this using Preferences Menu and restart gdm, the situation is the
same. Gconf has the right settings but X is wrong. Gdm seems not to read gconf
but only xorg.conf.
The latter contains the following line in my case:
Modes "1600x1200" "1400x1050" "1280x1024" "1280x960" "1024x768"
"832x624" "800x600" "720x400" "640x480"

[Sebastien Bacher (seb128)]

*** Bug 16694 has been marked as a duplicate of this bug. ***

[jon_gunnar (jonrue)]

Is this bug really still active? I have tried everything I can think about on
two separate machines.

HW Config:
MB: ASUS A8N-SLI Deluxe
RAM: 1GB
CPU: Athlon 64 3500+

Ubuntu 5.04 and kernel 2.6.10-5-386

[Sebastien Bacher (seb128)]

I've forwarded the issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=310358

I think it's specific to the "Make the default for this computer only" option.
Do you have the issue if you don't select that?

[Sebastien Bacher (seb128)]

fixed upstream

[Sebastien Bacher (seb128)]

This upload fixes the issue:

 gnome-session (2.11.91-0ubuntu1) breezy; urgency=low
 .
   * New upstream version:
     - Fix rendering of splash screen text (Ubuntu: #13093).
     - Fix RandR support to correctly use host settings (Ubuntu: #7494).