You are not logged in.

#1 2022-02-23 14:16:14

W54J04S07T
Member
Registered: 2016-06-27
Posts: 101

uaccess group

Creating group "uaccess" defaults to a group number 1000 here.

What I have not been able to find anywhere is what the
standard group id number for the "uaccess" group is
supposed to be.

Is there a preferred/standard number ( and what is it )...
or will any number do?

Offline

#2 2022-02-23 14:32:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,738

Re: uaccess group

Why and as to what point do you think you need that group? It's not supposed to be a group, see the first paragraph in: https://wiki.archlinux.org/title/Users_ … emd_groups

the point of the "uaccess" udev rule tag is that logind will dynamically grant access to devices  to the currently active user explicitly outside of the traditional group logic. It's not a group, but a piece of information that allows logind to dynamically grant access to devices to properly logged in/authenticated users.

Last edited by V1del (2022-02-23 14:37:01)

Offline

#3 2022-02-23 17:09:45

W54J04S07T
Member
Registered: 2016-06-27
Posts: 101

Re: uaccess group

That group seems to be required by some udev rules, or it triggers an error in the logs.
I inserted said group with Gid 1000 and the error went away.  As to whether that
Gid is the right number, is what I'm wondering about.

Given that most users are typically in Gid 1000 around here, it probably is fine
based on your comments... but I don't know that.  Hence the question.

Offline

#4 2022-02-23 17:38:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,738

Re: uaccess group

These udev rules should not use this as a group but as a TAGS+= rule as mentioned in the linked section. Which rules are those? The point if this is that you do not need this group, it isn't a group but should be used as an identifier so that the group can be dynamically assigned (that group being something from your user e.g. the group users or so).

If you have rules from packages that actively expect this to be a group then the rules are wrong and the relevant packages should get fixed.

Last edited by V1del (2022-02-23 17:39:34)

Offline

#5 2022-02-23 17:54:39

W54J04S07T
Member
Registered: 2016-06-27
Posts: 101

Re: uaccess group

systemd-udevd[399]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Unknown group 'uaccess', ignoring
systemd-udevd[416]: hiddev0: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Only network interfaces can be renamed, ignoring NAME="usb/%k".

Then I guess, the above udev rule needs to be corrected in the distro? 

I'm pretty sure I didn't put the last line in that file...

# Only some distribuions require the below
KERNEL=="hiddev*", NAME="usb/%k", GROUP="uaccess"

Should I just comment it out?

Offline

#6 2022-02-23 19:00:45

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,738

Re: uaccess group

That should work. The entire file somewhat reads like this was put in deliberately due to distros potentially not using the uaccess tag already, I'm admittedly not entirely familiar with this software and whether it would break without that, but yes I'd consider this to be something to potentially patch out as part of the package

Last edited by V1del (2022-02-23 19:08:21)

Offline

Board footer

Powered by FluxBB