[SOLVED] Old folder group is now set to '100' instead of 'users'...

bugandy · 2020-12-07 15:27:41

I'm not sure if the problem is it or viceversa, however following some strange problems with wine (read below) I realized that all the old folders in my home have '100' group while not so long ago their group was 'users', and new folder have group set to 'users'.

At the moment I can select the group 'users' for the old folders but not the group '100' for the new folders, not even through chown, but if the wine prefixes have 'users' as a group I run in some crashes that do not happen if the wine folders have '100' as a group and this prevents me from testing in clean wine prefixes.

Is there anything I can do to "delete" that group 100 and go back to the previous configuration? I think that setting the folder properties by hand can make things worse because of the above.

Thank you in advance for support.

Last edited by bugandy (2020-12-08 18:00:13)

Scimmia · 2020-12-07 15:37:58

I'm guessing you migrated this home dir from a different install? Only the GID matters, not the name, so if the GID of the users group was 100 on the old install and is something else on this install, you'll get what you're seeing.

bugandy · 2020-12-07 16:09:38

Thank you, in fact few months ago I run into a fresh system installation due to a corruption of the pacman database, and at a quick look it seems that all files restored from the backup have '100' group while those created after reinstallation have 'users' group.

But now how do I clean up this mess? In other words how do I make the GID group on the new installation match the old one?

Because as I said the wine prefixes created with the new GID don't work well and this means that I can't simply change the GID to the old folders without running these crashes and in any case I cannot create new wine prefixes because they would run into these crashes.

WorMzy · 2020-12-07 16:16:37

If you don't have a static definition for 'users' in /etc/groups, systemd will dynamically create the group with a random GID via systemd-sysusers.service (specifically /usr/lib/sysusers.d/basic.conf).

Depending on the age of your previous installation, you probably had a static entry as this was shipped by default until ~late 2017 (https://github.com/archlinux/svntogit-p … b78a118a32).

Can you elaborate on "the new GID don't work well"? There is nothing special about GID 100. Unless you have a good reason to revert to that, you're just as well chgrp-ing the old files to use the new GID.

EDIT: typo in file path /etc/group

Last edited by WorMzy (2020-12-07 22:01:04)

bugandy · 2020-12-07 17:47:19

Can you elaborate on "the new GID don't work well"?

As I said in first post "new folder" (right click -> create -> folder and mkdir "new folder") are created with group "user" instead of grup "100". This is an ls example output:

drwxr-xr-x 2 myusername users 4096 7 dic 18.01 'new folder'
-rw-r--r-- 1 myusername 100 0 28 ago 2017 wget-log

In fact copying and pasting the working wine prefix it became "NOT working", so the only explanation I could find is related to the change of the group in new folder (chown seems change group correctly if I check it through ls but in fact do not make prefix working, so I think something go wrong also whit chown).

In /etc/group I found this:
users:x:985:

and no references to group 100.

but checking in my old installation backup I found its /etc/group and it contains:
users:x:100:

So... changing that 985 into 100 and the reboot could be the solution?

ps: I haven't /etc/groups but just /etc/group without s. :-\

Scimmia · 2020-12-07 17:52:51

A lot of people are having issues with wine right now, maybe related? https://bbs.archlinux.org/viewtopic.php?id=261004

Don't change the GID in groups.

bugandy · 2020-12-07 18:14:12

I don't think so, my problem is related to the wine prefix, in other words with "export WINEPREFIX='/home/myuser/.wine-old' " it works while with "export WINEPREFIX='/home/myuser/.wine' " it doesn't work and after "cp .wine-old /.../.wine-old" and "export WINEPREFIX='/.../.wine-old' " it doesn't work. I think that if it was a regression it shouldn't work at all.

~~Why shouldn't I change the GID in group?~~ edit: the answers is on the wiki, read below.

It would seem to explain why mkdir creates files with gid different from the existing ones, maybe it does not fix the problem with wine but if it corrects the problem with mkdir why not do it?

Edit:
I note nor 'groups' neither 'groups myusername' return group 100, maybe is this the cause of above mentioned wine problems?

Last edited by bugandy (2020-12-08 17:58:19)

bugandy · 2020-12-08 17:56:13

OK, now I'm a bit confused... I corrected the GID with "#groupmod -g 100 users" and reset all files in the home as owned by group users through dolphin, so the first problem can be considered solved.

But wine's problem is still here.

Edit:

Anyway I'll mark this as solved in order to avoid confusion.

Thank you for the tips on GID.

Last edited by bugandy (2020-12-08 18:42:45)

Arch Linux

#1 2020-12-07 15:27:41

[SOLVED] Old folder group is now set to '100' instead of 'users'...

#2 2020-12-07 15:37:58

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#3 2020-12-07 16:09:38

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#4 2020-12-07 16:16:37

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#5 2020-12-07 17:47:19

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#6 2020-12-07 17:52:51

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#7 2020-12-07 18:14:12

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

#8 2020-12-08 17:56:13

Re: [SOLVED] Old folder group is now set to '100' instead of 'users'...

Board footer