Description
The problem comes on launching, when start the first image displayed is the one set as custom background instread of the image added as (Main Menu), if you move to configuration and back the image is shown well. So I think that it lefts a check for a Main Menu image in the launcher. I'm runnig it on RPi3.
Expected behavior
When launching background image should be "Main Menu" image if exist.
Actual behavior
When launching displays image selected as background image instread of Main Menu image
Steps to reproduce the bug
- Set a Background image
- Connect via ssh and add a folder with custom backgrounds f.e. /storage/background/ and add a image named "Main Menu" inside
- Go to directories and change backgrounds folder to defined directory, in our case storage/background/
- Disable Ribbon and enable Dynamic backgrounds.
- Restart the system.
Bisect Results
It always happen, looks like it remains a check for existing Main Menu image in dynamic background folder when launching.
Version/Commit
You can find this information under Information/System Information
- RetroArch: Sorry can't find now, I'm not at home, but I use last Lakka release
Environment information
Description
The problem comes on launching, when start the first image displayed is the one set as custom background instread of the image added as (Main Menu), if you move to configuration and back the image is shown well. So I think that it lefts a check for a Main Menu image in the launcher. I'm runnig it on RPi3.
Expected behavior
When launching background image should be "Main Menu" image if exist.
Actual behavior
When launching displays image selected as background image instread of Main Menu image
Steps to reproduce the bug
Bisect Results
It always happen, looks like it remains a check for existing Main Menu image in dynamic background folder when launching.
Version/Commit
You can find this information under Information/System Information
Environment information