Package Details: openrazer-daemon 3.5.0-1

Git Clone URL: (read-only, click to copy)
Package Base: openrazer
Description: Userspace daemon that abstracts access to the kernel driver. Provides a DBus service for applications to use.
Upstream URL:
Licenses: GPL2
Submitter: z3ntu
Maintainer: z3ntu
Last Packager: z3ntu
Votes: 65
Popularity: 1.92
First Submitted: 2017-11-10 09:12 (UTC)
Last Updated: 2022-11-20 14:07 (UTC)

Pinned Comments

z3ntu commented on 2019-05-16 14:12 (UTC) (edited on 2022-04-09 14:39 (UTC) by z3ntu)

Please remember, that this package uses DKMS for building the kernel module and as such requires the kernel headers for your kernel installed. See also

Another manual step that needs to be taken is adding your user to the plugdev group, e.g. using the command sudo gpasswd -a $USER plugdev.

You can find a few tips for troubleshooting an install at

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

vmsh0 commented on 2022-11-20 16:37 (UTC) (edited on 2022-11-20 16:37 (UTC) by vmsh0)

To me this boils down to: 1) Either assume /usr/bin/python3 is the one and only python you like, and just explicitly use that. You have a transitive dependency on the python, so you know what's there, that's fine 2) Or print a warning/ask for a variable (that is not PATH :) to be set when python3 is not /usr/bin/python3, to communicate your concern to the user and ask for their confirmation.

This middle ground of both assuming something which is definitely there is good, but refusing to use it, is unconvincing to me. Having said this, at the end of the day it's pretty easy to work around this, so if that's the way you thing it shall be done, then it's all good. Just my two cents. Thanks for the package!

gilbs commented on 2022-09-03 14:00 (UTC)

Do you think it would be possible to provide a way to bypass the python path check that doesn't involve manual operations (like editing the PKGBUILD or changing the PATH)? One idea could be to check against some environment variable (e.g. ["${AUR_OPENRAZER_SKIP_PYTHON_PATH_CHECK}" = "true"]?).

I use asdf-vm which shims system python by default, so it should play nicely with this install script.

Thanks for maintaining this package.

therxyy commented on 2022-02-07 17:04 (UTC) (edited on 2022-02-07 17:14 (UTC) by therxyy)

the package wont install, no matter what i try. numpy dependency seems broken or outdated

EDIT: my mistake, i didnt do pacman -Syu X)

z3ntu commented on 2021-11-24 20:45 (UTC)

@jahway603 I've only added the sanity check to the PKGBUILD so people stop building this package with a "broken" Python setup. The message already mentions "[..] or point your PATH variable to prefer /usr/bin/ temporarily." Would you be happy with explicitly adding the command "export PATH=/usr/bin:$PATH" to the message? And no I won't add workarounds to fix broken build environments.

jahway603 commented on 2021-11-22 02:56 (UTC)

Currently on 3.0.1-1 and unable to upgrade to the updated 3.1.0-1 version with the same "python path error". It was successful when I tried what @testbird71 suggested. @z3ntu, can you please add the fix into the PKGBUILD so that it will work for everyone? Thanks.

testbird71 commented on 2021-08-17 14:26 (UTC)

type in your terminal 1. export PATH=/usr/bin:$PATH 2. yay -Syu

testbird71 commented on 2021-08-16 13:37 (UTC)

ERROR: Your 'python3' does not point to /usr/bin/python3 but to /bin/python3, likely a custom environment like anaconda. Please build this package in a clean chroot (e.g. with or point your PATH variable to prefer /usr/bin/ temporarily. ==> FEHLER: Ein Fehler geschah in prepare().

How can i build it temporarily? I will not chroot

YoFreakinLo commented on 2021-08-06 09:49 (UTC)

@whynothugo thank you :)

whynothugo commented on 2021-08-06 09:48 (UTC)

@YoFreakinLo Yes, that's completely unrelated here. This is discussion for the openrazer package.

You're getting error download other packages from the Manjaro repositories. Apparently either mirrors or your local package db is out of date. Best to ask on Manjaro's forums or IRC.