Access to USB device denied
I have a ColorHug ALS ambient light sensor that I use together with the DDC/CI interface of my display to automatically set the brightness of my displays just like every smartphone does. It is connected via USB:
$ lsusb
Bus 001 Device 028: ID 273f:1007 Hughski Limited
…
This has been working fine until a few weeks ago, some Fedora upgrade likely has changed something. I have a file /lib/udev/rules.d/99-i2c-permissions.rules
which contains this:
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
Also my user account is in the i2c
group. Also all these devices should be readable for my user:
$ ls /dev/i2c-* -l
crw-rw----. 1 root i2c 89, 0 26. Dez 10:41 /dev/i2c-0
crw-rw----. 1 root i2c 89, 1 26. Dez 10:41 /dev/i2c-1
crw-rw----. 1 root i2c 89, 2 26. Dez 10:41 /dev/i2c-2
crw-rw----. 1 root i2c 89, 3 26. Dez 10:41 /dev/i2c-3
crw-rw----. 1 root i2c 89, 4 26. Dez 10:41 /dev/i2c-4
crw-rw----. 1 root i2c 89, 5 26. Dez 10:41 /dev/i2c-5
crw-rw----. 1 root i2c 89, 6 26. Dez 10:41 /dev/i2c-6
crw-rw----. 1 root i2c 89, 7 26. Dez 10:41 /dev/i2c-7
crw-rw----. 1 root i2c 89, 8 26. Dez 10:41 /dev/i2c-8
crw-rw----. 1 root i2c 89, 9 26. Dez 10:41 /dev/i2c-9
But now I get the following when trying to get a reading from the device:
$ colorhug-cmd take-reading-raw
No connection to device: USB error on device 273f:1007 : Access denied (insufficient permissions) [-3]
Calling this as root
still works, so it is just a permission problem.
Why does the permission not get passed to my normal user account and how can I restore that?
permissions usb
add a comment |
I have a ColorHug ALS ambient light sensor that I use together with the DDC/CI interface of my display to automatically set the brightness of my displays just like every smartphone does. It is connected via USB:
$ lsusb
Bus 001 Device 028: ID 273f:1007 Hughski Limited
…
This has been working fine until a few weeks ago, some Fedora upgrade likely has changed something. I have a file /lib/udev/rules.d/99-i2c-permissions.rules
which contains this:
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
Also my user account is in the i2c
group. Also all these devices should be readable for my user:
$ ls /dev/i2c-* -l
crw-rw----. 1 root i2c 89, 0 26. Dez 10:41 /dev/i2c-0
crw-rw----. 1 root i2c 89, 1 26. Dez 10:41 /dev/i2c-1
crw-rw----. 1 root i2c 89, 2 26. Dez 10:41 /dev/i2c-2
crw-rw----. 1 root i2c 89, 3 26. Dez 10:41 /dev/i2c-3
crw-rw----. 1 root i2c 89, 4 26. Dez 10:41 /dev/i2c-4
crw-rw----. 1 root i2c 89, 5 26. Dez 10:41 /dev/i2c-5
crw-rw----. 1 root i2c 89, 6 26. Dez 10:41 /dev/i2c-6
crw-rw----. 1 root i2c 89, 7 26. Dez 10:41 /dev/i2c-7
crw-rw----. 1 root i2c 89, 8 26. Dez 10:41 /dev/i2c-8
crw-rw----. 1 root i2c 89, 9 26. Dez 10:41 /dev/i2c-9
But now I get the following when trying to get a reading from the device:
$ colorhug-cmd take-reading-raw
No connection to device: USB error on device 273f:1007 : Access denied (insufficient permissions) [-3]
Calling this as root
still works, so it is just a permission problem.
Why does the permission not get passed to my normal user account and how can I restore that?
permissions usb
add a comment |
I have a ColorHug ALS ambient light sensor that I use together with the DDC/CI interface of my display to automatically set the brightness of my displays just like every smartphone does. It is connected via USB:
$ lsusb
Bus 001 Device 028: ID 273f:1007 Hughski Limited
…
This has been working fine until a few weeks ago, some Fedora upgrade likely has changed something. I have a file /lib/udev/rules.d/99-i2c-permissions.rules
which contains this:
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
Also my user account is in the i2c
group. Also all these devices should be readable for my user:
$ ls /dev/i2c-* -l
crw-rw----. 1 root i2c 89, 0 26. Dez 10:41 /dev/i2c-0
crw-rw----. 1 root i2c 89, 1 26. Dez 10:41 /dev/i2c-1
crw-rw----. 1 root i2c 89, 2 26. Dez 10:41 /dev/i2c-2
crw-rw----. 1 root i2c 89, 3 26. Dez 10:41 /dev/i2c-3
crw-rw----. 1 root i2c 89, 4 26. Dez 10:41 /dev/i2c-4
crw-rw----. 1 root i2c 89, 5 26. Dez 10:41 /dev/i2c-5
crw-rw----. 1 root i2c 89, 6 26. Dez 10:41 /dev/i2c-6
crw-rw----. 1 root i2c 89, 7 26. Dez 10:41 /dev/i2c-7
crw-rw----. 1 root i2c 89, 8 26. Dez 10:41 /dev/i2c-8
crw-rw----. 1 root i2c 89, 9 26. Dez 10:41 /dev/i2c-9
But now I get the following when trying to get a reading from the device:
$ colorhug-cmd take-reading-raw
No connection to device: USB error on device 273f:1007 : Access denied (insufficient permissions) [-3]
Calling this as root
still works, so it is just a permission problem.
Why does the permission not get passed to my normal user account and how can I restore that?
permissions usb
I have a ColorHug ALS ambient light sensor that I use together with the DDC/CI interface of my display to automatically set the brightness of my displays just like every smartphone does. It is connected via USB:
$ lsusb
Bus 001 Device 028: ID 273f:1007 Hughski Limited
…
This has been working fine until a few weeks ago, some Fedora upgrade likely has changed something. I have a file /lib/udev/rules.d/99-i2c-permissions.rules
which contains this:
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
Also my user account is in the i2c
group. Also all these devices should be readable for my user:
$ ls /dev/i2c-* -l
crw-rw----. 1 root i2c 89, 0 26. Dez 10:41 /dev/i2c-0
crw-rw----. 1 root i2c 89, 1 26. Dez 10:41 /dev/i2c-1
crw-rw----. 1 root i2c 89, 2 26. Dez 10:41 /dev/i2c-2
crw-rw----. 1 root i2c 89, 3 26. Dez 10:41 /dev/i2c-3
crw-rw----. 1 root i2c 89, 4 26. Dez 10:41 /dev/i2c-4
crw-rw----. 1 root i2c 89, 5 26. Dez 10:41 /dev/i2c-5
crw-rw----. 1 root i2c 89, 6 26. Dez 10:41 /dev/i2c-6
crw-rw----. 1 root i2c 89, 7 26. Dez 10:41 /dev/i2c-7
crw-rw----. 1 root i2c 89, 8 26. Dez 10:41 /dev/i2c-8
crw-rw----. 1 root i2c 89, 9 26. Dez 10:41 /dev/i2c-9
But now I get the following when trying to get a reading from the device:
$ colorhug-cmd take-reading-raw
No connection to device: USB error on device 273f:1007 : Access denied (insufficient permissions) [-3]
Calling this as root
still works, so it is just a permission problem.
Why does the permission not get passed to my normal user account and how can I restore that?
permissions usb
permissions usb
asked 19 mins ago
Martin Ueding
1,28811127
1,28811127
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491446%2faccess-to-usb-device-denied%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491446%2faccess-to-usb-device-denied%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown