Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error deleting themes in RG351M #392

Closed
egcarrano opened this issue May 14, 2021 · 3 comments · Fixed by #564
Closed

Error deleting themes in RG351M #392

egcarrano opened this issue May 14, 2021 · 3 comments · Fixed by #564
Assignees
Labels

Comments

@egcarrano
Copy link

Describe the bug

I cannot remove themes that I have installed in 351ELEC Reborn for RG351M.

To Reproduce

Steps to reproduce the behavior:

  1. Press Start
  2. Go to Dowloads -> Themes
  3. Select any downloaded theme
  4. Try to remove the theme

Expected behavior

At first, I flashed 351ELEC Reborn from scratch. Then I installed all themes currently available in order to check each one. After checking them I tried to delete some themes but I received an error message saying that the theme could not be removed. I received the same error message for 3 or 4 different themes. In addition, I was not trying to delete the theme I was currently using.

Device (please complete the following information):

I am using 351ELEC Reborn in RG351M.

@Dahak66
Copy link

Dahak66 commented May 14, 2021

Just adding that this is also the case on the 351V as well, and has been this way at least since the previous (formerly final) build. Deletion from within the file manager does work, though, and the download script does recognise deleted themes as available to download.

@egcarrano
Copy link
Author

Thank You. Could You tell me where the themes are stored?

@Dahak66
Copy link

Dahak66 commented May 15, 2021

From the filemanager, go to /etc/emulationstation/themes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants