arakasi72 / rtinst

seedbox installation script for Ubuntu and Debian systems
MIT License
1.22k stars 262 forks source link

Crash on Ubuntu 20.04.1 LTS #539

Open svu opened 3 years ago

svu commented 3 years ago

Installed libtorrent/rtorrent 0.13.8/0.9.8 rtorrent crashes immediately after I open rutorrent in my browser: Caught Segmentation fault, dumping stack: /usr/bin/rtorrent(+0x458eb) [0x5570cd92e8eb] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7fefc92303c0] /lib/x86_64-linux-gnu/libc.so.6(+0x18e6ff) [0x7fefc8fbb6ff] /usr/lib/x86_64-linux-gnu/libxmlrpc.so.3(+0xd30a) [0x7fefc925630a] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(+0x5ab1) [0x7fefc88dcab1] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(+0x7bd6) [0x7fefc88debd6] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(+0x8db2) [0x7fefc88dfdb2] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(+0x967b) [0x7fefc88e067b] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(+0xa1d0) [0x7fefc88e11d0] /usr/lib/x86_64-linux-gnu/libxmlrpc_xmlparse.so.3(xmlrpc_XML_Parse+0x136) [0x7fefc88de436] /usr/lib/x86_64-linux-gnu/libxmlrpc.so.3(xml_parse+0xd3) [0x7fefc9256563] /usr/lib/x86_64-linux-gnu/libxmlrpc.so.3(xmlrpc_parse_call+0xb0) [0x7fefc9256a60] /usr/lib/x86_64-linux-gnu/libxmlrpc_server.so.3(xmlrpc_registry_process_call2+0xc5) [0x7fefc92639f5] /usr/lib/x86_64-linux-gnu/libxmlrpc_server.so.3(xmlrpc_registry_process_call+0x29) [0x7fefc9263b89] /usr/bin/rtorrent(+0x1a4bcc) [0x5570cda8dbcc] /usr/bin/rtorrent(+0x1a3717) [0x5570cda8c717] /usr/bin/rtorrent(+0x1a4117) [0x5570cda8d117] /usr/lib/x86_64-linux-gnu/libtorrent.so.21(_ZN7torrent9PollEPoll7performEv+0xca) [0x7fefc92cae4a] /usr/lib/x86_64-linux-gnu/libtorrent.so.21(_ZN7torrent9PollEPoll7do_pollEli+0x69) [0x7fefc92caf59] /usr/lib/x86_64-linux-gnu/libtorrent.so.21(_ZN7torrent11thread_base10eventloopEPS0+0x12b) [0x7fefc9300f6b] Aborted (core dumped)

svu commented 3 years ago

looks like it is using system libxmlrpc from /usr/lib/x86_64-linux-gnu instead of the custom built by the script into /usr/lib. Should that conflict be detected and resolved?

V33m commented 3 years ago

Did you use rtinst after a clean install? If not, then you'll likely face issues similar to this. Given all the different scenarios out there, we simply have to base the script on a clean install.

svu commented 3 years ago

Yes I did used it on clean ubuntu install. But that install included system version of libxmlrpc

V33m commented 3 years ago

Are you able to find out if libxmlrpc from the script rtinst actually is installed? Can you please share a log of the installation?

svu commented 3 years ago

Sure I can share, where would I find it? Thanks

V33m commented 3 years ago

Add -l as a parameter when running rtinst and you will find your log at ~/rtinst.log. Even better is if you add set -x in the rist script as well by sudo sed -i "/^\(\s\|#\)*#\!\/bin\/bash/ a\set -x" /etc/rtinst/scripts/rtinst && sudo chmod +x /etc/rtinst/scripts/rtinst && sudo rtinst -l && cat $(eval echo "~$user")/rtinst.log

inode- commented 3 years ago

apt-get remove libxmlrpc-core-c3 libxmlrpc-core-c3-dev libxmlrpc-epi0

will solve the problem, but the default packages of libxmlrpc will not be available on the system.

benjschro commented 3 years ago

@inode- FYI, I used your suggestion and it fixed my problem.

I had the same issue as the OP. Is this something that can be checked and automated? Otherwise I think the only reliable way to manage this is to change the rpath of rtorrent to use specific versions of libraries instead of ones already installed in the system.