Server Ubuntu 11.04 - synergy 1.3.6 , Client Mac OSX Lion - synergy 1.3.7
Issue #1: Even though I have configured synergyc to start according to MacOS method #1 in http://synergy2.sourceforge.net/autostart.html, Synergy is no more active on the login screen (it was working great with Snow Leopard)
Issue #2: When the screen is asleep, synergy events do not wake it up (keyboard, mouse movement or click). You need to click a mouse or press a key on a keyboard directly connected to Lion to wake it up.
Issue #3: When the session has been locked, it is not possible to use synergy to enter the password. UPDATE: just redid a test and I cannot reproduce Issue #3 anymore...
PS: would have loved to open bugs in the tracker, but new users are not allowed to...
Server Ubuntu 11.10 - synergys 1.3.6, Client Max OSX Lion 10.7.2 - synergyc 1.3.6
Working (sort of)......
My arrangement is somewhat unusual:
Macbook Pro (Client) -> Monitor <- Ubuntu (Server) + keyboard/mouse
So I have 2 video inputs to the monitor, my Ubuntu machine connects via VGA, and my Macbook connects via DVI - there is a source selection button on the monitor, which allows me to switch between machines. I run Synergys on the Linux machine, with the client on the Mac. I did an upgrade install of Lion and all was working well i.e. on the Linux box when I moved out on the left with the mouse it appeared on the right of the same monitor (once I'd switched source to the Mac!), I could then continue moving left until the mouse would appear on the Macbook Pro's screen to the left.
Lion upgrade was a mess, so did a clean install - and now when I move left from Linux, I have to move my mouse a "long way" before it appears on the right side of my monitor, and the mouse stops at the left edge i.e. I can never reach the Macbook Pro's screen.
My guess is that the Mac is not correctly reporting the dimensions/location of the displays (built-in screen and external monitor), or it is but it automatically assumes that the external display is to the right of the monitor?
So in short, I think you should downgrade to 1.3.x, and things might work for you.
answered 07 Nov '11, 08:50