Won't launch if the download location is unavailable
Closed this issue · 4 comments
PLEASE FILL OUT THE FOLLOWING. Bug reports with limited information or lacking an attached log file may get limited or delayed help.
Describe the bug
Libation won't launch if the download location is unavailable.
In my case I had forgotten to mount the NAS volume I download to before opening Libation.
There are no visible errors explaining why it won't launch, nothing happens when I tried to launch Libation, even from the terminal. Also since it won't launch you can't change the download location from the UI.
To Reproduce
- Mount an external drive
- Open Libation, set a folder within the mounted location as download folder and close Libation
- Unmount the drive
- Try to open Libation again
Expected behavior
- Libation still launches but notifies that the download location is unavailable and needs to be changed.
Workaround
- Manually edit Settings.json to change the download location
Screenshots
Platform
- NixOS 25.05.809711.8cd5ce828d5d (Warbler)
- Libation Chardonnay v12.5.3.0 from the unstable channel
Log Files
Attach your Libation log file here. If your user folder contains the file "LibationCrash.log", attach that also.
Relevant lines : 1-222
After line 222 I realized what was happening and mounted the drive -> problem fixed.
Thank you for your logs and detailed explanation.
Libation Chardonnay v12.5.3.0 from the unstable channel
I'm not familiar. What "the unstable channel"? We made a related bugfix over a month ago, but not knowing what the unstable channel is, I don't know whether it includes this fix.
@Mbucari Am I correct that this was/should have been fixed by #1322 ?
@Mbucari Am I correct that this was/should have been fixed by #1322 ?
Cool if there's already a fix!
I'm not familiar. What "the unstable channel"? We made a related bugfix over a month ago, but not knowing what the unstable channel is, I don't know whether it includes this fix.
It's kinda like the stable/unstable branches of other distros I guess? Except that you can mix them up and have a few packages from unstable and the rest from stable, or the other way around. And probably other differences that are way over my head since I've not been using Nix for long 😅
On the stable channel Libation is quite a few versions behind, but it was updated to v12.4.9 on the unstable branch in late July and the maintainer added an autoupdate script, and right now it builds v12.5.3.0. I use the stable channel generally but unstable for Libation, which is why I mentioned it.
@rmcrackan yes, and I tested the ever-loving crap out of that PR. It's solid.
@Phantomwise The only official versions of libation are released on GitHub releases page. Anything that you get from a repository was not put there by libation's authors, and I don't think either of us know anything about those.
v12.4.9
This issue was fixed after that version. I'm going to close this for now. It seems likely that their next release will include the fix.
As @Mbucari said though, we're not supporting someone else's unofficial releases. Although Libation is free and open source, I can't be on the hook for other people's forks.