-
Notifications
You must be signed in to change notification settings - Fork 65
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
Linux: Insufficient permissions, please make sure the device file is read- and writable #560
Comments
|
FWIW, you don't even need to logout and back in - if you unplug & replug the keyboard, that should be enough for udev to notice, and set up permissions appropriately. |
I have the script in there, can see it is working (symlink |
Are you using Gnome or KDE, or anything else that plays well with systemd? The udev script relies on systemd knowing who is logged in, and that needs a bit of support from the login manager / DE. |
I use KDE Neon on Ubuntu 20 LTS, which ships the latest KDE Plasma :) |
@xerus2000 Can you tell me what Ideally, it should be something like this:
If it doesn't list a seat, then the udev rules as they are now will not be enough, and we'll have to figure out something else. |
I had this issue with my new keyboardio Atreus and fixed it by adding the rules suggested above (on Ubuntu 20.04). I also have an older Atreus keyboard and I'd love to run it through Chrysalis as well, so that I can share layouts between them. But I get the insufficient permissions error when selecting the original Atreus. Is there a different rule I need to set for the original Atreus? |
Hi, I just received my Atreus today and had the same problem and here is an easier alternate solution! I jumped onto discord and someone suggested I needed to add permissions for my user to the So just run in the Terminal:
And then log out and back in. Then re-open Chrysalis. Voila. I'm on Ubuntu 18.04 by the way. |
|
cool, sudo adduser $USER dialout didn’t wok for me after logout/login (but I was told that reboot wasn’t needed). |
The The master branch now has a better explanation too, and a "Fix it" button (which installs the udev rules, reloads it, triggers an udev rescan for the device, and then checks if it is accessible after). |
I think that the new changes on master adequately fix the issue for the vast majority of cases, so I'm going to close this one. Do feel free to reopen (or open a new issue) if Chrysalis master does not address the issue on some distro or another. |
Btw, seats output: ❯ loginctl list-seats --no-pager
SEAT
seat0
1 seats listed. |
The udev rules are in place and working, but Chrysalis only worked with the above dialout tweak... |
Describe the bug
Launch Chrysalis (Appimage 0.7.9+259), Error message pops up.
Did also happen after I set myself in the dialout group, logout/login
To Reproduce
see above
Expected behavior
No Error message
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Solution found with help on discord (algernon) :
Download this file: https://raw.githubusercontent.com/keyboardio/Kaleidoscope/master/etc/60-kaleidoscope.rules, place it in /etc/udev/rules.d/ (using the same name, 60-kaleidoscope.rules), then sudo udevadm control -R, and then if you logout and back in, it should hopefully work.
what that file does, is tell udev & systemd to give ownership to the atreus (& model01) device files to the user logged in on the main "seat" (which in practice translates to whoever is logged in on the desktop)
might even work if you just unplug & replug the keyboard, as udev should re-detect it then, so you can save a logout & login
The text was updated successfully, but these errors were encountered: