FS#55678 - [synergy] Synergys fails if enabled as a socket

Attached to Project: Community Packages
Opened by Victor Bessonov (Unb0rn) - Tuesday, 19 September 2017, 06:54 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Synergys is not working if the service enabled via socket systemctl --user enable synergys.socket
In logs I get something like:
WARNING: cannot listen for clients: cannot bind address: Address already in use

If I enable service instead of socket, everything works fine.

Additional info:
* package version(s) : 1.8.8-3


Steps to reproduce:
-Install Synergy
-Enable synergys.socket for user.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:00 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/synergy/issues/1
Comment by Vanush "Misha" Paturyan (ektich) - Wednesday, 30 May 2018, 15:19 GMT
as reported here [1], changing "Conflicts=synergys@.service" to "Conflicts=synergys.service" in the "[Unit]" section of the /usr/lib/systemd/user/synergys.socket file solves this issue.


[1] https://bbs.archlinux.org/viewtopic.php?id=225156
[2] https://www.freedesktop.org/software/systemd/man/systemd.socket.html
Comment by Vanush "Misha" Paturyan (ektich) - Friday, 22 November 2019, 09:45 GMT
Another option that should be added to the /usr/lib/systemd/user/synergys.socket file is "ReusePort=true". should be added to the "[Socket]" part of it.
Comment by Vanush "Misha" Paturyan (ektich) - Friday, 22 November 2019, 10:14 GMT
Something similar to the attached patch
   fs-55678.patch (0.3 KiB)
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...