Persistent crashes with qBittorrent v3.1.11 on Debian Stable (Wheezy) #1777

New issue

Closed

opened 2026-02-21 15:50:50 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 15:50:50 -05:00

Owner

Originally created by @unimportantdavidz on GitHub (Oct 23, 2014).

I first reported this while using 3.1.10, here is my first report:

Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v3.1.10
stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x321e0 [0x7fba4043f1e0]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fba4323317d]
Segmentation fault

I cannot seem to keep qB running for more than an hour or so before it crashes like this. I was not experiencing this issue in 3.1.9. Since it names libcrypto, I feel it's relevant to say that I require full stream encryption for all transfers in my qB options.

libc version 2.13-38+deb7u6
libcrypto version 5.6.1-6

Both are the defaults installed with Debian Wheezy.

Originally created by @unimportantdavidz on GitHub (Oct 23, 2014). I first reported this while using 3.1.10, here is my first report: Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.10 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x321e0 [0x7fba4043f1e0] /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fba4323317d] Segmentation fault I cannot seem to keep qB running for more than an hour or so before it crashes like this. I was not experiencing this issue in 3.1.9. Since it names libcrypto, I feel it's relevant to say that I require full stream encryption for all transfers in my qB options. libc version 2.13-38+deb7u6 libcrypto version 5.6.1-6 Both are the defaults installed with Debian Wheezy.

deekerman

2026-02-21 15:50:50 -05:00

closed this issue
added the
Crash
label

deekerman commented

2026-02-21 15:50:55 -05:00

Author

Owner

@unimportantdavidz commented on GitHub (Oct 23, 2014):

Confirmed to still occur with 3.1.11:

Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v3.1.11
stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x321e0 [0x7fa3bb9aa1e0]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fa3be79e17d]
Segmentation fault

@unimportantdavidz commented on GitHub (Oct 23, 2014): Confirmed to still occur with 3.1.11: Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.11 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x321e0 [0x7fa3bb9aa1e0] /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fa3be79e17d] Segmentation fault

deekerman commented

2026-02-21 15:50:55 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 23, 2014):

It is a known problem with libtorrent 0.15.x. It is a fault of libtorrent. See #750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992 (<---------- solutions are in here)
(or just pull qbt+libtorrent from debian testing)

(please do a search next time)

@sledgehammer999 commented on GitHub (Oct 23, 2014): It is a known problem with libtorrent **0.15.x**. It is a fault of libtorrent. See #750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992 (<---------- solutions are in here) (or just pull qbt+libtorrent from debian testing) (please do a search next time)