Since ChromeOS has switched over to using Wayland as their primary display environment and Synergy is primarily an Xorg/X11 client, the current way that I've worked around the issue (similar to what is mentioned in the Chrome documentation above ) is to run an alternate X server in full screen but one of the side effects of the way I had it working was that the cursor wasn't actually visible and the ChromeOS cursor didn't update to follow the location of the cursor from Synergy, luckily my window manager had focus follows mouse enabled so I was able to track the cursor a little bit by watching which window activated, and since I have a primarily keyboard centric workflow it didn't really impact my ability to be productive. I was able to get Synergy "sort of" working on ChromeOS, but there are some fairly significant caveats such as an invisible cursor and only being able to interact with apps that live within the Linux apps and in particular that are launched under the say X DISPLAY as Synergy. Synergyc: /build/buildd/synergy-1.3.8/src/lib/platform/CXWindowsScreen.cpp:112: CXWindowsScreen::CXWindowsScreen(const char*, bool, bool, int): Assertion `s_screen = _null' failed.įYI i have successfully configured synergy with Ubuntu on my chromebook but i'm interested of controlling Chrome OS only !
build/buildd/synergy-1.3.8/src/cmd/synergyc/synergyc.cpp,246 build/buildd/synergy-1.3.8/src/cmd/synergyc/synergyc.cpp,346 T17:41:17 WARNING: cannot open secondary screen: unable to open screen build/buildd/synergy-1.3.8/src/lib/platform/CXWindowsScreen.cpp,901 build/buildd/synergy-1.3.8/src/cmd/synergyc/synergyc.cpp,765 Here is what is logged when I run synergyc -f 192.168.1.21
I tried very hard to make this happen via my Acer C720P and my macbook pro !įrom the steps described by Aaron, i've done all the commands but when i launch synergyc to my serveur, nothing happen.
0 kommentar(er)
