Open igorsantos07 opened 4 months ago
You don't need to, and should never run a browser as root. All you need is a udev config, for the example pid/vid in the issue:
/etc/udev/rules.d/90-qmk.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="3434", ATTR{idProduct}=="02A0", GROUP="plugdev", TAG+="uaccess"
unplug the keyboard, plug back in and it should work
This is a split of one of the many issues reported at #91 (and possibly other issues around the board, such as https://github.com/the-via/releases/issues/257): on Linux, it's usually necessary to run the browser with root privileges, or otherwise give the current user permissions over
/dev/hidraw*
(or similar files), as pointed bywlarch
.Given the amount of people reacting to the linked solutions, it seems to affect many Linux users (if not all of them).
The only thing that the VIA app can say are two errors (one quite misleading), since it can see the keyboard, but can't really talk to it:
The first one seems to be replaceable by the following in some other distros (or other keyboards):
That said, it's possible to pinpoint the issue if you visit
chrome://device-log
(found byhofheinz
and confirmed by others) - there, it complains about missing permission on the specific file.Is there any chance the VIA app could drink from that log and tell specifically about the lack of permissions? If not, maybe could the "failed to open device" hint about a possible lack of root permissions, if the OS is Linux?