Default Resolution Error - All Emulators Affected

k-shaps

@k-shaps I just tried entering that as well; following it by rebooting via the command "sudo reboot" still nothing. Depending on the emulator I get the same error message with a variation after the all/ in the above error message.

AlexMurphy

@k-shaps Have a look at this. https://retropie.org.uk/forum/topic/2407/can-t-select-emulator-for-rom/2

k-shaps

@AlexMurphy I tried "sudo chown -R pi:pi /opt/retropie/configs" and that did nothing. Anything else you recommend? Also do you know how this could have started? I can't seem to figure out what I could have done that would have changed this. Before I had all my emulators running CEA-16 with no issues.

AlexMurphy

@k-shaps If the link above did not work then no, sorry. Probably best to start fresh.

k-shaps

@AlexMurphy Thanks! Two more questions - I didn't follow that thread all the way through in terms of using 777 for folder names and permissions as I don't know how or where I can do that. Is there an easy guide that I can follow perhaps with screenshots or a video? Also if I do need to start fresh exactly how would I go about doing that?

BuZz

@k-shaps you should not need to do any chmod 777 ever and it's a bad idea too (makes no sense on files - since you don't want executable bit set, and also sets writable by anyone).

All user editable stuff should be owned by the user retropie was installed for - eg pi.

k-shaps

@BuZz Thank! Still a bit confused on this "All user editable stuff should be owned by the user retropie was installed for - eg pi." Where can I go to edit this or change the permissions to allow for the emulators to accept my default resolution changes?

BuZz

@k-shaps if using the image - the /opt/retropie/configs/all should be owned by pi - the command mentioned above chown -R pi:pi /opt/retropie/configs should make sure all configs have the correct ownerships.

Not sure why you are getting the error once that has been done, unless something is changing it - a 3rd party script or something else (I don't know of any issues in retropie that would cause this - there was some old bug but it was fixed a while ago).

k-shaps

@BuZz Sorry, really a noob to all this - how can I even get to that to make sure it's correct? Like where is /opt/retropie/configs/all and how do I go about editing it? Can I do this with WinSCP via SFTP or does it need to be done all on the pi? If so I don't have the first clue on how to do this. Any help would be great! Thanks!

/opt/retropie/configs/all is a folder - where it is ? that is where it is :-) that is the location

If you mean how do you access it - see

https://retropie.org.uk/docs/SSH/

ls -la /opt/retropie/configs/all

will show current permissions.

Can access the folder via windows networking also, and via sftp.

k-shaps

@k-shaps Thanks Buzz! I'll give this a whirl when I get home from work tonight. Hope this works!

k-shaps

Here is the readout I get. Any suggestions?

BuZz

@k-shaps need to use sudo chown. Also no space between - and la

k-shaps

@BuZz Here is what I get after that. Should I be all set now or do other steps need to be taken?

BuZz

@k-shaps ownership of the folder is wrong - you need to do the chown (with sudo).

k-shaps

@BuZz Cool, here is what I get after that. Any other steps need to be taken or can I reboot and try changing my default resolution again?

BuZz

@k-shaps no.. it's still wrong. the chown must have been incorrect. I need to see what you are typing in. [edit] see you updated the picture - the chown is wrong - see next post.

k-shaps

@BuZz My pi doesn't like this command....

BuZz

@k-shaps erm - why are you typing that in ?

you need to do the chown you did earlier with sudo on front.

sudo chown -R pi:pi /opt/retropie/configs

I recommend you do some reading on linux commandline before you nuke your system by accident ;-)

k-shaps

@BuZz Can you list out step by step what I need to do. I'm a noob at this. Here is what I put in based on your last instruction

BuZz

@k-shaps now it's fixed.

I don't always have time to do step by step instructions - and it's better imho that you understand what you are typing in. That said I did say earlier to put sudo in front of chown, but I meant the previous chown -R pi:pi ... etc not just chown on its own.

Check out http://linuxcommand.org/ - Then you will truly be the master of your system :)

ls means list
chown means change ownership

they are separate commands. sudo is to run something at super user privileges. sudo sudo chown means to run the chown command with super user (root) privileges.