My user account doesnt have sudo despite being in sudoers. I cant run new commands i have to execute the binary. Grub takes very long to load with “welcome to grub” message. I just wanted a stable distro as arch broke and currupted my external ssd

    • digger@lemmy.ca
      3·
      9 months ago

      I’d give LMDE a look. Debian under the hood, everything works, and really slick to boot.

    • jasondj@ttrpg.network
      2·
      9 months ago

      Nah Debian 12 is weird. I recently installed on a few systems and they all do the same — usermod isn’t in roots $PATH by default, and my user account wasn’t a sudoer by default.

      I’ve added myself to sudo but I keep getting “kicked out” when I start a new shell. Have to newgrp sudo to be able to sudo again.

      • penquin@lemm.ee
        2·
        9 months ago

        On the Debian installer when it gets to entering the password when you create the user, you just skip the first password page (leave it empty) and enter your password on the next page. This adds you to the sudoers group. I’ve found this out the hard way.

      • tal@lemmy.today
        2·
        9 months ago

        I’ve added myself to sudo but I keep getting “kicked out” when I start a new shell.

        Group permissions from the /etc/group file get assigned at login. Each process will inherit group memberships from its parent.

        You can see them for a process (self being the current process) in:

        $ grep ^Groups: /proc/self/status

        The gids there correspond to the gids in /etc/group.

        That’s why the need to log out the user in question after adding the user to a group, unless you’re gonna use sg or similar to add that gid and then have all your new processes started by that process that you just started with the new gid.

        You’ll see this with all user memberships in groups on Linux. It’s not behavior specific to Debian or specific to membership in the wheel or sudo group.