You may succeed with giving the kmsgrab system admin capabilities, it does no longer require explicit sudo then.

sudo setcap cap_sys_admin+ep /path/to/kmsgrab

https://linux.die.net/man/8/setcap
https://linux.die.net/man/3/cap_from_text
https://man7.org/linux/man-pages/man7/capabilities.7.html

I did not debug to the end, but I strongly assume at some point DRM hits this method, which bails out with -EACCES ("Operation not permitted") when privileges are not met.

@windg said in sudo: /usr/bin/sudo must be owned by uid 0:

Now that mitu mentions it, it seems that I put the theme here : /etc/emulationstation/themes and maybe that's why it failed from FTP .

Yes, that's a root folder and so you need root permissions to work there.

Custom themes or those you want to edit should be placed in ~/.emulationstation/themes or /opt/retropie/configs/all/emulationstation/themes (they're the same, via symlink) where they can be worked on by the regular user.

Ah cool I see it works with themes too. Ah well. ;)

EmulationStaton doesn't need sudo to run and never has.
We don't support DietPi on the Pi, so I'm not sure you're using the RetroPie main repository or some fork that supports DietPi.

If by "Arcade Mode" you mean EmulationStation then:
Pressing F4 will exit EmulationStation and drop you to the Terminal. Or you could use the ES main menu by pressing "Start" and selecting "Quit" and then "Quit EmulationStation".

If you bought a custom premade image then I have no idea what software you're using and only the original seller can help you,

@polygaryd
so to run this from emulationstation @mitu said to add XINIT: /opt/retropie/ports/dunelegacy/dunelegacy in the emulators.cfg file in /opt/retropie/configs/ports/dunelegacy folder and retropie's run command will handle xinit. So I removed xserver-xorg-legacy package and tested what he told me to do. It does in fact work, no need for sudo before the xinit command with his suggestion.

As a side note he actually told me to do this for glhexen2 which needs xinit but couldnt find the game data files if you run "sudo xinit". I used what he told me and applied it to dunelegacy.

There are two more issues, one I have overcome the other I need help with. The issue I overcame was that when you run dunelegacy it says it cant find the pak files to run the game and wants them either in the "data" folder or /home/pi/.configs/dunelegacy/data". So in the start script located in /home/pi/Retropie/roms/ports/dunelegacy.sh I added "cd /opt/retropie/ports/dunelegacy" before the runcommand line. This first puts you in the dunelegacy directory with the executable and the data folder it wants, then runs the runcommand to execute the dunelegacy executable. I wish I could have the data under /home/pi/RetroPie/roms/ports like every other game ran in emulationstation but I havent figured out how to do that yet if its even possible.

The issue I need help with is I have no keyboard in dune legacy, but the mouse works. The game works fine otherwise. I cannot figure out how to get the keyboard working.

Keyboard does work in glhexen2 using XINIT: string so it must be something wrong with dunelegacy??

Any help on this would be great.

@BuZz

Yes. It was that. Changed back the bluetooth connect mode to default and is solved. It was in background mode because my SNES30 joystick was temperamental about connecting with Retropie.

I did an update from the the old Retropie version rather than a new install. And maybe because that the bug still present.

Thanks a lot.

@mitu oh, ok, i just fixed it by editing my sudoers file.

As from time to time I still have the sudo password prompt hitting me back on a system where I can't change /etc/sudoers and this is one of the first Google results: sudo password will be requested if you changed the runcommand configuration to set the CPU governor to something that is not default. It'll request password during game launch and after the game ends (to restore previous value).

So, solutions are, like described above, add entries to /etc/sudoers or change runcommand config to not touch CPU governor.

@Dwarfboysim said in sudo apt autoremove - is it safe for Retropie?:

Will I break anything? Is it recommended?

No, it will not break anything.

@mitu Seems a bit odd to launch a shell script for the sole purpose of launching another shell script, but it works. Thank you

@fabio78 glad it worked. It’s one of the first huge issues I ran into when I started to make more advanced changes.

@project_gamer You messed up the permissions on the /etc/sudoers file. Boot the PI in safe mode and restore the permissions on the file - it should be owned by root and not by the pi user. You probably chown-ed the /etc folder to the pi user :(.

Hi again,
Sorry about that, after entering amixer -i the output is amixer: Mixer default error: No such file or directory and entering amixer -l just gave the above error when I thought you said amixer -1,

And would you have any idea about how I would even read the boot/config.txt file

Thanks

@kormik home/pi is owned by pi not root