Imported issue:
Steps to reproduce:
Expected: As when both my setup had both client and server running 10.8.x, the screensaver engages on both computers
Actual: The screensaver only engages on the server.
Versions and operating systems:
Server: 1.4.12 / Mac OS X 10.8.4
Client: 1.4.12 / Mac OS X 10.9 Mavericks developer previews
This seems to still be broken in the current beta build. 1.4.14
I can confirm this behavior. Screensaver sync worked on 10.8, doesn't on 10.9.
I'm seeing this as well. Both client and server on 1.4.12, so it doesn't appear to be a recent regression.
This appears to still be broken as of version 1.4.17.
Still broken in 1.5.0 (tested with Mac OS 10.9.3 and 10.9.4 beta 13E9).
Works when server is 10.8 and client is 10.9, but once I upgraded the server to 10.9 it stopped working.
Scratch that, reverse it... Upgrading the CLIENT to 10.9 is what causes the issue, sorry.
Confirming this is still an issue with OSX 10.9.4 & Fedora 20. Both are running Synergy 1.5.0, the OSX system is the server, screensaver works fine there. The Fedora system will not turn off its display, it sits at the screensaver forever. I've disabled "Synchronize screen savers" on the Synergy server as mentioned in a couple of other threads. Turning this option on/off has no effect.
I was using Synergy v1.5.1-r2398-MacOSX109-x86_64 on Yosemite, along with Synergy v1.5.1-r2398-Linux-x86_64 on RHEL 6.4. Hot corner on my Macbook was working, e.g. when I moved mouse to that corner, my macbook screen lock+screen saver come on.
I just upgraded to beta synergy-1.6.1-master-afa24f4-MacOSX1010-x86_64 and matching version for Linux. Hot corner is now broken. Moving the mouse to corner no longer put my macbook into screen saver mode.
OS: OSX 10.10 and Linux RHEL 6.4_x86_64
Version 1.7.6 was just released, and yet this is still broken even after all this time (when I put the server into screensaver mode, the client does not go into screensaver mode).
Server: Ubuntu Linux 14.04.4 LTS
Client: Mac OS X 10.11.3 El Capitan
Here is my server config:
section: screens
linux:
mac:
super = ctrl
ctrl = super
end
section: links
linux:
right = mac
mac:
left = linux
end
section: options
screenSaverSync = true
end
Still broken for me too.
WFM now. Synergy release 1.8.3-stable on RHEL6.6 and OSX 10.11.6
Same issue here with 1.8.8-stable-25a8cb2 using OSX as the server and Windows 10 as the client.
not working with osx + win 1.9.0-rc3, as well. Is there confirmation that this is working for paid versions?
Still not working
Server: MacOS Sierra Version 10.12.6
Client: MacOS High Sierra Version 10.13.4
Synergy: 1.8.8-stable-c30301e
Happy to buy paid version if it works
Sigh
@nbolton why is this closed when paying users still have this issue? It's only "stale" because we're waiting to hear back from your team...
I agree that bugs should not be closed just because they are old. If the bug has not been resolved, it hurts no one to keep it open, but closing it when the bug is still valid is doing EVERYONE a disservice. If your bug list is too long, and github's triaging isn't working for you, I recommend using a different problem tracker. Needing a place to put "old bugs" that are cluttering your devel process implies that github's issue system is not sufficient for your needs.
They closed 672 issues 5 hours ago WTF?
Yep. They just unilaterally closed all stale bugs without fixing a single one.
This issue was not meant to be marked stale. Please let me know if you see any others that are obviously not stale (or are still an issue).
This still does not work. I'm shocked as I just paid for the software, hoping that the commercial version would work better.
Requesting an update on this issue please.
It is quite simple to subscribe to screensaver events on OSX, and also to control them so I'm wondering if this is just a lack of development resources, or there are roadblocks to fixing this? 馃
Most helpful comment
I agree that bugs should not be closed just because they are old. If the bug has not been resolved, it hurts no one to keep it open, but closing it when the bug is still valid is doing EVERYONE a disservice. If your bug list is too long, and github's triaging isn't working for you, I recommend using a different problem tracker. Needing a place to put "old bugs" that are cluttering your devel process implies that github's issue system is not sufficient for your needs.