GUI problem

[D]

To reproduce:
while changing screen resolution, during prompt to keep resolution or automatically revert, attempt to change the resolution again before selecting option. "Counter until revert" will continue into the negative and window will be unclosable via gui.

Description: Ubuntu precise (development branch)
Release: 12.04

What i expected to happen: Unclickable outside of keep or revert resolution
What happened: See above

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
.tmp.unity.support.test.0:

ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,regex,grid,resize,gnomecompat,snap,place,vpswitch,mousepoll,animation,move,session,imgpng,wall,expo,workarounds,unitymtgrabhandles,fade,ezoom,scale,unityshell]
CompositorRunning: compiz
CurrentDmesg:

Date: Thu Mar 8 17:32:10 2012
DistUpgraded: Log time: 2012-03-07 18:30:05.370545
DistroCodename: precise
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff60]
MachineType: TOSHIBA Satellite A305D
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=33130eed-7ddd-40ac-ac2f-b98a3550f240 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago)
dmi.bios.date: 07/07/2008
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: ATI Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr1.60:bd07/07/2008:svnTOSHIBA:pnSatelliteA305D:pvrPSAH0U-00S007:rvnATICorp.:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite A305D
dmi.product.version: PSAH0U-00S007
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Sebastien Bacher (seb128)]

Thank you for your bug report, what do you mean "attempt to change the resolution again before selecting option."? why attempt? do you validate the choice?

[D (therealcrocus)]

Thanks for replying. Forgive my poor English.

I'm referring to the menu that has a dropdown to select another resolution. Once another resolution is selected and the resolution changes a dialogue pops up and asks if you want to keep these settings or revert to the previous resolution. If you select neither option and instead select another resolution from the dropdown menu you get the behavior noted above.

Why do this? To mess with it deliberately or perhaps laziness on the user's end.

Once you do that you cannot select any option from the popup dialogue, nor does it close. It just remains onscreen and the count continues into the negative.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Robert Roth (evfool)]

I have managed to reproduce using the steps described, and it seems to be an upstream issue.