aFatBird

RC1 does not start on Fedora 26

4 posts in this topic

The Synergy2 service does not start on Fedora 26. When I try it from the command line it outputs

QIODevice::write (QFile, ""): device not open

. Synergy2 does not create a log before failing.

systemctl status synergy

shows:

synergy.service - Synergy Service
   Loaded: loaded (/usr/lib/systemd/system/synergy.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/synergy.service.d
           └─override.conf
   Active: failed (Result: exit-code) since Sat 2017-11-04 03:13:31 CDT; 9min ago
  Process: 3512 ExecStart=/usr/bin/env HOME=/home/username /usr/bin/synergyd (code=exited, status=127)
 Main PID: 3512 (code=exited, status=127)

Nov 04 03:13:31 skua systemd[1]: synergy.service: Failed with result 'exit-code'.
Nov 04 03:13:31 skua systemd[1]: synergy.service: Service has no hold-off time, scheduling restart.
Nov 04 03:13:31 skua systemd[1]: Stopped Synergy Service.
Nov 04 03:13:31 skua systemd[1]: synergy.service: Start request repeated too quickly.
Nov 04 03:13:31 skua systemd[1]: Failed to start Synergy Service.
Nov 04 03:13:31 skua systemd[1]: synergy.service: Unit entered failed state.
Nov 04 03:13:31 skua systemd[1]: synergy.service: Failed with result 'exit-code'.

The troubleshooting steps for beta4 do not resolve this issue.

 

RC1 starts and connects on windows 10 though.

Share this post


Link to post
Share on other sites
1 hour ago, aFatBird said:

synergyd

What the heck? That should say synergy-service. Could you email [email protected]?

Share this post


Link to post
Share on other sites

I sent an email to the support address with a copy of my post. Maybe the service name refactor worked on the .deb but missed the .rpm build. Thanks for the reply.

Share this post


Link to post
Share on other sites
5 hours ago, aFatBird said:

I sent an email to the support address with a copy of my post. Maybe the service name refactor worked on the .deb but missed the .rpm build. Thanks for the reply.

try restarting your computer,(or systemctl daemon-reload)

and if that doesnt work removing and then installing it again.

the service is from the old beta 4 and shouldn't work.

Edited by jaap aarts
removed m
  • Like 1

Share this post


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