Bug 225216 - Display KCM module does not revert to old resolution on non-confirmation
Summary: Display KCM module does not revert to old resolution on non-confirmation
Status: RESOLVED DUPLICATE of bug 222110
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-02 00:31 UTC by Roger Pixley
Modified: 2010-02-02 00:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Pixley 2010-02-02 00:31:50 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Version:           KDE Development Platform: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2))
System Settings: 1.0 (using Devel)
OS:                Linux
Installed from:    Ubuntu Packages

The Display KCM module for Size and Orientation allows you to change the screen
size and apply it. This will change the screen to a new resolution and then
open a dialog box to ask if this appropriate with a countdown

Reproducible: Always

Steps to Reproduce:
Open the display section of System Settings. Set a new resolution and click apply. Note that the highlighted option is not Revert to Old Configuration. Wait till the timer runs out. Stay with the new resolution that you set despite the Dialog saying it would be reverted.
Actual Results:  
I have the resolution that I had selected and applied but never confirmed.

Expected Results:  
I should not have the resolution that I selected. I should have the resolution that I had prior to my selection

I saw that the Keep Resolution option was selected which I thought was distinctly wrong since if the screen was blank and I started pressing buttons it would keep the system with an unsuable resolution setting.
Comment 1 Christoph Feck 2010-02-02 00:37:43 UTC

*** This bug has been marked as a duplicate of bug 222110 ***