Screen Resolution: "Use previous settings" fails

[Jonas Alves]

TESTCASE:

- start a session which has no xrandr capplet configuration
- use the display configuration tool; change the settings
- click on the button to use the previous configuration

the jaunty version displays an error, the update not

[Dwight Shepherd (dwight-shepherd)]

I had this problem too initially but when i ran it the second time it started working.

Is this the same experience for you?

[harry paterson (hpaterson)]

How can I set the screen resolution of the latest Ubuntu release
higher than 900 x 600 ?

[Jonas Alves (jonasfa)]

Oh my god! xD

You're right.. I tried it again and now it's working..
But why? There wasn't any update since the release o.O

On Thu, May 1, 2008 at 7:56 PM, Dwight Shepherd <email address hidden>
wrote:

> I had this problem too initially but when i ran it the second time it
> started working.
>
> Is this the same experience for you?
>
> --
> [hardy] screen resolution: "Use previous settings" fails
> https://bugs.launchpad.net/bugs/222297
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonas Alves
<email address hidden>

[Andreas Gustafsson (gson)]

I can confirm the reported behavior of the display failing to return to its original
resolution after a 20-second timeout. I can't say what happens if you click
on a button in the dialog, because when I have changed the resolution,
my screen is garbled because of bug #138087 such that I can't see any
buttons to click.

In combination, these two bugs (#138087 and #222297) mean that if I
make any attempt to change the resolution, my screen ends up garbled
and I have no way to recover other than killing the X server or rebooting.

[Brian Chidester (brianchidester)]

Also shows up in Intrepid and hardy releases provided by the OEM team. However I am not seeing the action where the second time it works. I have seen this since the first install from a canonical provided cd. Using my QA title to mark as confirmed.

[harry paterson (hpaterson)]

My problem is that sometimes I can set the screen resolution to 1024 and
the next time I boot
that resolution is not available in the resolution settings and it
defaults to 900 x 600 and
sometimes when I boot again it is back to 1024 ??

Harry Paterson

[Andreas Gustafsson (gson)]

I tried the jaunty alpha 5 i386 desktop live CD, and the bug is still there: after a resolution change, if you do not confirm the new resolution and let the countdown run its course, the screen still does _not_ return to its original resolution.

[Sebastien Bacher (seb128)]

reassigning to correct component that's a gnome-control-center tool, it does switch back to the previous configuration correctly on my jaunty installation not confirming the issue

[Ludovico Cavedon (cavedon)]

I confirm this issue on Jauty.
How to replicate:
1) remove ~/.config/monitors.xml
2) run gnome-display-manager
3) change the settings
4) click on "use previuos settings"

It will fail trying to
mv ~/.config/monitors.xml.backup ~/.config/monitors.xml

Because the first time you started it has no configuration saved.

Proposed fix: save current config if it does not exist when starting gnome-display-manager

[Sebastien Bacher (seb128)]

The current comment suggests that the issue is similar to http://svn.gnome.org/viewvc/gnome-settings-daemon?view=revision&revision=802 which has been recently fixed to svn

[Sebastien Bacher (seb128)]

the commit on http://svn.gnome.org/viewvc/gnome-settings-daemon?view=revision&revision=800 describes that too

"(RANDR) - Handle the case where no backup file was created for monitors.xml, because *that* file didn't exist (such as on a first-time login)"

the fix will be in GNOME 2.26.1 and jaunty

[Martin Pitt (pitti)]

Accepted gnome-settings-daemon into jaunty-proposed-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Sebastien Bacher (seb128)]

could somebody who was having the issue confirm that the update is working so it can be moved to official updates?

[Pedro Villavicencio (pedro)]

I've managed to reproduce the bug with the steps described on https://bugs.edge.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/222297/comments/10 ; the proposed version works fine though and it doesn't display the error. Bug is fixed there, marking this as verification done. thanks.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-settings-daemon - 2.26.1-0ubuntu1

---------------
gnome-settings-daemon (2.26.1-0ubuntu1) jaunty-proposed; urgency=low

  * New upstream version:
    - Fix crash when closing the lid on some laptops (lp: #349628)
    - Fix crash when closing a11y notification bubble
    - Fix problems with saving/restoring screen setup (lp: #222297)
    - Make the screen resolution confirmation dialog always appear in front of
      the settings window (lp: #360084)
    - Increase confirmation timeout to 30 seconds to give slower devices (like
      projectors) time to adjust (lp: #355912)
    - Avoid some GConf roundtrips
    - Build fixes
  * debian/patches/06_undo_build_change.patch:
    - the issue is fixed in the new version
  * debian/patches/07_use_gstreamer_volume.patch,
    debian/patches/90_autoreconf.patch:
    - new version update

 -- Sebastien Bacher <email address hidden> Wed, 22 Apr 2009 11:15:29 +0200

[Martin Pitt (pitti)]

Copied to karmic as well.