[Bug] Automatic library scan not triggering upon filesystem changes.

[nicktheone]

RomM version
4.6.1

Describe the bug
ROMM is not automatically picking up new ROMs added to the library folder.

To Reproduce
Add a new ROM to the library folder (an .nds ROM file, at present), wait for the set delay to expire and check if ROMM has picked it up.

Expected behavior
ROMM should be picking up the new ROMs after the set time delay for an automatic expires.

Server (please complete the following information):

• OS: Debian 12
• Docker: Docker 29.1.5

Client (please complete the following information):

• Device: PC
• OS: Windows 11
• Browser: Firefox
• Version: 147

[gantoine]

you have ENABLE_RESCAN_ON_FILESYSTEM_CHANGE=true set?

[nicktheone]

Yes, of course. I've forgot to mention it but I've set both ENABLE_RESCAN_ON_FILESYSTEM_CHANGE=true and RESCAN_ON_FILESYSTEM_CHANGE_DELAY=5 and the feature is showing as enabled in the Administration pane.

[gantoine]

nothing in the container logs when you add a new game to the folder?

[nicktheone]

[romm] 
[15:41:32] 1 change detected
[romm] 
[15:41:32] process already dead, exit code: 0
[romm] 
[15:41:33] 1 change detected
[romm] 
[15:41:38] SIGINT timed out after 5 seconds
[romm] 
[15:41:38] process has not terminated, sending SIGKILL
[romm] 
[15:41:38] 1 change detected
[romm] 
[15:41:43] SIGINT timed out after 5 seconds
[romm] 
[15:41:43] process has not terminated, sending SIGKILL

This is all it's showing. ROMM picks up the changes immediately but then it loops like that until the transfer is complete (I've tried adding files through a Samba share, uploading them through a file management webapp or straight uploading them through an SSH connection). The scan never happens and the files are never added to ROMM library.