Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Synergy 1.11 working on Big Sur?


Recommended Posts

John Kenneth Fisher

I realize OS X Big Sur is a beta with all that means, and that if Synergy does not work that is not Symless' problem. I also realize that just saying it works on the current Big Sur beta does not mean it will work on the NEXT Big Sur beta, or that there aren't issues yet to be found on Big Sur.

 

That said - I only have two programs that will overly inconvenience me if I cannot run them on Big Sur beta, and Synergy is one of them. Has anyone tried to use it and have any anecdotal feedback? Thanks!

Link to post
Share on other sites
  • 1 month later...
  • 1 month later...
On 8/13/2020 at 8:12 AM, Daniel Alarcon said:

@John Kenneth Fisher We haven't officially tested on Big Sur yet, however, I've received reports of Synergy working without any problem in it by users

If I am experiencing a bug (Server is a Mac on Big Sur, Client is Windows. If I copy something on Windows and go to paste it in Big Sur, it appears to paste Japanese Kanji) where can I report it to help fix the issue in a future release?

Link to post
Share on other sites
  • 1 month later...
barronlroth
On 9/17/2020 at 12:17 PM, The1Jon said:

If I am experiencing a bug (Server is a Mac on Big Sur, Client is Windows. If I copy something on Windows and go to paste it in Big Sur, it appears to paste Japanese Kanji) where can I report it to help fix the issue in a future release?

Same issue here. I'll also report it.

 

On 9/24/2020 at 9:39 AM, Daniel Alarcon said:

 

Link to post
Share on other sites

Daniel - Any idea when you will do testing?  I'm not moving to Big Sur until I have more than anecdotal evidence that Synergy will work.  I'm still running 1.10.3-stable, and rely on it every day! Can certainly  update to newer Synergy if required.  

Thanks!

Link to post
Share on other sites

I can't get keyboard to work with apple m1 with Big Sur as server.

Mouse works fine on Windows and OS X Clients, but keyboard doesn't.

tested with 1.12. stable

Link to post
Share on other sites

I'm having a similar problem where often the keyboard does not work on the client machine.  Running two machines with Big Sur.  When I turn the screen saver on, which also puts up the password prompt, they keyboard starts working again.

Link to post
Share on other sites

I have an apple wireless keyboard:
https://www.apple.com/shop/product/MQ052B/A/magic-keyboard-with-numeric-keypad-british-english-silver

Have not tried with a different one.  I have hot corners setup so I just move my mouse to the corner whenever it happens.  It's usually when I walk away and come back, often the server has went to sleep but the client has not, then I wake up server, it doesn't work, then I go to the hot corner to put on the screen saver, and it works again. 

 

Link to post
Share on other sites

Hi, I'm running Synergy Basic with the following version and build and wanted to report the following issue.

image.png.38c3d9666dcf70477758e0029344aec0.png

  • Server: M1 Mac mini | Big Sur 11.0.1
  • Client: HP Elitebook | Windows 10 Enterprise Version 1809
  • Problem: Synergy on the server machine crashes and shuts down randomly throughout the day
  • MacOS Console Crash Report: 
    Process:               synergy [1840]
    Path:                  /Applications/Synergy.app/Contents/MacOS/synergy
    Identifier:            synergy
    Version:               1.12.2 (1.12.2)
    Code Type:             X86-64 (Translated)
    Parent Process:        ??? [1]
    Responsible:           synergy [1840]
    User ID:               501
    
    Date/Time:             2020-11-30 21:09:18.990 -0800
    OS Version:            macOS 11.0.1 (20B29)
    Report Version:        12
    Anonymous UUID:        75D5EA06-BBA2-8562-8F8A-15400505CA89
    
    
    Time Awake Since Boot: 43000 seconds
    
    System Integrity Protection: enabled
    
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000028
    Exception Note:        EXC_CORPSE_NOTIFY
    
    Termination Signal:    Segmentation fault: 11
    Termination Reason:    Namespace SIGNAL, Code 0xb
    Terminating Process:   exc handler [1840]

     

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...