Could not connect to display, Status 127 - Fedora
Dewm-Bot opened this issue · 2 comments
When trying to run waynergy, no matter what commands I use I get the final error "Could not connect to display"
Server: Windows 11, running Barrier latest (also tried with InputLeap and Synergy)
Client: Fedora Kinoite (40.20240704)
wl-clipboard is not installed
waynergy -n -c 192.168.10.150 --loglevel 5 -b kde
0.000000325: [DEBUG] Section log not found in INI
0.000020487: [INFO] Log initialized at level 5
0.000028455: [INFO] waynergy version 0.0.17
0.000051585: [DEBUG] Property syn_raw_key_codes not found in INI
0.000066856: [DEBUG] requiring wait() on SIGCHLD
0.000517727: [WARN] Child died: PID 45085, Status 127
0.000550960: [DEBUG] not requiring wait() on SIGCHLD
0.000562432: [INFO] Clipboard sync disabled by command line
0.000577493: [DEBUG] Section wayland not found in INI
0.000628705: [ERROR] Could not connect to display
I have tried running it directly, running it with sudo, different launch commands including -E, the error is the exact same no matter what commands are used (other than the warning about wl-clipboard if not using -n).
master now logs the error code for a wl_display_connect() failure, so building and running that will give a better idea. Usually there's something else printed, but perhaps Fedora are building libwayland weirdly.
Thank you so much! I can confirm that the latest master provides FAR more info into what's actually going on. Unfortunately I don't have logs anymore, but what I did do was reinstalled python-uinput (unsure if this was of any use) and performed chmod on /dev/uinput.
I was certain I have done this previously, but maybe I missed that? Though the extended debug information provided me with a clear indicator that uinput simply wasn't working correctly. I now run the command without the -b kde switch as it provides me with an error "input backend kde not supported" Without the switch it now works correctly!
Thank you so much! And I sincerely apologize for the user-error here.