| Summary: | Update synergy in Mageia 8 for compatibility with Mageia 9. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dave Hodgins <davidwhodgins> |
| Component: | RPM Packages | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, herman.viaene |
| Version: | 8 | Keywords: | feedback |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | synergy | CVE: | |
| Status comment: | |||
| Attachments: | Synergy conf file on system where mouse/keyboard is connected | ||
|
Description
Dave Hodgins
2023-05-30 19:08:07 CEST
Assigning to QA, Packages in 8/Core/Updates_testing: ====================== synergy-gui-1.14.5.14-1.mga8 synergy-1.14.5.14-1.mga8 From SRPMS: synergy-1.14.5.14-1.mga8.src.rpm Assignee:
geiger.david68210 =>
qa-bugs Looks like it should have a README.urpmi file added. On the install running synergys, where the mouse/keyboard are physically connected the option screenSaverSync must be removed or commented out, if present in the synergy.conf file which may be $HOME/.synergy.conf or /etc/synergy.conf Otherwise it fails to start the server. Found using debug ... $ synergys -n desktop --debug DEBUG which returns ... [2023-05-30T17:47:34] ERROR: cannot read configuration "/etc/synergy.conf": read error: line 47: unknown argument "screenSaverSync" @Dave I've used synergy a long time ago, and remember to have been fiddling around with the conf settings. Found now https://help.ubuntu.com/community/SynergyHowto which has a sample of the conf file. I'll try to get the current version working and then do the update on the server side. CC:
(none) =>
herman.viaene Got the current version working with this laptop as server and desktop PC as client. Some remarks: this installation had no synergy.conf file, neither system wide in/etc nor in the home. Edited one in ~/.synergy.conf for the server, copying the sample from above mentioned site. Note that I had to use FQDN's. As I have firewall running, I had to open port 24800, then I could travel the mouse pointer from one screen to another. Updated the server with the new version (this one carries an /etc/synergy.conf file, fine. Then run the updated server vs the current client and all works OK. Note: although the site does not mention this, you get nowhere trying to use the synergy-gui since that one refuses to start without a licence key. Leaving to Dave to check and give the OK. Feedback: see Comment 2 CC:
(none) =>
fri Created attachment 13863 [details]
Synergy conf file on system where mouse/keyboard is connected
It's working for me once the screenSaverSync option is removed. As the conf
file can be in /home, it can't be handled by the package, so should be
documented in a README.urpmi
Attaching my working conf file which is started by ...
$ cat .config/autostart-scripts/synergy
#!/bin/bash
killall -9 synergys 2>/dev/null
synergys -n desktop --debug FATAL
On my rpi4b, synergyc is started by
$ cat .config/autostart-scripts/synergy
#!/bin/bash
killall -9 synergyc 2>/dev/null
synergyc --name rp4 --restart --debug FATAL 192.168.10.2
Once the README.urpmi is added, this is ready to validate.
The synergy-gui rpm should probably be removed as it is nagware. The synergy rpm package itself is open source and does work. Mageia8 is EOL! So closing as OLD! Resolution:
(none) =>
OLD |