Bug 254927

Summary:	kscreenlocker does not stop on remote desktop
Product:	kscreensaver	Reporter:	Adi Spivak <adispivak>
Component:	locker	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	drf
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Adi Spivak 2010-10-22 08:22:27 UTC

Version:           4.5 (using KDE 4.5.1) 
OS:                Linux

 have tried several vnc servers solutions and NX, however, every time i connect to the remote desktop, if i stop moving my mouse for 2 seconds the screen saver starts anew and since my screen saver is slide show, it is killing my bandwidth and it is not possible to work.
killall kscreenlocker or kill -9 <id> just create a new process with a new id.
This is probably a bug in KDE, due to the inability to detect your session via ConsoleKit, causing a infinite idle time to be assumed.
http://forum.kde.org/viewtopic.php?f=17&t=90988&sid=80c3d0cf72777b77f3d86355c9e1be5d

Reproducible: Always

Steps to Reproduce:
set screensaver to 10 minutes and password lock for 60 seconds, wait for screen saver to start and VNC or NX to the PC, stop the screensaver (with the mouse or with killall) and leave the mouse for 2 seconds.

Actual Results:  
screensaver (kscreenlocker proccess) resume inidiatly.

Expected Results:  
screensaver (kscreenlocker) should reset timer and stop.

Comment 1 Oswald Buddenhagen 2010-10-23 23:32:43 UTC

is it the screensaver that activates itself or the power management profile? we have "some" confusion in that area ...

Comment 2 Adi Spivak 2010-10-24 07:01:13 UTC

how can i verify it? 
i put the screen saver on in the monitor and screen saver dialog.
the power option should turn off the monitor after 30 minutes but nothing else that i know of.

Comment 3 Oswald Buddenhagen 2010-10-24 19:04:27 UTC

the power profiles are under hardware => power management. there is a checkbox "suspend session" and next to it a combo box which allows locking the session. make sure this is disabled.

Comment 4 Adi Spivak 2010-10-27 14:38:01 UTC

sorry for the late response.
this appears to have solved the issue.
thank you, however i still think it's a bug that they cannot live together.
either remove one or make it work.

thanks.

Comment 5 Oswald Buddenhagen 2010-10-30 11:17:18 UTC


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