Bug 20120 - Amule no longer starts (might need rebuild due to crypto)
Summary: Amule no longer starts (might need rebuild due to crypto)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-14 14:52 CET by JanKusanagi
Modified: 2017-01-14 17:35 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description JanKusanagi 2017-01-14 14:52:02 CET
Trying to start Amule in a terminal shows:

$ amule
amule: Symbol `_ZTVN8CryptoPP23FilterWithBufferedInputE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP11ProxyFilterE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP13Base64EncoderE' has different size in shared object, consider re-linking
Gtk-Message: Failed to load module "canberra-gtk-module"
 2017-01-14 14:48:25: Initialising aMule 2.4.0 (SVN 20160926) compiled with wxGTK2 v3.0.2 and Boost 1.60
 2017-01-14 14:48:25: Checking if there is an instance already running...
 2017-01-14 14:48:25: No other instances are running.
amule: symbol lookup error: amule: undefined symbol: _ZN8CryptoPP10RandomPool34GenerateIntoBufferedTransformationERNS_22BufferedTransformationERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEy



I imagine it needs to be rebuilt due to lib64cryptopp6, one of its dependencies.

Thanks! =)
JanKusanagi 2017-01-14 14:52:25 CET

CC: (none) => jan-bugs

Comment 1 David GEIGER 2017-01-14 15:33:10 CET
Thanks for your report JanKusanagi :)

Should be fixed in next amule update!

- amule-2.4.0-0.git20161207.1.mga6

CC: (none) => geiger.david68210

Comment 2 JanKusanagi 2017-01-14 16:42:41 CET
Thank you! Fast fix, as usual!


Updated version starts up ok, and seems to work fine.

Thanks! =)


P.S.- Won't do it myself this time, but in cases like this one, is it OK if I close the bug directly with this comment?
Comment 3 David GEIGER 2017-01-14 17:35:13 CET
Yes you can close this bug directly.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.