4bf0836eae
It was doing that already if started through synergy but not if started by something outside of synergy. In particular, if you use `xscreensaver-command --activate' synergy used to send fake mouse motion events every 5 seconds to deactivate it. That's unlikely to be what the user wanted, especially if the locking is enabled since it would force the password dialog to appear. As before, it's recommended that client screens not use locking because xscreensaver will not deactivate without getting a password even if we make the request through a programmatic interface. Presumably that's for security reasons but it makes life harder for synergy. |
||
|---|---|---|
| .. | ||
| arch | ||
| base | ||
| client | ||
| common | ||
| http | ||
| io | ||
| mt | ||
| net | ||
| platform | ||
| server | ||
| synergy | ||
| Makefile.am | ||