-
Notifications
You must be signed in to change notification settings - Fork 670
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
[Spotify] Plugin install, undefined symbol #5521
Comments
I've just loaded up the 1.3.1 version to try this out. I'd be tempted to say that you have a missing library, have a look at the full list of dependancies here Also try running from terminal and see if your output is similar to mine or if anything else appears I have this as my console output: |
I have the same issue, also on Arch Linux with Clementine 1.3.1-3. The referenced symbol seems to be part of crypto++, which I have installed (5.6.5-2).
|
Seems to be a problem with crypto++, I just downgraded the package to 5.6.4 and everything is working ok. I'm gonna post the bug in their repo. |
I would suppose the problem is that the arch maintainer built clementine against cryptopp 5.6.4, while the current version in the repos is 5.6.5 |
Seems to be solved: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/clementine&id=12af6a0cac31e9912cc36bcbddea2128f4001b7a (bug tracker: https://bugs.archlinux.org/task/51718). It's weird crypto++ broke the ABI with a patch version. |
Yes, we fumbled the 5.6.5 release. More correctly, I fumbled it. Our sincerest apologies for that. If interested, more of the back story is we caught Issue 277/CVE-2016-7420. It was a procedural finding that effectively said, "You did not tell someone they needed to defined Stepping back to 10,000 feet, we recognized the bigger problem was (1) the library did not ship in the recommended or "best state", (2) users needed to do something special to get into a recommended or "best state", and (3) users needed to RTFM to figure out what the best state was. The short of that is, "If RTFM was going to work, then it would have happened by now". At 5.6.5 we shipped the library in the recommended or "best state". Effectively, we sacrificed distros for users. It was an awful decision to make and it really bothered everyone who is part of the Crypto++ project. We knew someone was going to get the pointy end of the stick. We thought we had nearly all of the bases covered the 5.6.5. We knew 5.6.5 needed a recompile to vet the If interested, here's where Debian, Fedora and Gentoo experienced the pain point (Clementine was added to the list):
If interested, we maintain a wiki page for Distributions. The section Post-Release Patches has a handful of bug reports you might be interested in. I try to keep commits coupled tightly to a report, so you should not have any trouble cherry picking. I strongly encourage Clementine to cherry-pick the changes for Crypto++ Issue 283 and Crypto++ 332. As far as I know, they are the two "symbol problems" for 5.6.5. Finally, I also maintain a private mailing list for distros and other interested parties. Its very low volume and only makes contact with maintainers and packagers when necessary. If you want to be added to the discussions, then email me at _noloader, gmail account_. |
Before posting
Please follow the steps below and check the boxes with [x] once you did the step.
System information
Please provide information about your system and the version of Clementine used.
Expected behaviour / actual behaviour
Steps to reproduce the problem (only for bugs)
clementine: symbol lookup error: clementine: undefined symbol: _ZN8CryptoPP6SHA5129InitStateEPy
The text was updated successfully, but these errors were encountered: