gnome screensaver only on one screen with NVidia-9755/xinerama

[Dustin Spicuzza]

Binary package hint: gnome-screensaver

With Feisty, NVidia drivers 1.0.9755 (actually, anything above 8776 is affected) with xinerama, gnome screensaver only shows up on one screen, and does not blank the other screens. I found a recommendation to disable composite, but its still broken.

Package: gnome-screensaver
Version: 2.17.8-0ubuntu2

Error message:

random@minenotyers:~$ gnome-screensaver --debug --g-fatal-warnings
GTK Accessibility Module initialized
random@minenotyers:~$ GTK Accessibility Module initialized
The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 2114 error_code 8 request_code 78 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Also along these lines, the 'properties' page breaks also -- it shows up and quickly disappears:

random@minenotyers:~$ gnome-screensaver-preferences
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
** Message: Found best visual for GL: 0x21
The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadColor (invalid Colormap parameter)'.
  (Details: serial 255 error_code 12 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

ProblemType: Bug
Architecture: i386
Date: Sun Mar 11 17:58:59 2007
DistroRelease: Ubuntu 7.04
Uname: Linux minenotyers 2.6.20-ubuntu1-rndrnd #2 Sun Mar 11 16:58:49 EDT 2007 i686 GNU/Linux

[Greg Grossmeier (greg.grossmeier)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release?

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/

Thanks in advance!

[Dustin Spicuzza (randomperson83)]

I haven't had Ubuntu on that machine in quite awhile, mostly due to that bug. I was planning on trying again at some point, might give it a try this weekend.

[Dustin Spicuzza (randomperson83)]

FYI: I had contacted NVidia about that bug at some point, and they informed me that they were aware of it, so I'm assuming that they probably fixed it in a later release... but not sure, due to not testing it.

[Greg Grossmeier (greg.grossmeier)]

This seems to be related to another issue, bug 87317 . Both are about gnome-screensaver not acting based on information for the second monitor with nVidia drivers.

Testing with the latest development version livecd would still be a good thing to do though.

[Greg Grossmeier (greg.grossmeier)]

Is this still an issue in Hardy?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.