|
We are running Linux (Centos 5.5) in a 32 bit architecture. We have had great success with version 1.3.1 in that the cursor properly moves between screens and the keyboard/clipboard properly transverses between screens. Unfortunately when we tried to move to later versions (i.e. 1.3.4, 1.3.6 and even 1.4.2) they all had the same symptoms in that the server and client initially connect and the mouse moves properly between screens but as soon as the keyboard is touched while in a focused window on the client side, the system locks up (i.e. the server no longer honors requests and the client keeps trying to reconnect). What gives? Are we locked into 1.3.1 forever? |
|
For now, the workaround on RHEL5 seems to be either to: A) drop by back 1.3.1 server B) use the --no-xinitthreads on Syngerys 1.3.6 or newer. I see lots of comments on this for various bugs. Too bad we can't have Synergys note this on startup. Or have it mentioned in the docs more clearly. John Oh yeah! I forgot about writing that feature, ha. I'll update the user FAQ.
(03 May '11, 15:05)
nbolton ♦♦
|
|
Could be a bug. Possibly related:
Update:As l8gravely points out, there is a work around for this. I forgot about writing this feature, sorry about that! It sounds our symptoms are the same as stated in Bug #1795 and #233, except that we are running CentOS 5.5 on both the server and the client. There are no windows machines in our set-up/environment. Actually Bug #1795 stated that their work-around was to swap the roles and made Windows machine as the server and made the RHEL machine the client, but we have Centos 5.5 on both machines..., so that workaround probably won't work for us. So is this just a Centos 5.5/RHEL as a Synergy server issue? We would like to stay current to have all the latest fixes/features.
(22 Apr '11, 11:31)
Hoser
So, are you saying that it's a new issue? Are you able to find the bug by searching? http://synergy-foss.org/search
(22 Apr '11, 11:35)
nbolton ♦♦
Apparently multiple users are reporting this problem in different ways, as Bug #339 is also related. So I guess it's an old issue that was introduced after build 1.3.1. The common thread in all of these Bug reports is that when RHEL or Centos is the Synergy server, any keyboard entry on the client side causes the server to hang.
(22 Apr '11, 13:59)
Hoser
|