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

ludusavi kept getting stuck in a loop trying to scan something #274

Open
Heus-Sueh opened this issue Sep 25, 2023 · 2 comments
Open

ludusavi kept getting stuck in a loop trying to scan something #274

Heus-Sueh opened this issue Sep 25, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@Heus-Sueh
Copy link

Ludusavi version

v0.21.0

Operating system

Linux

Installation method

Flatpak

Description

ludusavi kept getting stuck in a loop trying to scan something
image

Logs

ludusavi_rCURRENT.log

@Heus-Sueh Heus-Sueh added the bug Something isn't working label Sep 25, 2023
@mtkennerly
Copy link
Owner

This can happen if there is one game with significantly more save data than the others (e.g., 10+ GB for a single game), since the progress bar only updates per game rather than per file/byte. It should finish scanning eventually, but it could take a long time depending on the game and system. I'll look into better ways to represent progress in this kind of situation.

@mtkennerly
Copy link
Owner

I'm not sure, but the errors in your log might be a permissions issue with accessing /var/home/heus/.var/app/com.usebottles.bottles. The Flatpak version of Ludusavi now has broader permissions by default, so it should be able to read that path now. You can also use Flatseal to allow additional paths if needed.

If you still see this issue, could you try running with --env=RUST_LOG=ludusavi=trace? That way, the log file should indicate the last game being scanned that takes so much extra time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants