Scan Isn't Finding Library

[bradleyesqueda-lgtm]

Using MacBook M1. I opened the program like normal, did what I had to do, and closed it. Went back immediately after and suddenly, my library is gone and it just says scanning forever and then nothing happens. Did an uninstall and reinstall, nothing. Logged in and out multiple times, nothing. Please help!

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Platform
[e.g. Windows 10, Windows 11, Mac, Linux (State distribution)]

Log Files
Attach your Libation log file here. Logs are typically in your [user]\Libation folder. (For example, on windows: C:\my_username\Libation) Also within Libation, on the first tab in Settings you can click the button 'Open log folder'. If your user folder contains the file "LibationCrash.log", attach that also.

[Mbucari]

If you go into your settings folder (~/Library/Application Support/Libation), I suspect there are two files named LibationContext.db-wal and LibationContext.db-shm. Delete those and restart Libation, and it should work. If it doesn't, attach your log files. Libation > Settings > Open Log Folder button

[bradleyesqueda-lgtm]

That worked. Thank you so much. Apologies for not including the log files.

…

On Sat, Aug 16, 2025, 9:57 PM Mbucari ***@***.***> wrote: *Mbucari* left a comment (rmcrackan/Libation#1338) <#1338 (comment)> When you opened an issue, did you see that there was already a bunch of text in the issue text box? Things like "Log Files"? What do you think all that means? I'll tell you; it's a fill-in-the-blank where you're supposed to add the information it's requesting. However, I do have lunch. If you go into your settings folder (~/Library/Application Support/Libation), I suspect there are two files named LibationContext.db-wal and LibationContext.db-shm. delete those and restart Libation, and it should work. If it doesn't, attach your log files... — Reply to this email directly, view it on GitHub <#1338 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWDMDX2CRKTJGH65RZZ3OVD3OADU5AVCNFSM6AAAAACECEHI3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJUGEZTAMZXGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Mbucari]

@bradleyesqueda-lgtm thank you for letting us know. I'm sorry for the way I spoke last night.