Results 1 to 10 of 11
Enjoy an ad free experience by logging in. Not a member yet? Register.
Change system-wide "default" admin profile?
Long story short I *think* I tracked it back to a corrupted permission in the home folder of the user I created at install (user 1) and for the life of me I couldn't get it fixed.
I ended up creating a new user and migrating *everything* from user 1 to user 2.
After lots of config and touble shooting I think I've solved every problem but 1:
When I use "deep" GUI tools like synaptic or users and groups they ask for the password of user 1 instead of user 2.
How do I tell the system that user 1 is no longer the default admin profile and that user 2 is now the default admin so I can delete the old corrupted user profile?
Replace User1 with User2 in /etc/sudoers file. Make sure not to edit anything else. Use visudo to edit sudoers file.
Ok thanks for the tip. I'll check when I get home (work / memory /senile). But I thought I did that already?
12-29-2012 #4Ok thanks for the tip. I'll check when I get home (work / memory /senile). But I thought I did that already?
Like I said: work /memory/senile.
Now, thinking about it, I *think* I might have both user 1 and user 2 in sudoers. I think I left the old in so I could su between them and have sudo powers on both profiles as I worked to migrate everything.
Is there like an order of placement preference for who is default? I ask because if they're both still in there then they're listed:
Is the last one in the list the "default" or is User1 still default because I haven't removed it from the file yet?
Actually, I just checked and I was right the first time. User2 is the only one at the bottom of the file when I open sudo visudo. Where else can I look?
Could you post the contents of /etc/sudoers file here?
# # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d bella ALL=(ALL) ALL %jupiter ALL=NOPASSWD: /usr/lib/jupiter/scripts/bluetooth, /usr/lib/jupiter/scripts/camera, /usr/lib/jupiter/scripts/cpu-control, /usr/lib/jupiter/scripts/resolutions, /usr/lib/jupiter/scripts/rotate, /usr/lib/jupiter/scripts/touchpad, /usr/lib/jupiter/scripts/vga-out, /usr/lib/jupiter/scripts/wifi
Until I get this fixed how do I re-enable the User1 profile from the command line?
OK, I foundCode:
passwd -u username
But, somewhere in the system she's still listed as the default admin profile.
It looks like User1 is in sudo group and User2 is not. Execute id command as User1 and User2. Check if there is any difference in Groups.
Add User2 in sudo Group. You can do it in GUI as well as through command line.
sudo usermod -a -G sudo user2