Bug 149383

Summary:	wish for customizing screensaver wakup signal
Product:	[Plasma] plasma4	Reporter:	Elmar Stellnberger (AT/K) <estellnb>
Component:	screensaver overlay	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	chanika, chaofeng111, iremyuruk
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Elmar Stellnberger (AT/K) 2007-08-30 12:08:37 UTC

Version:           Unbekannt (using KDE 3.5.7 "release 69.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.27-0.9-default

KDesktop offers a lot of options to configure the screensaver.
Notwithstanding there is no way to customize possible wakup events. 
At me the slightest vibration can cause the mouse to send a signal and thus to quit the screensaver so that activating the screensaver has no effect. Especially when using a notebook on a slanted table (Schrägtisch) there is absolutely no way to make use of the screensaver because the mouse will always keep moving.
  Why not allow to set a threshold or disable mouse triggered wakeups at all (keyboard-only-wakeup)?

Comment 1 Nate Graham 2018-06-08 20:06:30 UTC

Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham