gnome-display-properties applies resolution changes without a timeout box

[Adam Buchbinder]

Binary package hint: gnome-control-center

Run gnome-display-properties. Pick a different resolution. Click "apply".

What I expected: I expected a confirmation dialog with a countdown to appear, saying that I should click "OK" if my monitor was displaying the resolution. (More accurately, since the resolution I picked was out of range, I expected that my monitor would snap back to the old resolution eventually.)

What happened: My monitor proceeded to display the "Invalid Resolution" message for quite some time. I did a CTRL-ALT-Backspace, and tried to log back in, to discover that the invalid resolution was now part of my user profile, making my account nigh-unusable.

Compounding this problem was the fact that "failsafe" mode doesn't reset resolution changes; I ended up creating another user account from the xterm-only login, logging in there, and trying to find any reference to ways to change the mysterious setting which wasn't in .gnome or .gconf and wasn't affected by logging in as failsafe, but *was* affected by logging in as "terminal only".

(For some reason, I found a forum post rather than https://wiki.ubuntu.com/X/Config/Resolution, but eventually I deleted .config/monitors.xml. In any case, this is hardly bulletproof, and I'll file a bug on whatever makes failsafe configurations as soon as I find out what component it is. Aren't we supposed to have "bullet-proof X"?)

I don't think this is a dupe of bug 197673, since that was about randr changes, while this is just about screen-resolution changes. If it *is* a dupe, please just reopen that one.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: gnome-control-center 1:2.24.0.1-0ubuntu7.1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
SourcePackage: gnome-control-center
Uname: Linux 2.6.27-7-generic i686

[Sebastien Bacher (seb128)]

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