[Bug] App crashing on Goose

[timbueno]

muos-app version
v0.5.0

Describe the bug
App crashes at launch on muOS Goose.

To Reproduce
Steps to reproduce the behavior:

1. Install app
2. Configure app via ssh
3. Attempt to launch app
4. Witness crash after period of black screen.

Expected behavior
Opening of the app

System (please complete the following information):

• muOS version: GOOSE
• device: TrimUI Brick
• RomM version: 4.1.4

Additional context
Log trackback below:

Traceback (most recent call last):
  File "/mnt/mmc/MUOS/application/RomM/main.py", line 37, in <module>
    from romm import RomM
  File "/mnt/mmc/MUOS/application/RomM/romm.py", line 14, in <module>
    from api import API
  File "/mnt/mmc/MUOS/application/RomM/api.py", line 15, in <module>
    from PIL import Image
  File "/mnt/mmc/MUOS/application/RomM/deps/PIL/Image.py", line 97, in <module>
    from . import _imaging as core
ImportError: cannot import name '_imaging' from 'PIL' (/mnt/mmc/MUOS/application/RomM/deps/PIL/__init__.py)

[p-banuelos]

+1, RomM version 4.1.6, Anbernic RGX35XX Plus

[frasderp]

+1, RomM version 4.1.6, Anbernic RGX40XX V, happy to see it wasn't just me...

[aob1au]

I have also been having this issue, same version 4.1.6 on RG40XX V.
I haven't had time to troubleshoot much, but I just added my 2nd SD card back into the slot, and now it seems to be able to move past the initial black screen. Will try and do some more troubleshooting over next few days if I get time

[p-banuelos]

@aob1au @gantoine, in my case adding a SD card to the second slot allowed me to enter the app correctly

[wychwitch]

This is also happening to me on my Trimui Brick, which is unfortunate since I installed MuOS mostly for this app :(

Edit:

It seems to be an issue with the installation of pillow according to this

[wychwitch]

I managed to get this working by manually reinstalling pillow! I did this by sshing into muos

Here are the steps.

First, enable ssh connection in the web services menu

Then, log in with root/root

once logged in, you'll need to install pip3 by running python3 -m ensurepip --upgrade

Once installed, run pip3 install -t /mnt/mmc/MUOS/application/RomM/deps/ --upgrade pillow

After that it should all work!

Of course this is a workaround solution, but a solution nontheless

[BinaryVixen899]

Also had this issue. Reformatted my second SD card to be a single exFat partition and everything works like a charm. FWIW I did while extremely tired upgrade pillow as well, but I would not suggest others do that since you'll be modifying a python dependency as root, but your mileage may vary, it probably doesn't matter in this specific case, and (if you're the user who had the pillow issue) I have no clue what caused your issue but upgrading pillow probably was the fix for your case so nice job :), just never do that normally unless you're aware of the risks.

tl;dr
I didn't see any indication in my logs that pillow was the cause, python root is sketchy, I would not advise doing it, if you did it don't freak out. If your logs look like this, simply make sure you have a second SD card that is properly formatted as per MUOS.

[~]# cat /mnt/mmc/MUOS/application/RomM/logs/2025-10-12.log
Traceback (most recent call last):
  File "/mnt/mmc/MUOS/application/RomM/main.py", line 37, in <module>
    from romm import RomM
  File "/mnt/mmc/MUOS/application/RomM/romm.py", line 25, in <module>
    from ui import (
  File "/mnt/mmc/MUOS/application/RomM/ui.py", line 30, in <module>
    class UserInterface:
  File "/mnt/mmc/MUOS/application/RomM/ui.py", line 34, in UserInterface
    fs = Filesystem()
         ^^^^^^^^^^^^
  File "/mnt/mmc/MUOS/application/RomM/filesystem.py", line 52, in __init__
    os.mkdir(self._sd2_roms_storage_path)
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/sdcard/ROMS'

[rafadc]

In my case there is something different on how the storage works for applications.

I just went to storage section and synced to SD1 and it works. Probably the problem is that this is still looking for some files in SD1 even if you marked your apps to be in SD2

[strombolichan]

I took a look at filesystem.py and it seems what's happening is that it's trying to access /mnt/sdcard/ROMS, but is unable to access it since that file path is reserved for the second sd card slot. That's why putting in a second sd card solves the problem. What's strangest is that the file path does exist in muos even without a second sd card, but since it's mapped to a non-existent drive, romm tries to access it thinking it's there, then crashes when it can't access it.

I ended up testing this out with a newly flashed rg35xx-sp by deleting /mnt/sdcard then creating the sdcard directory and ROMS directory again. Of course I only did this to test it out and on a device I was willing to re-flash, but it should go without saying that you should not do this on your device since it will most likely break your second sd card slot until you re-flash (and even then no guarantees). But sure enough after doing this romm booted up no problem. So the issue seems to be with how romm determines whether or not the second sd card slot is populated or not.

[theycallmeboxy]

I tried to compile the app using the code following the merged #66 and I still receive the original error:

ImportError: cannot import name '_imaging' from 'PIL' (/mnt/mmc/MUOS/application/RomM/deps/PIL/init.py)

I had to use the workaround quoted to resolve. I'm using TrimUI Brick and most recent MUOS.

I managed to get this working by manually reinstalling pillow! I did this by sshing into muos

Here are the steps.

First, enable ssh connection in the web services menu

Then, log in with root/root

once logged in, you'll need to install pip3 by running python3 -m ensurepip --upgrade

Once installed, run pip3 install -t /mnt/mmc/MUOS/application/RomM/deps/ --upgrade pillow

After that it should all work!

Of course this is a workaround solution, but a solution nontheless

[wychwitch]

Yeahhhh, I've been following along and I think that the issues with the Trimui Brick are actually different from the one #66 seemingly addresses. Trimui Brick has only one SD card slot so that was never the cause of the issues. Despite that they resulted in extremely similar errors which is confusing! I think these might need to be considered different issues

I've since switched to pakui so I can't help beyond that. Im glad my temporary workaround worked in your case at least @theycallmeboxy