Bug 276205

Summary:	Cannot lock screen via Menu, screen timeout or keyboard shortcut.
Product:	[Unmaintained] kscreensaver	Reporter:	Emmett Culley <lst_manage>
Component:	locker	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	mgraesslin, pskopek, rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Emmett Culley 2011-06-21 18:12:58 UTC

Version: unspecified (using KDE 4.6.3)
OS: Linux

Only the command: /usr/libexec/kde4/kscreenlocker --forcelock will lock the screen. After returning to desktop I see the following after the commandline that locked the screen:
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2 (X_ChangeWindowAttributes)
Resource id: 0x640001e

This is on a machine (nVidia graphics) the an upgrade to Fedora 15 via DVD failed. After fresh install and copying home directory from original Fedora 14 machine I found screen loc did not work.

On other machine (Dell laptop AMD video) where upgrade via DVD worked, the screen lock works as expected.

Reproducible: Always

Steps to Reproduce:
Click on Leave | Lock menu item, press ctl-alt L, or wait for configured timeout. No screen lock. Or blank screen at timeout, for that matter.

Only command /usr/libexec/kde4/kscreenlocker --forcelock blanks screen and requires password.

Actual Results:
No screen lock. Or blank screen at timeout, for that matter.

Only command /usr/libexec/kde4/kscreenlocker --forcelock blanks screen and requires password.

Expected Results:
Screen to blank and require password to use desktop

This is on a machine (nVidia graphics) where an upgrade to Fedora 15 via DVD failed. After fresh install and copying home directory from original Fedora 14 machine I found screen loc did not work.

On other machine (Dell laptop AMD video) where upgrade via DVD worked, the screen lock works as expected.

When I first noticed this I did a little researh and fourn the command line method. After trying that method the normal screen lock feature worked, until I logged out again. Now, even logging out and back in, only the commandline method works.

Comment 1 Emmett Culley 2011-09-04 23:17:13 UTC

Still having this problem.  Since I am the only one that reported I assume it is exclusive only to this machine and not a bug at all.  At least not a KDE bug.

Still, I'd like to know where to look:  Again, this is the command line and th resultanet output that does lock the screen:

[emmett@ws1 ~]$ /usr/libexec/kde4/kscreenlocker --forcelock
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode: 2 (X_ChangeWindowAttributes)
  Resource id:  0x680001e
Authentication failure

I don't know if the output happen when I unlock or right after I run the command, or as the screen is locked.

Comment 2 Peter Skopek 2012-05-04 13:58:55 UTC

After today's update of F16 with KDE I see the same symptoms.
The day before lock screen was working fine.
May 4, 2012

Comment 3 Martin Flöser 2015-01-23 14:43:25 UTC

The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.