RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    sudoers.so is null, cant do anything.

    Scheduled Pinned Locked Moved Help and Support
    3 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      kikinaak Banned
      last edited by

      I have downloaded retropie 3.8.1 SD image, flashed it to a 32 gig sandisk card, and popped it in a pi 3.
      It boots up, goes through controller config, and launches emulationstation.
      However, most of the configuration menu options drops briefly to a shell where I get:

      [code]
      sudo: error in /etc/sudo.conf, line 0 while loading plugin 'sudoers_policy'
      sudo: unable to load /usr/lib/sudo/sudoers.so: (null)
      sudo: fatal error, unable to load plugins
      ALSA lib conf.c:1697:(snd_config_load1) toplevel:1:9316:Unexpected end of file
      ALSA lib conf.c:3778:(snd_config_update_r) /usr/share/alsa/alsa.conf may be old or corrupted: consider to remove or fix it
      lvl0: VolumeControl::init() - Failed to attach to the default card!
      ALSA lib conf.c:1697:(snd_config_load1) toplevel:1:9316:Unexpected end of file
      ALSA lib conf.c:3778:(snd_config_update_r) /usr/share/alsa/alsa.conf may be old or corrupted: consider to remove or fix it
      lvl0: AudioManager Error - Unable to open SDL audio: ALSA: Couldn't open audio device: Invalid argument
      [/code]

      Attempting to sudo anything results in the same error. I assume the alsa errors are because it hasnt been configured yet.
      /usr/lib/sudo/sudoers.so is present, but is a zero length file.

      Any idea how to get this resolved without being able to use sudo? I cannot even cleanly reboot without being root! Also, perhaps related perhaps not, Each boot retropie thinks is the first boot. I assume because conf files have not been written.

      BuZzB 1 Reply Last reply Reply Quote 0
      • BuZzB
        BuZz administrators @kikinaak
        last edited by

        @kikinaak image was written badly, or sd card is corrupt or faulty

        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

        1 Reply Last reply Reply Quote 0
        • K
          kikinaak Banned
          last edited by

          That cleared it. Thanks much, I was scratching my head since I assumed "image write ok" meant I could rely on it. Guess not.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.