Bug 142308

Summary:	x11vnc dpms internal X screensaver activates incorrectly
Product:	[Unmaintained] kdesktop	Reporter:	Paul B. Henson <henson>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	faure, finex, firew4lker, melendro
Priority:	NOR	Keywords:	needs_verification, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Paul B. Henson 2007-02-28 03:41:55 UTC

Version:            (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
OS:                Linux

When using x11vnc to remotely control a KDE 3.5.5 desktop using the option to force DPMS mode on the console monitor to try and prevent snooping of the session, the built in X screensaver continuously activates. This misbehavior is similar to the problem reported in bug 134765; however, in that bug they claim that the KDE screensaver is kicking in, and indicate they think the problem lies in kdesktop_lock. The problem I am reporting involves the built in X screensaver (with the floating X logo), and has nothing to do with kdesktop_lock.

I tracked this problem down to revision 581777 of kdebase/kdesktop/lockeng.cc, which basically appears to change all invocations of XSetScreenSaver to explicitly indicate "DontPreferBlanking", whereas the previous revision used whatever the default was.

After recompiling 3.5.5 with this one delta removed, the problem goes away. Also, as far as I can tell the screensaver continues to work perfectly fine, coming on when manually requested, and automatically after the configured idle time, as well as powering down as configured. I'm not sure what bug this change fixes, but the breakage to x11vnc is somewhat annoying.

Any chance of either removing this delta or reworking it to be x11vnc/dpms compatible?

Thanks much...

Comment 1 FiNeX 2008-12-10 02:46:40 UTC

Is this still an issue on KDE 4?

Comment 2 Paul B. Henson 2009-01-08 00:51:16 UTC

Seems to work fine on KDE 4.

Comment 3 FiNeX 2009-01-08 11:24:46 UTC

Thanks. I'm closing the bug with "unmantained" because:
1) the problem will not be fixed even on KDE3 (it is unmantained)
2) it ha not been inherited by KDE4 :-)

Comment 4 firewalker 2010-02-02 23:05:41 UTC

It is still present on KDE 4 (4.3.98).

Comment 5 Melendro 2010-07-06 20:49:27 UTC

I can confirm that the problem is still here in KDE 4.4.4
Please, reopen the bug.

Comment 6 David Faure 2010-09-28 02:24:24 UTC


*** This bug has been marked as a duplicate of bug 134765 ***