[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 142308] New: x11vnc dpms internal X screensaver activates
From:       "Paul B.Henson" <henson () acm ! org>
Date:       2007-02-28 2:41:56
Message-ID: 20070228034154.142308.henson () acm ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=142308         
           Summary: x11vnc dpms internal X screensaver activates incorrectly
           Product: kdesktop
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: faure kde org
        ReportedBy: henson acm org


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...


[prev in list] [next in list] [prev in thread] [next in thread]