2

I have some issues with permission from various apps (such as accessing serial ports, despite being the dialout group, or contacting to Docker daemon, despite being in the docker group -- I think) and I need clarifications here.

When I run the id command, I get this:

uid=1000(eudoxos) gid=1000(eudoxos) groups=1000(eudoxos)

I understand that Debian/Ubuntu create separate primary group for each user (gid 1000).

When I look inside /etc/group, I see my username in a number of other groups (those are secondary groups, right?), such as adm, sudo, audio, plugdev, fuse, docker, dialout and so on). The id command should report those, as per GID, current, primary, supplementary, effective and real group IDs? but I don't see anything like that in the output. What am I missing? Is something misconfigured? (I did login anew after changing groups already)

EDIT: more information

$ grep eudoxos /etc/group
adm:x:4:eudoxos,syslog
dialout:x:20:eudoxos
cdrom:x:24:eudoxos
floppy:x:25:eudoxos
sudo:x:27:eudoxos
audio:x:29:eudoxos,pulse,timidity
dip:x:30:eudoxos
video:x:44:eudoxos
plugdev:x:46:eudoxos
eudoxos:x:1000:
fuse:x:104:eudoxos
lpadmin:x:111:eudoxos
admin:x:117:eudoxos
vboxusers:x:123:eudoxos
sambashare:x:129:eudoxos
pgrimaging:x:1003:eudoxos
docker:x:151:eudoxos
kvm:x:152:eudoxos
libvirt:x:153:eudoxos

and

$ grep group /etc/nsswitch.conf
group:          compat systemd
netgroup:       nis
Improve this question
11
  • Can you add the output of grep eudoxos /etc/group and grep group /etc/nsswitch.conf to your question. Commented Jan 27, 2019 at 14:01
  • added as edit :) Commented Jan 27, 2019 at 14:16
  • Hm...strange. Should work. Which distribution and version are you running? Does groups also do not show the groups? id -a? Commented Jan 27, 2019 at 14:37
  • Ubuntu 18.04. id -a shows the same as id (i.e. uid=1000(eudoxos) gid=1000(eudoxos) groups=1000(eudoxos)) and groups only says eudoxos. ... Commented Jan 27, 2019 at 14:39
  • 1
    Does this answer your question? Missing groups at each startup Commented Jun 23, 2024 at 18:26

1 Answer 1

Reset to default
1

As indicated in my last comment, the issue only happens when logging into the GUI session (not in terminal). This lead quickly to finding reports of the same allover forums/bugzillas. It is a bug in lightdm (which I incidentally use) which has not been fixed. Commenting out pam_kwallet*.so from its config file and reboot fixes the issue.

Thanks to all those who were helpfully commenting on the issue above.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.