The other day, apparently a script or other essential file got scrambled/deleted/whatever, now preventing the standard user to gain 'admin' group rights and successfully complete the boot process into Gnome. Right now the boot process gets stuck right after switching from the text mode boot status messages to the graphic mode on console 7 or 8 with the spinning circle thingy. Switching to a console and logging in as the standard user results in this:
-bash: getent: command not found -bash: cut: command not found -bash: expr: command not found -bash: /usr/bin/mint-fortune: Permission denied
Below are records from some files, while googling around for quite some time, have been pointed out to be relevant for the permission management:
$ grep -i wolfi /etc/group adm:x:4:wolfi dialout:x:20:wolfi cdrom:x:24:wolfi plugdev:x:46:wolfi lpadmin:x:104:wolfi admin:x:115:wolfi sambashare:x:120:wolfi wolfi:x:1000 $ cat /etc/sudoers Defaults env_reset # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL
# less /etc/shadow ==>
wolfi entries of same pattern do exist
$ grep -i wolfi /etc/passwd wolfi:x:1000:1000:WR,,,:/home/wolfi:/bin/bash
So, how exactly does the process work, assigning
wolfithe admin group privileges to actually be able to access things like f.e.
Am I wrong to assume, that what happens on the console at log-in is independent from what the GUI is doing (or not doing) after switching from the text-mode boot message output screen on console one, to the graphics screen on console 7 or 8 (not quite sure which one it actually is on this version)?