I've "solved" by keeping "pi" as login user and disabling password when doing sudo
thanks

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.

@djmoss haha. Happens to us all - I often leave files lying around called username@server when I fail to use scpcorrectly (missing : on the end).

Finding the root folder in /etc is a nice festive surprise :-)

@SgtJimmyRustles said in Usbromservice changed all the rom folders to root permissions:

Errors when I try a sudo chown -R pi:pi /home/pi

chown: changing ownership of '/home/pi/RetroPie': Operation not permitted

Just a little explanation for this: FAT32 (vfat in Linux) is a Windows file system that doesn't support Linux file permissions and ownerships. Those are determined by the mount options (here: uid=1000,gid=1000,fmask=0022,dmask=0022) and are immutable by commands like chmod or chown. Thus, the above error message ist normal behaviour for a vfat mount.

@cyanxx. Will do Thanks

I would like to add I dont feel retropie cashes in on this they could make a lot of money if they chose to but they dont you get the moral decent project vote no one could dispute that. You project clearly runs itself for it purpose and not for profit.

Im only talking in licensing terms in general

@youxia said in Is it still possible to ssh as root while emulationstation is working?:

I don't inherently need root in my life

Well said. 🙂 Good luck with your new build.

@mindfieldx Yes, it's part of the 4.5 release: https://github.com/RetroPie/RetroPie-Setup/commit/47035624de6e26b52a9c0d7529926c307440a6f5

0 joolswills committed to RetroPie/RetroPie-Setup fixed: make sure autoconf.cfg is owned by $user when adding/changing values

Kinda sucks all around. I love both sides here. I've been with the RetroPie group for a couple of years now. I make one little comment about how I wish N64 games ran better on the Pi3, and I got a reply back almost instantly about trying this "Odroid XU4" and the Odroid Arena build. I'd never heard of it before, and thought I'd check them out. I myself made the assumption that this build was still in it's fragile infancy, and bolstered my arrogance around their Discord channel like I owned the place. I had thought that my growing knowledge of how RetroPie works, and how to make things work with it, would help their community advance. I thought I came across cool and helpful but it was mistaken as an arrogant attempt at making the guys over there feel inadequate in their development. Because of that, I was temporary banned from their channel, and muted from their Facebook. I was completely wrong and have come full circle. My knowledge, in fact, is primitive to what the guys over there know and have been doing from the ground up. They've taken a device and built upon it with what they have available, and have come up with a working system that is as good as (if not better in some areas than) the current release of RetroPie for Raspberry Pi's. I've become humbled by the staff and have been trying to assist that community where I can. There are issues, yes, but it's something that is being worked on daily, just like how RetroPie is. They aren't focused on developing for just one SBC either. Think of how LibreELEC is developed to provide Kodi to many devices, not just Pi's. This is where their team has gone too. Yes, RetroPie also supports other devices, but RetroPie falls short in their support. You provide simple instructions on where to start then leave the user in the dust struggling to find help by saying things like "it's YOUR problem" or "contact Odroid". The problem isn't always related to the hardware.

Anyway, I just wanted to say that I think it's great what both sides are doing for the community. Sure, better support is needed, but that's no reason to say the team is producing "ugly hacks". We need to work together, not distance ourselves further apart.

There, I've said my peace. Long Live RetroPie and Long Live TheORA!

Please add more information about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

How did you install the drivers ? The root account doesn't have a password on the default Retropie image, you need to use the pi user and sudo to gain root access or run commands as root.

@mitu Thats where i looked, its gone-vanished of the face of the earth, hope the setup script fixes it

@mitu That makes sense. I understand. Thanks for your help!

@mitu Thank you!

I have not done any of this in a while and I noobed out on the basics. Much appreciated.

@hailtostarscream If you wish to create a custom version of a theme, then you can create a copy of the theme folder from /etc/emulationstation/themes/ into /opt/retropie/configs/all/emulationstation/themes/. The themes folder may need to be created.

Alternatively, you can download the theme from the relevant Github repo and place it in /opt/retropie/configs/all/emulationstation/themes/. For example, the snes mini theme can be found at https://github.com/ruckage/es-theme-snes-mini.

IIRC there is no root password.
Single user mode won't help as it requires root password too, and you need to be root to edit /boot/cmdline.txt in order to remove this.
So you can :

use a windows computer to add init=/bin/sh at the end of cmdline.txt in the /boot (fat) partition of the SD card use a linux computer (live distro if you don't have one), then mount root partition of the SD card and change ownership of sudoers.

It works.
Thanks

thanks :)

Ok guys, this time it works fine.
You were right BuZz.
Ty all.

@Kvitekvist said in Root Password prevents SSH and WinSCP:

@meleu So, press F4 + Any key, then: sudo nano /etc/ssh/sshd_config to undo the changes i did? Is this the right steps to get there?

I'm not sure if this was the only change you have made, but it seems the right thing to do.

BTW: Pressing F4 only is enough to exit emulationstation.