nvidia-settings X display configuration window doesn't work on nvida-280.13

[Zeus]

nvidia-settings gives this error when X-Servier Display Configuration is clicked similar to bug 539196 logged for Lucid

Unable to load X Server Display Configuration page:

Failed to query NoScanout for screen 0.

zeus@Pandion:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu oneiric (development branch)"
zeus@Pandion:~$ ubuntu-bug nvidia-settings

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nvidia-settings 280.13-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Aug 26 09:50:42 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-settings
UpgradeStatus: Upgraded to oneiric on 2011-08-13 (12 days ago)

[Zeus (zeus-jay)]

zeus@Pandion:~$ sudo apt-cache policy nvidia-current
nvidia-current:
  Installed: 280.13-0ubuntu1
  Candidate: 280.13-0ubuntu1
  Version table:
 *** 280.13-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/restricted amd64 Packages
        100 /var/lib/dpkg/status

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nigel Charman (online-charman)]

I had this problem after upgrading to 11.10. Resolved by updating the driver from 173 to "version current" as per http://ubuntuforums.org/showthread.php?t=1400792.

[Bryce Harrington (bryce)]

Hey zeus-jay,

Hi, thanks for reporting this issue during the development period of
Ubuntu.

I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?

Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.