-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not found in Arch gnome Wayland. #175
Comments
Unit razer_test.service could not be found. |
Did you select razer_test as backend in the RazerGenie setting (button on the bottom left of the UI)? You want to have "OpenRazer" selected there. |
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. |
I have put the error messages that it shows in the console, first with openrazer selected, a few messages above, and the previous message with the razer_test console message. |
Keep the setting on "OpenRazer" and then go to https://github.com/openrazer/openrazer/wiki/Troubleshooting |
Not found in Arch gnome Wayland.
Unit razer_test.service could not be found.
My device is in the supported list. Deathadder v2 X hyperspeed.
I have followed all the steps and done all the checks following the instructions at [(https://github.saobby.my.eu.org.translate.goog/openrazer/openrazer/wiki/Troubleshooting?_x_tr_sl=auto&_x_tr_tl=es-ES&_x_tr_hl=es)]
Everything is fine as far as openrazer daemon is concerned, it runs perfectly, and apparently everything is fine as far as openrazer-daemon.service
I have tried so many things that surely many of the answers I am going to receive have already been tried and discarded, but I am willing to try again everything that is told to me in this thread until I find the solution, although I am afraid that it will have to be to a bug in razergenie.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Translation loaded: false libopenrazer: There was an error checking if the daemon is enabled. Unit state is: not-found . Error message:
systemctl --user status openrazer-daemon.service
`● openrazer-daemon.service - Daemon to manage razer devices in userspace
Loaded: loaded (/usr/lib/systemd/user/openrazer-daemon.service; enabled; preset: enabled)
Active: active (running) since Sun 2024-11-10 04:00:01 CET; 38min ago
Invocation: 877e0333c6d24f1d8f5586a683313d28
Docs: man:openrazer-daemon(8)
Main PID: 1371 (openrazer-daemo)
Tasks: 4 (limit: 37300)
Memory: 23.5M (peak: 25.4M)
CPU: 93ms
CGroup: /user.slice/user-1002.slice/user@1002.service/app.slice/openrazer-daemon.service
└─1371 openrazer-daemon
nov 10 04:00:01 davidarch systemd[1361]: Starting Daemon to manage razer devices in userspace...
nov 10 04:00:01 davidarch openrazer-daemon[1371]: Starting daemon.
nov 10 04:00:01 davidarch systemd[1361]: Started Daemon to manage razer devices in userspace.
nov 10 04:00:01 davidarch openrazer-daemon[1371]: 2024-11-10 04:00:01 | razer | INFO | Initialising Daemon (v3.9.0). Pid: 1371
nov 10 04:00:01 davidarch openrazer-daemon[1371]: 2024-11-10 04:00:01 | razer.screensaver | INFO | Initialising DBus Screensaver Monitor
nov 10 04:00:01 davidarch openrazer-daemon[1371]: 2024-11-10 04:00:01 | razer | INFO | Serving DBus`
The text was updated successfully, but these errors were encountered: