Version: (using KDE KDE 3.5.4) Installed from: Debian testing/unstable Packages I have configured kscreensaver to start automatically after a 5 minute delay. It works all right until I take over the desktop remotely, using the x11vnc. When viewed through vnc, when I release the mouse, the screensaver starts immediately. (It used to work all right a couple of releases back, I'm not sure when, I didn't use vnc for many months now)
Yes, I also have to disable the screensaver when I take over my home computer running x11vnc 0.8.3 remotely from work with tightvnc_viewer. I have Mandriva Linux with KDE 3.5.4. Karl Runge thinks it may be a bug in kdesktop_lock: http://www.karlrunge.com/x11vnc/#faq: Q-42: Help! x11vnc and my KDE screensaver keep switching each other on and off every few seconds. This is a new (Jul/2006) problem seen, say, on the version of KDE that is shipped with SuSE 10.1. It is not yet clear what is causing this... If you move the mouse through x11vnc the screensaver shuts off like it should but then a second or two after you stop moving the mouse the screensaver snaps back on. This may be a bug in kdesktop_lock. For now the only workaround is to disable the screensaver. You can try using another one such as straight xscreensaver. vatbier
I have traced this down to a DPMSInfo() call in the kdesktop_lock Even though there has been mouse or keyboard input to wake kdesktop_lock up and cause it to turn off the screen saver, kdesktop_lock (or a respawned process of it) checks DPMSInfo() and if it sees the Monitor is in a low power state ("standby", "suspend", or "off") it turns on the screensaver again. I'm not sure if this is the desired behavior of kdesktop_lock or not to discard the recent mouse/keyboard input information... I have put in a workaround to x11vnc for this, the -nodpms option where it will keep the Monitor in the DPMS "on" state whenever VNC clients are connected. http://www.karlrunge.com/x11vnc/#faq-kde-screensaver Karl
*** Bug 138402 has been marked as a duplicate of this bug. ***
*** Bug 136222 has been marked as a duplicate of this bug. ***
i can confirm it too, and i use kde's own vnc tools (krdc and krfb). so for now the only real fix is to revert patch like mentioned in bug 142308?
Is this still an issue on KDE 4?
As far as I can tell, it's gone. I checked it in ubuntu hardy. (It looks OK for KDE 3 also in hardy)
Actually -- what a coincidence, it's amazing -- I just had this bug with my wife's kubuntu hardy's KDE3. Not that I'll reopen this bug though, before seeing it with kde4 first.
I can confirm this bug with KDE 4.5.1 and X11VNC
*** Bug 142308 has been marked as a duplicate of this bug. ***
Bug not reproducible anymore with KDE-4.5.1 and x11vnc 0.9.9.
Oops. And on the second try the bug happened again. If I move the mouse out of vncviewer, the screensaver kicks in immediately again. However I think this is an Xorg bug more than a KDE bug. It's X which decides when to let the screensaver kick in, AFAIK.
*** This bug has been confirmed by popular vote. ***
On my system the screensaver starts as soon as I stop moving the cursor on the remote screen, moving the mouse away from it.
I confirm this with kde-4.7.4 and tigervnc-1.1.0.
Confirmed with KDE 4.9.0 and x11vnc 0.9.13. The -nodpms option of x11vnc does not solve the problem. The only workaround I've found is to disable the screensaver.
The -nodpms switch to x11vnc works great for me. Without it, the screen saver kicks in every other second, even when typing text. Client: KRDC 4.8.5 Server x11vnc version: 0.9.13 Server KDE version: 4.9.2
*** Bug 313905 has been marked as a duplicate of this bug. ***
*** Bug 147091 has been marked as a duplicate of this bug. ***
The kde 4.10 screen locker doesn't behave the same, so this shouldn't be happening any more IIRC. If anyone is encountering it on 4.10 and can reproduce it, I'd like to hear details.
given comment #20 I assume this issue to be fixed. If it still happens, please reopen.