Hallo everyone.
I'm new in this forum and I need expert opinions about some issues, which I presume depended on the new openSUSE Leap 16.0.
The question arose after the upgrade from OpenSUSE Leap 15.6 to Leap 16.0.. Nevertheless I posted here, because I think, it isn't a distribution specific theme. In fact, it might affect other systems with distributions, which have changed their user policy / management.
But before writing about these issues I have to describe the situation.
The situation
Until Leap 15.6 all users belonged per default to the group “users” and there was in general only one admin with privileged authority.
Now, in Leap 16.0 the user organisation is very different. It depends firstly on the way the upgrade is made and secondly, if you choose to set an admin during the installation.
If you make the upgrade from scratch (for a new installation is probably the same) and decide to set an admin (optional), you get a configuration of users, which is for me unknown and quite strange:
Could this situation due to the different user policies leads to minor or even big issues?
I ask this because I noticed little strange behaviours, maybe related with:
In this case, the user "PIPPO" would belong both the group "PIPPO" and "users"
Many thanks in advance for your opinions and maybe a solving approach
I'm new in this forum and I need expert opinions about some issues, which I presume depended on the new openSUSE Leap 16.0.
The question arose after the upgrade from OpenSUSE Leap 15.6 to Leap 16.0.. Nevertheless I posted here, because I think, it isn't a distribution specific theme. In fact, it might affect other systems with distributions, which have changed their user policy / management.
But before writing about these issues I have to describe the situation.
The situation
Until Leap 15.6 all users belonged per default to the group “users” and there was in general only one admin with privileged authority.
Now, in Leap 16.0 the user organisation is very different. It depends firstly on the way the upgrade is made and secondly, if you choose to set an admin during the installation.
If you make the upgrade from scratch (for a new installation is probably the same) and decide to set an admin (optional), you get a configuration of users, which is for me unknown and quite strange:
- The first user (for example PIPPO) belongs the group PIPPO and gets some admin privileges
- Other users can be set by the first user. They can be set as simple user or privileged user.
- The admin belongs the group root and has all administrative privileges.
- All directories and files saved under the previous Leaps in /home and /Documents (each in a dedicated partition) belong to (old) user "PIPPO" of group "users";
- New directories and file created under Leap 16.0 belong to user "PIPPO" of group "PIPPO".
Could this situation due to the different user policies leads to minor or even big issues?
I ask this because I noticed little strange behaviours, maybe related with:
- Opening an "old" OpenOffice file gives the warning: "Not all attributes could be read"
- The mount of the external backup device (it belongs to PIPPO of group users) only happens after more attempts with the error message “You don't have the authorization for mounting this device.”
- The new system takes considerably more time to open a file or the file manager (Dolphin) as in the previous Leap versions, even if the system monitor does not show more resource use (CPU, memory) during this action.
In this case, the user "PIPPO" would belong both the group "PIPPO" and "users"
Many thanks in advance for your opinions and maybe a solving approach
