From: ThatNerdyPikachu <ThatNerdyPikachu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qbittorrent-nox: symbol lookup error on launch
Date: Thu, 27 Aug 2020 21:36:30 +0200 [thread overview]
Message-ID: <20200827193630.Bj0t5y3xdbKrlLBnLhNrzmVZN82ryy1Jks-Lr7yfauY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24512@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
New comment by ThatNerdyPikachu on void-packages repository
https://github.com/void-linux/void-packages/issues/24512#issuecomment-682150476
Comment:
qbit works.
Deluge will need a rebuild before I can confirm it works, how would I go about doing that @ericonr ?
Deluge stacktrace:
```
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/deluge/_libtorrent.py", line 23, in <module>
import deluge.libtorrent as lt
ModuleNotFoundError: No module named 'deluge.libtorrent'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/bin/deluged", line 11, in <module>
load_entry_point('deluge==2.0.3', 'console_scripts', 'deluged')()
File "/usr/lib/python3.8/site-packages/deluge/core/daemon_entry.py", line 90, in start_daemon
from deluge.core.daemon import is_daemon_running
File "/usr/lib/python3.8/site-packages/deluge/core/daemon.py", line 22, in <module>
from deluge.core.core import Core
File "/usr/lib/python3.8/site-packages/deluge/core/core.py", line 28, in <module>
from deluge._libtorrent import LT_VERSION, lt
File "/usr/lib/python3.8/site-packages/deluge/_libtorrent.py", line 25, in <module>
import libtorrent as lt
ImportError: /usr/lib/python3.8/site-packages/libtorrent.so: undefined symbol: _ZNK10libtorrent5entry4dictEv
```
next prev parent reply other threads:[~2020-08-27 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:06 [ISSUE] " ThatNerdyPikachu
2020-08-27 17:45 ` ericonr
2020-08-27 17:54 ` pullmoll
2020-08-27 17:57 ` ericonr
2020-08-27 17:59 ` ThatNerdyPikachu
2020-08-27 18:05 ` ericonr
2020-08-27 18:06 ` ThatNerdyPikachu
2020-08-27 18:08 ` ericonr
2020-08-27 18:09 ` ThatNerdyPikachu
2020-08-27 18:19 ` ThatNerdyPikachu
2020-08-27 18:21 ` ericonr
2020-08-27 18:22 ` ericonr
2020-08-27 18:22 ` ThatNerdyPikachu
2020-08-27 18:23 ` pullmoll
2020-08-27 18:25 ` pullmoll
2020-08-27 18:26 ` ericonr
2020-08-27 18:26 ` pullmoll
2020-08-27 19:36 ` ThatNerdyPikachu [this message]
2020-08-27 19:37 ` ThatNerdyPikachu
2020-08-27 19:54 ` ThatNerdyPikachu
2020-08-27 20:06 ` ThatNerdyPikachu
2020-08-27 21:34 ` ericonr
2020-08-28 8:43 ` [ISSUE] [CLOSED] " pullmoll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200827193630.Bj0t5y3xdbKrlLBnLhNrzmVZN82ryy1Jks-Lr7yfauY@z \
--to=thatnerdypikachu@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).