-
Notifications
You must be signed in to change notification settings - Fork 232
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
Segfault #78
Comments
woha a lot of details here. I must admit, I do not really understand what I'm looking at. @gregf when does it segfault? Are you running any command line arguments? Anything special in the config file? |
@karlstav Any command I run it segfaults. If I remove my config it appears to work. So I think it has something to do with iniparser? I don't see anything invalid in my config myself.
|
could you could try to comment out the two lines you changed (method and source), just to check? |
I did that playing around with it, and it didn't make any difference. On Thu, Oct 29, 2015 at 07:33:38AM -0700, karl wrote:
--gregf |
iniparser-4.0_2 if you want to try and replicate the issue. |
are you using a system wide iniparser or the bundled one? I have tried with both the bundled and the newest from github without any issues. |
Looks like system wide.
|
could you try to compile it with the bundled instead? are you by any chance using the package from AUR? It is kinda out of date, although it should work. |
I narrowed it down to this line in the config file.
The comment to the right of stereo for some reason causes the segfault. I'm not using archlinux. I tried both the package for voidlinux.eu and I tried compiling it by hand. |
I think its a line length issue with iniparser. It segfaults on the word center. In the sentence |
This appears to be fixed with the bundled version and the latest version of cava. So i'm very sorry to have wasted your time. Voidlinux has 0.3.5 packaged and it looks like the latest version is 0.3.5.9. I'm going to submit a pull request to update there package. Thank you for your time, and again sorry to have wasted it. |
@gregf no problem 😉 There must have been a problem with the version of iniparser used in Voidlinux, nothing have been done with cava lately than can have caused/fixed this. For what it's worth this made me realize that the lines on the comment in the config file are waaaaay to long, looks like a mess... |
Void's iniparser-package got patched and plays nicely with cava. So yes, Voidlinux' Cava-Package is working again. |
The text was updated successfully, but these errors were encountered: