Bug #34 - Wrong behaviour with xscreensaver (server linux, client windows)

Status:

Accepted

Priority:

Normal

Assignee:

None

Category:

None

Target:

None

Found:

None

Created by:

Issue Importer

Created on:

30 Mar 2009

Updated by:

None

Updated on:

13 Jan 2011 16:34

Platform:

None

Google ID:

gc-25

Redmine ID:

Google user: jul.gil

(synergy 1.3.1 on Linux and Windows)

When xscreensaver is activated on the server, the client session under Windows launches his
screensaver, and then stops it quickly.

I think that there is problems on both sides...

The server detects the activation, and immediatly a deactivation, the death of the xscreensaver
window, and again an activation. Then 3 events are sent to the clients, to start, stop and then
start the screen saver.

DEBUG: CXWindowsScreenSaver.cpp,194: xscreensaver activated
DEBUG: CXWindowsScreenSaver.cpp,390: xscreensaver activated on window 0x00c010d0
DEBUG: CXWindowsScreenSaver.cpp,204: xscreensaver deactivated
DEBUG: CXWindowsScreenSaver.cpp,390: xscreensaver deactivated on window 0x00c010d0
DEBUG: CXWindowsScreenSaver.cpp,174: xscreensaver died
DEBUG: CXWindowsScreenSaver.cpp,345: xscreensaver window: 0x00000000
DEBUG: CXWindowsScreenSaver.cpp,345: xscreensaver window: 0x00c01151
DEBUG: CXWindowsScreenSaver.cpp,390: xscreensaver activated on window x00c01151
DEBUG1: CXWindowsUtil.cpp,1738: ignoring X error: 3
DEBUG1: CXWindowsUtil.cpp,1738: ignoring X error: 3
DEBUG: CServer.cpp,1456: onScreenSaver activated
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcjgilles2" on=1
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcwin" on=1
DEBUG: CServer.cpp,1456: onScreenSaver deactivated
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcjgilles2" on=0
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcwin" on=0
DEBUG: CServer.cpp,1456: onScreenSaver activated
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcjgilles2" on=1
DEBUG1: CClientProxy10.cpp,359: send screen saver to "pcwin" on=1

On the client side the 3 events are received :

DEBUG1: recv screen saver on=1
DEBUG1: recv screen saver on=0
DEBUG1: recv screen saver on=1

But the second on=1 is not taken in account, the screen saver just flashes.

I think that there is something misunderstood between synergys and xscreensaver - perhaps there
is another way to detect the activation of the screensaver. Neverless the client should behaves
according the events received, and finally starts the screensaver.

27 May 2009: Issue Importer changed Status.

New Accepted

27 May 2009: Issue Importer changed Target.

27 May 2009: Issue Importer changed Found in ver.

1.3.2

27 May 2009: Issue Importer wrote a comment.

Google user: nick.bolton.uk

jul.gil, thanks for the bug report and log data. I have marked this as accepted.

27 May 2009: Issue Importer wrote a comment.

Google user: nick.bolton.uk

27 May 2009: Issue Importer wrote a comment.

Google user: nick.bolton.uk

9 Jun 2009: Issue Importer wrote a comment.

Google user: malvineous

Oh, I've often wondered about this. I always though it was just chance, I didn't
realise Synergy had screensaver synchronisation because it has never worked for me!
(Same setup, Linux server and Windows client.) Now I know what causes the flashes on
the Windows PC. Normally I just lock both PCs manually.

24 Jul 2009: Issue Importer changed Target.

? ?

24 Jul 2009: Issue Importer wrote a comment.

Google user: nick.bolton.uk

5 Jun 2010: Issue Importer changed Target.

? ?

5 Jun 2010: Issue Importer wrote a comment.

Google user: nick.bolton.uk

13 Jan 2011 16:34: Nick Bolton changed Target.

Write comment