Unexpecting silent exit (v 3.1.9.2) [Bug] #1585

New issue

Closed

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

deekerman commented

2026-02-21 15:44:23 -05:00

Owner

Originally created by @vsyrovat on GitHub (Jul 20, 2014).

Ubuntu 12.04, kernel 3.15.6 or 3.16-rc5, KDE 4.13.2
Unexpected silent exit while minimized to tray. Re-run may cause 100% eating CPU (1 core) and not downloading torrents (show "checking" but not checking actually, because hdd is idle). Running in console shows following error message:

$ qbittorrent

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

Originally created by @vsyrovat on GitHub (Jul 20, 2014). Ubuntu 12.04, kernel 3.15.6 or 3.16-rc5, KDE 4.13.2 Unexpected silent exit while minimized to tray. Re-run may cause 100% eating CPU (1 core) and not downloading torrents (show "checking" but not checking actually, because hdd is idle). Running in console shows following error message: $ qbittorrent --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.9.2 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x364a0 [0x7f118028e4a0] /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7f118313397d] Segmentation fault (core dumped)

deekerman

2026-02-21 15:44:23 -05:00

closed this issue
added the
Crash
label

deekerman commented

2026-02-21 15:44:29 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jul 20, 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)
(just use this ppa until you update your distro: https://launchpad.net/~surfernsk/+archive/internet-software)

(please do a search next time)

@sledgehammer999 commented on GitHub (Jul 20, 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) (just use this ppa until you update your distro: https://launchpad.net/~surfernsk/+archive/internet-software) (please do a search next time)

deekerman commented

2026-02-21 15:44:29 -05:00

Author

Owner

@vsyrovat commented on GitHub (Jul 20, 2014):

Thanks. Upgrade libtorrent-rasterbar to 0.16.16 (with downgrade qbittorrent to 3.1.9, from surfernsk ppa) solved the problem.
This problem did not appear before with using qbittorrent for months on same distro, and appear after last upgrade, so i guessed that this was version-specifig bug. Now i think cause is in last openssl update or any other package.

(please do a search next time)
You right, but program told me "please report a bug", so I did it =)
Maybe there is a reason to include patched libtorrent-rasterbar to hydr0g3n/qbittorrent-stable ppa, specially for distros with buggy libtorrent?

@vsyrovat commented on GitHub (Jul 20, 2014): Thanks. Upgrade libtorrent-rasterbar to 0.16.16 (with downgrade qbittorrent to 3.1.9, from surfernsk ppa) solved the problem. This problem did not appear before with using qbittorrent for months on same distro, and appear after last upgrade, so i guessed that this was version-specifig bug. Now i think cause is in last openssl update or any other package. > (please do a search next time) > You right, but program told me "please report a bug", so I did it =) > Maybe there is a reason to include patched libtorrent-rasterbar to hydr0g3n/qbittorrent-stable ppa, specially for distros with buggy libtorrent?