You are not logged in.

#1 2011-05-16 08:47:26

lswest
Member
From: Munich, Germany
Registered: 2008-06-14
Posts: 454
Website

[SOLVED] Xscreensaver-command -lock no longer working

As of yesterday afternoon (probably after the upgrade to 5.13-1), I have been unable to lock my monitor using xscreensaver.  The screen fades to black, only to jump back to my desktop, and xscreensaver reporting a crash.  I honestly can't see a reason from the log file, but I have little experience with programs like this.  I would greatly appreciate it if someone could either confirm/let me know it's a bug that has no workaround, and I'll gladly report the bug. 

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.

Last edited by lswest (2011-05-20 20:51:32)


Lswest <- the first letter of my username is a lowercase "L".
"...the Linux philosophy is "laugh in the face of danger". Oops. Wrong one. "Do it yourself". That's it." - Linus Torvalds

Offline

#2 2011-05-16 15:11:00

_djm_
Member
Registered: 2009-11-30
Posts: 30
Website

Re: [SOLVED] Xscreensaver-command -lock no longer working

I also get a similar error - I sent a bug report.

Offline

#3 2011-05-18 06:53:29

darthyorik
Member
Registered: 2010-10-16
Posts: 1

Re: [SOLVED] Xscreensaver-command -lock no longer working

I have the issue as well.

Edit: For now, I've downgraded as well. I need this to work for security reasons.

Last edited by darthyorik (2011-05-18 09:46:13)

Offline

#4 2011-05-20 20:40:36

Painless
Member
Registered: 2006-02-06
Posts: 177

Re: [SOLVED] Xscreensaver-command -lock no longer working

If you stop using blank-only mode, it should work.

Offline

#5 2011-05-20 20:50:53

lswest
Member
From: Munich, Germany
Registered: 2008-06-14
Posts: 454
Website

Re: [SOLVED] Xscreensaver-command -lock no longer working

It does indeed work after disabling blank only.  Hopefully the blank only functionality will return in the future, but it's working now, so I'll mark this as solved.

Thanks!


Lswest <- the first letter of my username is a lowercase "L".
"...the Linux philosophy is "laugh in the face of danger". Oops. Wrong one. "Do it yourself". That's it." - Linus Torvalds

Offline

#6 2011-05-21 07:57:28

Proofrific
Member
Registered: 2008-01-05
Posts: 196

Re: [SOLVED] Xscreensaver-command -lock no longer working

Painless wrote:

If you stop using blank-only mode, it should work.

That fixed it for me, too. Thanks!

Offline

Board footer

Powered by FluxBB