-
-
Notifications
You must be signed in to change notification settings - Fork 724
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
Waybar 0.10.3, libcava 0.10.1, segfaults with cava module enabled in bar configuration #3276
Comments
Yeah it seems to be something wrong when According to https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html , the value should default to |
Yeah, need to add validation for $XDG_CONFIG_HOME. |
Hi @OriginCode , fix is merged. Please try again with the master branch |
Yeah it doesn't segfault now as it just cannot find the file lol. You might want to consider implement the spec to check |
Checking your point... |
Hi @OriginCode , thank you for your feedback. Related merge request is created to the original cava upstream. See karlstav/cava#565. Once it's done I'll do sync with libcava and bump libcava version. |
Hi @OriginCode , please check with the new commits. Now it should be fine. If it's so, please close the issue |
@LukashonakV It still doesn't recognize |
Hi @OriginCode, can you explain what you're expecting from cava when the environment variable is not defined in the system ? |
@LukashonakV It should look for |
Hi @OriginCode , I fixed the issue when libcava expands user variables and constructs file path for opening. Please update waybar or libcava-0.10.3 and let me know about results. Thanks |
I still get |
@OriginCode you should use |
Both don't work on my end. :( |
This error means you have not configured xdg variable . |
As I mentioned before, according to https://specifications.freedesktop.org/basedir-spec/latest/index.html#variables when the variable is not set, it should look up |
Actually, I'm still thinking of fallbacks... the reason, to me it seems obvious it's the user responsibility to provide correct content into the API. When the fallback happened, it was not clear which config now is used So, for now, fallback mechanic is not considered. And the new libcava version just fixed memory leaking |
No pressure, at least |
Tested with
--buildtype=debug
.waybar -l trace
:gdb waybar
:Seems to be related to config file loading?
The text was updated successfully, but these errors were encountered: