linuxserver / docker-emulatorjs

Web based retro emulation frontend with rom scanning and automated art ingestion.
GNU General Public License v3.0
509 stars 51 forks source link

[BUG] PSX games won't load if there is a .srm file alongside the rom file #46

Closed tuxrinku closed 1 year ago

tuxrinku commented 1 year ago

Is there an existing issue for this?

Current Behavior

When trying to load a psx game that has a .srm save file in the same folder (from retropie, since I use the same roms folder for both retropie and emulatorjs), the rom won't load. It's working fine when the .srm file is deleted. It's also not a permission issue since I did a chmod -R 777 in the rom folder.

Expected Behavior

No response

Steps To Reproduce

  1. Have a psx rom with a .srm file in the same folder
  2. Start the rom from emulatorjs
  3. Retroarch shows a message "failed to load content"

Environment

- OS: Ubuntu 22.04
- How docker service was installed: package manager

CPU architecture

x86-64

Docker creation

docker run -d \
  --restart always \
  --name=emulatorjs \
  -p 3000:3000 \
  -p 4001:4001 \
  -v /home/rinku/docker/emulatorjs_docker/config:/config \
  -v /media/mergerfs_data/roms/atari2600:/data/atari2600/roms:ro \
  -v /media/mergerfs_data/roms/atari7800:/data/atari7800/roms:ro \
  -v /media/mergerfs_data/roms/ds:/data/nds/roms:ro \
  -v /media/mergerfs_data/roms/gba:/data/gba/roms:ro \
  -v /media/mergerfs_data/roms/gbc:/data/gbc/roms:ro \
  -v /media/mergerfs_data/roms/n64:/data/n64/roms:ro \
  -v /media/mergerfs_data/roms/nes:/data/nes/roms:ro \
  -v /media/mergerfs_data/roms/psx:/data/psx/roms:ro \
  -v /media/mergerfs_data/roms/megadrive:/data/segaMD/roms:ro \
  -v /media/mergerfs_data/roms/snes:/data/snes/roms:ro \
  -v /home/rinku/docker/emulatorjs_docker/data/:/data/ \
  lscr.io/linuxserver/emulatorjs

Container logs

Nothing shows in the logs, just a retroarch message saying 'failed to load content".

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service 00-legacy: starting
s6-rc: info: service 00-legacy successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/01-envfile
cont-init: info: /etc/cont-init.d/01-envfile exited 0
cont-init: info: running /etc/cont-init.d/01-migrations
[migrations] started
[migrations] no migrations found
cont-init: info: /etc/cont-init.d/01-migrations exited 0
cont-init: info: running /etc/cont-init.d/10-adduser
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

cont-init: info: /etc/cont-init.d/10-adduser exited 0
cont-init: info: running /etc/cont-init.d/20-config
chown: changing ownership of '/data/atari2600/roms': Read-only file system
chown: changing ownership of '/data/atari7800/roms': Read-only file system
chown: changing ownership of '/data/gba/roms': Read-only file system
chown: changing ownership of '/data/n64/roms': Read-only file system
chown: changing ownership of '/data/nes/roms': Read-only file system
chown: changing ownership of '/data/psx/roms': Read-only file system
chown: changing ownership of '/data/segaMD/roms': Read-only file system
chown: changing ownership of '/data/snes/roms': Read-only file system
chown: changing ownership of '/data/gbc/roms': Read-only file system
chown: changing ownership of '/data/nds/roms': Read-only file system
cont-init: info: /etc/cont-init.d/20-config exited 0
cont-init: info: running /etc/cont-init.d/99-custom-files
[custom-init] No custom files found, skipping...
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-mods: starting
s6-rc: info: service init-mods successfully started
s6-rc: info: service init-mods-package-install: starting
s6-rc: info: service init-mods-package-install successfully started
s6-rc: info: service init-mods-end: starting
s6-rc: info: service init-mods-end successfully started
s6-rc: info: service init-services: starting
s6-rc: info: service init-services successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun backend (no readiness notification)
services-up: info: copying legacy longrun ipfs (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun profile (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
[ls.io-init] done.
s6-rc: info: service 99-ci-service-check successfully started
Initializing daemon...
go-ipfs version: 0.10.0-66aa35dd43
Repo version: 11
System version: amd64/linux
Golang version: go1.17.10
2023/03/09 16:29:49 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/127.0.0.1/udp/4001/quic
Swarm listening on /ip4/172.17.0.19/tcp/4001
Swarm listening on /ip4/172.17.0.19/udp/4001/quic
Swarm listening on /p2p-circuit
Swarm announcing /ip4/109.13.110.50/tcp/4001
Swarm announcing /ip4/109.13.110.50/udp/4001/quic
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/127.0.0.1/udp/4001/quic
Swarm announcing /ip4/172.17.0.19/tcp/4001
Swarm announcing /ip4/172.17.0.19/udp/4001/quic
API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready
github-actions[bot] commented 1 year ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity