If you stop using blank-only mode, it should work.
That fixed it for me, too. Thanks!
]]>Thanks!
]]>Edit: For now, I've downgraded as well. I need this to work for security reasons.
]]>Things I've tried:
Re-installing 5.13-1 (no change)
Restart of system & xscreensaver (no change in either case)
Downgrade to 5.12-2 (which works, as it did before)
The log file is as follows:
##########################################################################
xscreensaver: 10:40:45: logging to "log.txt" at Mon May 16 10:40:45 2011
##########################################################################
xscreensaver 5.13, copyright (c) 1991-2008 by Jamie Zawinski <jwz@jwz.org>.
xscreensaver: 10:40:45: running as lswest/lswest (1000/101)
xscreensaver: 10:40:45: in process 12688.
xscreensaver: 10:40:46: running on display ":0"
xscreensaver: 10:40:46: vendor is The X.Org Foundation, 11001000.
xscreensaver: 10:40:46: useful extensions:
xscreensaver: 10:40:46: MIT Screen-Saver (disabled at compile time)
xscreensaver: 10:40:46: Shared Memory (1.1)
xscreensaver: 10:40:46: Double-Buffering (1.0)
xscreensaver: 10:40:46: Power Management (1.1)
xscreensaver: 10:40:46: GLX
xscreensaver: 10:40:46: XF86 Video-Mode (2.2)
xscreensaver: 10:40:46: XC Misc (disabled at compile time)
xscreensaver: 10:40:46: Xinerama (1.1)
xscreensaver: 10:40:46: Resize-and-Rotate (1.3)
xscreensaver: 10:40:46: NVidia
xscreensaver: 10:40:46: NVidia GLX
xscreensaver: 10:40:46: XInput
xscreensaver: 10:40:46: screen 0 non-colormapped depths: 0 24.
xscreensaver: 10:40:46: screens in use: 1
xscreensaver: 10:40:46: 0/0: 1680x1050+0+0 (default)
xscreensaver: 10:40:46: selecting RANDR events
xscreensaver: 10:40:46: not using XInputExtension.
xscreensaver: 10:40:46: consulting /proc/interrupts for keyboard activity.
xscreensaver: 10:40:46: 0: visual 0x21 (TrueColor, depth: 24, cmap: default)
xscreensaver: 10:40:46: 0: saver window is 0x2200001.
xscreensaver: 10:40:46: selecting events on extant windows... done.
xscreensaver: 10:40:46: awaiting idleness.
##############################################################################
xscreensaver: 10:40:54: X Error! PLEASE REPORT THIS BUG.
xscreensaver: 10:40:54: screen 0/0: 0x15d, 0x0, 0x2200001
##############################################################################
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 132 (DPMS)
Minor opcode of failed request: 6 (DPMSForceLevel)
Serial number of failed request: 655
Current serial number in output stream: 656
#######################################################################
If at all possible, please re-run xscreensaver with the command
line arguments `-sync -verbose -log log.txt', and reproduce this
bug. That will cause xscreensaver to dump a `core' file to the
current directory. Please include the stack trace from that core
file in your bug report. *DO NOT* mail the core file itself! That
won't work. A "log.txt" file will also be written. Please *do*
include the complete "log.txt" file with your bug report.
http://www.jwz.org/xscreensaver/bugs.html explains how to create
the most useful bug reports, and how to examine core files.
The more information you can provide, the better. But please
report this bug, regardless!
#######################################################################
xscreensaver: 10:40:53: LOCK ClientMessage received; activating and locking.
xscreensaver: 10:40:53: 0: locked mode switching.
xscreensaver: 10:40:53: user is idle (ClientMessage)
xscreensaver: 10:40:53: blanking screen at Mon May 16 10:40:53 2011.
xscreensaver: 10:40:53: 0: grabbing keyboard on 0x15d... GrabSuccess.
xscreensaver: 10:40:53: 0: grabbing mouse on 0x15d... GrabSuccess.
xscreensaver: 10:40:53: fading...
xscreensaver: 10:40:54: fading done.