4.0-rc2 images are available for testing.

felixrising

Hi,

I've been testing 4.0 RC1 and came across a weird situation where I could not get my retropie controller configurations to update/save. It seemed to affect my ability to save Retroarch from within several different emulators that I tested too. After a while I started poking around the file system and noticed that "/opt/retropie/configs/all" was owned by root:root, while the rest of /opt/retropie/configs/* was owned by pi:pi.

After chowning /opt/retropie/configs/all and it's subfiles/folders to pi:pi it looks like my retroarch config changes are now being saved normally from within RGUI.

Is there a bug somewhere which could cause this directory to become incorrectly chowned? I had done some some updates via the setup script, etc.

BuZz

I recall perhaps an old bug, but I don't know of any currently. there were some bugs with config ownership with files in there, but the folder is chowned on launch of retropie-setup currently so it should be ok. There shouldn't be any code that would chown it incorrectly - but there may have been an earlier case where it was created incorrectly.

felixrising

@BuZz
Thanks for the response. My install is new (2 days old), based on the posted RC1 image. I'm confident I haven't executed any chown commands manually, (meaning: I'm sure it wasn't end user generated ;) ). If I notice the issue reoccur, I'll try and note what across or options i executed. The only stuff I'd done was via the setup script previously, including a script update and a packages update (both raspian and RetroPie). I could enable some auditing via auditd or shell history/trap profile.d scripting and try and capture how it occurred if it crops up again.

Cheers

BuZz

Did you launch retropie-setup script manually at all ? eg from a root shell. If it was run from root account rather than via sudo it could mess with the permissions for example. I should put some protection in against this perhaps.

Can't see anything in the code that would cause it currently (had a quick grep). But it's possible there is a bug somewhere (there are always bugs!) :)

mauruco

Hello.
I had trouble installing my garsia controller. I searched a bit and found the error on the line 69 in ps3controlle.sh. I left the line 69 + 75 commented and then I was able to install it. I think that after installing the drive ps3 the file "sixad" was created or already existed.
Regards

felixrising

Hi @BuZz,

No, I didn't su to root and run it from there, only via sudo. Probably a good idea to add some [ id -u != pi ] test as you mentioned. Anyway. I'll definitely keep an eye out and help isolate it if I can.

EDIT. I just checked, /opt/retropie/config/all is owned by root again!.

<snip>
pi@retropie:/opt/retropie/configs $ ls -ltrah
total 144K
drwxr-xr-x 7 root root 4.0K May 27 21:43 ..
drwxr-xr-x 2 pi pi 4.0K May 27 21:43 ports
-rw-r--r-- 1 pi pi 26 Aug 8 23:30 bluetooth.cfg
drwxr-xr-x 3 pi pi 4.0K Aug 8 23:43 dreamcast
drwxr-xr-x 35 root root 4.0K Aug 8 23:43 .
drwxr-xr-x 4 root root 4.0K Aug 9 01:13 all
drwxr-xr-x 2 pi pi 4.0K Aug 10 19:00 ngp
drwxr-xr-x 2 pi pi 4.0K Aug 10 19:00 ngpc
drwxr-xr-x 2 pi pi 4.0K Aug 10 19:00 pcengine
</snip>

Cheers & love the project!

felixrising

@BuZz

Strikes again!

Note that /opt/retropie/config/all is owned by root again, and just one file in the all directory:

<snip>
pi@retropie:/opt/retropie/configs/all $ ls -ltrah
total 96K
-rw-r--r-- 1 root root 202 May 27 21:43 autoconf.cfg
-rw-r--r-- 1 pi pi 70 Jul 23 23:32 runcommand.cfg
-rw-r--r-- 1 pi pi 2.9K Jul 23 23:32 runcommand-launch-dialog.cfg
-rw-r--r-- 1 pi pi 23 Jul 23 23:39 autostart.sh
drwxr-xr-x 35 root root 4.0K Aug 8 23:43 ..
drwxr-xr-x 4 root root 4.0K Aug 9 01:13 .
-rw-r--r-- 1 pi pi 111 Aug 9 01:13 scraper.cfg
-rw------- 1 pi pi 26K Aug 10 18:56 retroarch.cfg.bak
-rw-r--r-- 1 pi pi 0 Aug 10 18:57 content_history.lpl
-rw------- 1 pi pi 26K Aug 10 21:33 retroarch.cfg
drwxr-xr-x 4 pi pi 4.0K Aug 10 23:10 emulationstation
drwxr-xr-x 2 pi pi 4.0K Aug 11 17:41 retroarch-joypads
-rw-r--r-- 1 pi pi 550 Aug 11 17:53 retroarch-core-options.cfg
</snip>

BuZz

@felixrising what have you run since?

BuZz

Aah autoconf. Hmm I'll check. Please can you update RetroPie-Setup and all packages first though.

felixrising

@BuZz

Will do.

EDIT: Done. The permissions have returned to pi:pi:-

pi@retropie:/opt/retropie/configs $ ls -ltrah
total 144K
drwxr-xr-x 7 root root 4.0K May 27 21:43 ..
drwxr-xr-x 2 pi pi 4.0K May 27 21:43 ports
-rw-r--r-- 1 pi pi 26 Aug 8 23:30 bluetooth.cfg
drwxr-xr-x 3 pi pi 4.0K Aug 8 23:43 dreamcast
drwxr-xr-x 35 pi pi 4.0K Aug 8 23:43 .
drwxr-xr-x 4 pi pi 4.0K Aug 11 19:05 all
drwxr-xr-x 2 pi pi 4.0K Aug 11 19:05 ngp
...

pi@retropie:/opt/retropie/configs/all $ ls -ltrah
total 124K
-rw-r--r-- 1 pi pi 202 May 27 21:43 autoconf.cfg
-rw-r--r-- 1 pi pi 70 Jul 23 23:32 runcommand.cfg
-rw-r--r-- 1 pi pi 2.9K Jul 23 23:32 runcommand-launch-dialog.cfg
-rw-r--r-- 1 pi pi 23 Jul 23 23:39 autostart.sh
drwxr-xr-x 35 pi pi 4.0K Aug 8 23:43 ..
-rw-r--r-- 1 pi pi 111 Aug 9 01:13 scraper.cfg
-rw------- 1 pi pi 26K Aug 10 18:56 retroarch.cfg.bak
...

Pineapple12

@eddyman1us
I'm having trouble with the new setup scrip and PS3 clones. It seems the setup script installs the genuine version. When you go back to configure clone support, the screen flashes quickly but nothing really happens. My clones don't work with 4.0-rc1 but do work with 3.8.1. Also, removing the driver seems to hang.

BuZz

First post updated to 4.0-rc2