Bug #1150 - screen lock doesn't engage if in client screen

Status:

Invalid

Priority:

Normal

Assignee:

None

Category:

None

Target:

None

Found:

None

Created by:

Issue Importer

Created on:

7 Apr 2006 14:49

Updated by:

None

Updated on:

20 Sep 2010 22:25

Platform:

None

Google ID:

sf-146

Redmine ID:

1182

SourceForge user: bwirtz

I have a synergy server on a Red Hat with the KDE
desktop. The client is a windows XP machine. When the
mouse cursor is in the client screen & the KDE desktop
lock starts, nothing happens. Both screens remain
visible and unlocked.

However, there is a kdesktop_lock process running. I
need to kill that process to be able to lock the
screen. Note that the locking works just fine if I do
it manually, or the screensaver timeout happens when
the mouse cursor is in the server screen.

Thanks,

20 Apr 2006 17:14: Issue Importer wrote a comment.

SourceForge user: xxvelcrar

Logged In: YES
user_id=178196

I believe this is due to the keyboard lockout feature of the
screen lock. Most of the screen lockers I've seen require
the ability to steal the keyboard focus - which synergy
apparently keeps to itself.

try doing this:

on the server run in a terminal:

$ sleep 5; gksudo ls

and then move the cursor to the client screen within 5
seconds. gksudo should then pop up an error saying that it
can't get the keyboard focus and that something may be
stealing your keypresses (synergy ;-) ).

20 Sep 2010 22:25: Nick Bolton changed Status.

New Invalid

20 Sep 2010 22:25: Nick Bolton wrote a comment.

Closing this bug report since it is more than 2 years old. If this is still a valid bug, please request that it be reopened on the mailing list.

Write comment

Synergy

Bug #1150 - screen lock doesn't engage if in client screen