qBittorrent-nox Crashes #616

Closed
opened 2026-02-21 15:12:55 -05:00 by deekerman · 35 comments
Owner

Originally created by @GTRsdk on GitHub (Jul 2, 2013).

******** Information ********
To control qBittorrent, access the Web UI at http://localhost:8080
The Web UI administrator user name is: admin
02/07/2013 21:57:11 - The Web UI is listening on port 8080
02/07/2013 21:57:13 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0
02/07/2013 21:57:13 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0
02/07/2013 21:57:14 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0
02/07/2013 21:57:31 - UPnP / NAT-PMP support [ON]
02/07/2013 21:57:31 - HTTP user agent is qBittorrent v3.1.0alpha
02/07/2013 21:57:31 - DHT support [ON], port: UDP/6881
02/07/2013 21:57:31 - PeX support [ON]
02/07/2013 21:57:31 - Local Peer Discovery support [ON]
02/07/2013 21:57:31 - Encryption support [FORCED]
02/07/2013 21:57:31 - Embedded Tracker [OFF]
02/07/2013 21:57:32 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0


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

Originally created by @GTRsdk on GitHub (Jul 2, 2013). *******\* Information ******** To control qBittorrent, access the Web UI at http://localhost:8080 The Web UI administrator user name is: admin 02/07/2013 21:57:11 - The Web UI is listening on port 8080 02/07/2013 21:57:13 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0 02/07/2013 21:57:13 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0 02/07/2013 21:57:14 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0 02/07/2013 21:57:31 - UPnP / NAT-PMP support [ON] 02/07/2013 21:57:31 - HTTP user agent is qBittorrent v3.1.0alpha 02/07/2013 21:57:31 - DHT support [ON], port: UDP/6881 02/07/2013 21:57:31 - PeX support [ON] 02/07/2013 21:57:31 - Local Peer Discovery support [ON] 02/07/2013 21:57:31 - Encryption support [FORCED] 02/07/2013 21:57:31 - Embedded Tracker [OFF] 02/07/2013 21:57:32 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 0 --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.0alpha stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7f54b0ec74f0] /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7f54b2b417bd] Segmentation fault
deekerman 2026-02-21 15:12:55 -05:00
  • closed this issue
  • added the
    OS: Linux
    label
Author
Owner

@sledgehammer999 commented on GitHub (Jul 3, 2013):

We had many reports of this one. This is probably related to libtorrent-rasterbar, you probably have a stale/custom version installed. Remove it entirely and install the one from your distro's official repos.

Report here if it worked. Also what distro are you using?

@sledgehammer999 commented on GitHub (Jul 3, 2013): We had many reports of this one. This is probably related to libtorrent-rasterbar, you probably have a stale/custom version installed. Remove it entirely and install the one from your distro's official repos. Report here if it worked. Also what distro are you using?
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

I'm using the one in the Debian Wheezy repositories, which Debian Wheezy is also the distro I use.

@GTRsdk commented on GitHub (Jul 3, 2013): I'm using the one in the Debian Wheezy repositories, which Debian Wheezy is also the distro I use.
Author
Owner

@sledgehammer999 commented on GitHub (Jul 3, 2013):

From where did you obtain v3.1.0alpha? From this PPA? ->https://launchpad.net/~hydr0g3n/+archive/qbittorrent-trunk/
If yes, did you use the package intended for precise pangolin?

@sledgehammer999 commented on GitHub (Jul 3, 2013): From where did you obtain v3.1.0alpha? From this PPA? ->https://launchpad.net/~hydr0g3n/+archive/qbittorrent-trunk/ If yes, did you use the package intended for precise pangolin?
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

I compiled 164f3b761d.
And seeing the log (after restarting it with the setting which I thought was causing the issue) it has crashed again.
But this time it stayed up for a few hours before crashing.
It had seemed that the "Keep incomplete downloads at..." setting was causing the issue the first time, and made it crash a lot earlier.

On the recent crash, there's no backtrace. It only says Segmentation Fault. Which is quite odd, since I didn't use any custom CFLAGS or custom CXXFLAGS.

@GTRsdk commented on GitHub (Jul 3, 2013): I compiled 164f3b761ddfcf4045802215e7e9fd2566d5243f. And seeing the log (after restarting it with the setting which I thought was causing the issue) it has crashed again. But this time it stayed up for a few hours before crashing. It had seemed that the "Keep incomplete downloads at..." setting was causing the issue the first time, and made it crash a lot earlier. On the recent crash, there's no backtrace. It only says Segmentation Fault. Which is quite odd, since I didn't use any custom CFLAGS or custom CXXFLAGS.
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

I'm going to fetch the latest commit and recompile with --enable-debug and see if that can get some more useful information.

@GTRsdk commented on GitHub (Jul 3, 2013): I'm going to fetch the latest commit and recompile with --enable-debug and see if that can get some more useful information.
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

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

@GTRsdk commented on GitHub (Jul 3, 2013): Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.0alpha stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7fd37524e4f0] /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fd376ec87bd] Segmentation fault
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

oh and BTW: the libtorrent-rasterbar was the one from Debian Wheezy's repositories which contains qBittorrent 2.9.8, so it could very well be the older version.
Any recommended way to get the newer one?

@GTRsdk commented on GitHub (Jul 3, 2013): oh and BTW: the libtorrent-rasterbar was the one from Debian Wheezy's repositories which contains qBittorrent 2.9.8, so it could very well be the older version. Any recommended way to get the newer one?
Author
Owner

@sledgehammer999 commented on GitHub (Jul 3, 2013):

Try again your latest debug build but:

  1. Launch it in terminal with "gdb program_name program_options"
  2. When the segfault happens type into the same terminal "backtrace full"

Hopefully this will produce a more helpful backtrace.

Any recommended way to get the newer one?

Well, there is 0.16.10 in experimental...
I don't think the problem is in libtorrent though. It seems to be a problem with openssl(libcrypto).

@sledgehammer999 commented on GitHub (Jul 3, 2013): Try again your latest **debug** build but: 1. Launch it in terminal with "gdb program_name program_options" 2. When the segfault happens type into the same terminal "backtrace full" Hopefully this will produce a more helpful backtrace. > Any recommended way to get the newer one? Well, there is 0.16.10 in experimental... I don't think the problem is in libtorrent though. It seems to be a problem with openssl(libcrypto).
Author
Owner

@GTRsdk commented on GitHub (Jul 3, 2013):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2b67700 (LWP 22766)]
0x00007ffff783b5de in RC4 () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(gdb) backtrace full
#0 0x00007ffff783b5de in RC4 ()
from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)

@GTRsdk commented on GitHub (Jul 3, 2013): Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff2b67700 (LWP 22766)] 0x00007ffff783b5de in RC4 () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (gdb) backtrace full #0 0x00007ffff783b5de in RC4 () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 No symbol table info available. #1 0x0000000000000000 in ?? () No symbol table info available. (gdb)
Author
Owner

@sledgehammer999 commented on GitHub (Jul 3, 2013):

can you install debug symbols for openssl and retry? (and maybe for libtorrent too)

@sledgehammer999 commented on GitHub (Jul 3, 2013): can you install debug symbols for openssl and retry? (and maybe for libtorrent too)
Author
Owner

@sledgehammer999 commented on GitHub (Jul 5, 2013):

Any news on this? Did you try it again with -dbg packages of openssl?

@sledgehammer999 commented on GitHub (Jul 5, 2013): Any news on this? Did you try it again with -dbg packages of openssl?
Author
Owner

@GTRsdk commented on GitHub (Jul 7, 2013):

Here's what I got:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2b67700 (LWP 6395)]
RC4 () at rc4-x86_64.s:309
309 rc4-x86_64.s: No such file or directory.
(gdb) backtrace full
#0 RC4 () at rc4-x86_64.s:309
No locals.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)

@GTRsdk commented on GitHub (Jul 7, 2013): Here's what I got: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff2b67700 (LWP 6395)] RC4 () at rc4-x86_64.s:309 309 rc4-x86_64.s: No such file or directory. (gdb) backtrace full #0 RC4 () at rc4-x86_64.s:309 No locals. #1 0x0000000000000000 in ?? () No symbol table info available. (gdb)
Author
Owner

@sledgehammer999 commented on GitHub (Jul 8, 2013):

@GTRsdk as I said you must install the -dbg package of openssl

As bug #750

  1. Install -dbg package of openssl, libtorrent, qbittorrent.
  2. Open a terminal and type 'gdb qbittorrent'
  3. Then type 'run'
  4. When it crashes type 'bt' and then 'thread apply all bt'

Copy all output from the begining (gdb qbittorrent).

@sledgehammer999 commented on GitHub (Jul 8, 2013): @GTRsdk as I said you must install the **-dbg** package of openssl As bug #750 1. Install -dbg package of openssl, libtorrent, qbittorrent. 2. Open a terminal and type 'gdb qbittorrent' 3. Then type 'run' 4. When it crashes type 'bt' and then 'thread apply all bt' Copy all output from the begining (gdb qbittorrent).
Author
Owner

@GTRsdk commented on GitHub (Jul 8, 2013):

When I try to get the debug openssl, here's what I've found:
root@atom-server:~# apt-cache search openssl |grep dbg
libcurl3-dbg - debugging symbols for libcurl (OpenSSL, GnuTLS and NSS flavours)
globus-gsi-openssl-error-dbg - Globus Toolkit - Globus OpenSSL Error Handling Debug Symbols
globus-openssl-module-dbg - Globus Toolkit - Globus OpenSSL Module Wrapper Debug Symbols
libssl1.0.0-dbg - Symbol tables for libssl and libcrypto
libpion-common-4.0-dbg - lightweight HTTP interface library - common debug files
libpion-net-4.0-dbg - lightweight HTTP interface library - debug files
libpion-net-plugins-dbg - lightweight HTTP interface library - plugins debug files
python-openssl-dbg - Python 2 wrapper around the OpenSSL library (debug extension)
python3-openssl-dbg - Python 3 wrapper around the OpenSSL library (debug extension)
python-pygraphviz-dbg - Python interface to the Graphviz graph layout and visualization package (debug extension)

@GTRsdk commented on GitHub (Jul 8, 2013): When I try to get the debug openssl, here's what I've found: root@atom-server:~# apt-cache search openssl |grep dbg libcurl3-dbg - debugging symbols for libcurl (OpenSSL, GnuTLS and NSS flavours) globus-gsi-openssl-error-dbg - Globus Toolkit - Globus OpenSSL Error Handling Debug Symbols globus-openssl-module-dbg - Globus Toolkit - Globus OpenSSL Module Wrapper Debug Symbols libssl1.0.0-dbg - Symbol tables for libssl and libcrypto libpion-common-4.0-dbg - lightweight HTTP interface library - common debug files libpion-net-4.0-dbg - lightweight HTTP interface library - debug files libpion-net-plugins-dbg - lightweight HTTP interface library - plugins debug files python-openssl-dbg - Python 2 wrapper around the OpenSSL library (debug extension) python3-openssl-dbg - Python 3 wrapper around the OpenSSL library (debug extension) python-pygraphviz-dbg - Python interface to the Graphviz graph layout and visualization package (debug extension)
Author
Owner

@GTRsdk commented on GitHub (Jul 8, 2013):

I installed libssl1.0.0-dbg and re-ran the program. That's how I got the earlier output.

@GTRsdk commented on GitHub (Jul 8, 2013): I installed libssl1.0.0-dbg and re-ran the program. That's how I got the earlier output.
Author
Owner

@GTRsdk commented on GitHub (Jul 8, 2013):

I'm going to install libtorrent-rasterbar-dbg and retry it.

@GTRsdk commented on GitHub (Jul 8, 2013): I'm going to install libtorrent-rasterbar-dbg and retry it.
Author
Owner

@sledgehammer999 commented on GitHub (Jul 8, 2013):

libssl1.0.0-dbg

That's the one.

When it crashes issue also thread apply all bt in gdb

@sledgehammer999 commented on GitHub (Jul 8, 2013): > libssl1.0.0-dbg That's the one. When it crashes issue also `thread apply all bt` in gdb
Author
Owner

@sirio81 commented on GitHub (Jul 14, 2013):

I just wanted to say I'm having the same problem with qbittorrent 2.9.8 from debia wheezy 64 bit.
I've been using it since long time with no issues.
Recently I run 'aptitude safe-upgrade' and it stared crashing.
So the problem may be ralated to some lib that changed a bit (it may be libssl from what I read above).
I also compiled the latest version because I read 2.9 is not supported yet, but I still get segmentation fault:

Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v3.0.10
stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7f85a8d4f4f0]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7f85abb407bd]
Errore di segmentazione

@sirio81 commented on GitHub (Jul 14, 2013): I just wanted to say I'm having the same problem with qbittorrent 2.9.8 from debia wheezy 64 bit. I've been using it since long time with no issues. Recently I run 'aptitude safe-upgrade' and it stared crashing. So the problem may be ralated to some lib that changed a bit (it may be libssl from what I read above). I also compiled the latest version because I read 2.9 is not supported yet, but I still get segmentation fault: Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.0.10 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7f85a8d4f4f0] /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7f85abb407bd] Errore di segmentazione
Author
Owner

@sledgehammer999 commented on GitHub (Jul 14, 2013):

@sirio81
Can you build against libtorrent 0.16.10 too? Maybe the problem is there...

@sledgehammer999 commented on GitHub (Jul 14, 2013): @sirio81 Can you build against libtorrent 0.16.10 too? Maybe the problem is there...
Author
Owner

@GTRsdk commented on GitHub (Jul 15, 2013):

I decided to install libtorrent 0.16.10 and give it another go... so far it seems to be alright, but I just launched it, so I can't be too sure. I've got hope though!

@GTRsdk commented on GitHub (Jul 15, 2013): I decided to install libtorrent 0.16.10 and give it another go... so far it seems to be alright, but I just launched it, so I can't be too sure. I've got hope though!
Author
Owner

@GTRsdk commented on GitHub (Jul 15, 2013):

So far, so good... will report back in the (later) morning.
And BTW: My settings were cleared, so I don't have the exact same settings.
You can keep the settings you want, but I decided to clear mine.

@GTRsdk commented on GitHub (Jul 15, 2013): So far, so good... will report back in the (later) morning. And BTW: My settings were cleared, so I don't have the exact same settings. You can keep the settings you want, but I decided to clear mine.
Author
Owner

@sledgehammer999 commented on GitHub (Jul 15, 2013):

And BTW: My settings were cleared, so I don't have the exact same settings.

Then enable Tools->Options...->Bittorrent->Encryption mode: require encryption.

Bittorrent encryption uses RC4. From the bug report the crash happens in the RC4 function of openssl. So its best to froce RC4 encryption in order to test openssl+libtorrent 0.16.10

@sledgehammer999 commented on GitHub (Jul 15, 2013): > And BTW: My settings were cleared, so I don't have the exact same settings. Then enable Tools->Options...->Bittorrent->Encryption mode: require encryption. Bittorrent encryption uses RC4. From the bug report the crash happens in the RC4 function of openssl. So its best to froce RC4 encryption in order to test openssl+libtorrent 0.16.10
Author
Owner

@GTRsdk commented on GitHub (Jul 15, 2013):

Alright. It was set to the default (Prefer Encryption) and was still running strong 12 hours later.
Switched to required encryption, and a few hours later it is still running fine.

@GTRsdk commented on GitHub (Jul 15, 2013): Alright. It was set to the default (Prefer Encryption) and was still running strong 12 hours later. Switched to required encryption, and a few hours later it is still running fine.
Author
Owner

@fbordignon commented on GitHub (Jul 15, 2013):

Hi guys, same thing happening here.
Just start qbittorrent after a crash and the torrent is paused. I hit resume and a few seconds later it crashes.
I was using the standard 2.9.7 version that was installed with apt-get on ubuntu 12.04
openssl 1.0.1

Trying to make it work, I downloaded the source of 3.1.0alpha, compiled and got the same crash.

Proceeded with the debugger as instructed and got the following result http://pastebin.com/qWSpYDnS

Noticed that after I deleted the torrent, closed qbittorrent and start all again, it worked for more time.
No matter what settings are on the encryption the error is the same (preferred and require).
Please let me know if you need more details or procedures.

Thanks for the great torrent client. Hope it helps.

@fbordignon commented on GitHub (Jul 15, 2013): Hi guys, same thing happening here. Just start qbittorrent after a crash and the torrent is paused. I hit resume and a few seconds later it crashes. I was using the standard 2.9.7 version that was installed with apt-get on ubuntu 12.04 openssl 1.0.1 Trying to make it work, I downloaded the source of 3.1.0alpha, compiled and got the same crash. Proceeded with the debugger as instructed and got the following result http://pastebin.com/qWSpYDnS Noticed that after I deleted the torrent, closed qbittorrent and start all again, it worked for more time. No matter what settings are on the encryption the error is the same (preferred and require). Please let me know if you need more details or procedures. Thanks for the great torrent client. Hope it helps.
Author
Owner

@sledgehammer999 commented on GitHub (Jul 15, 2013):

@fbordignon

What version of libtorrent? Probably 0.15.10. Can you try with 0.16.x instead?
Also what if you disable encryption?

(offtopic)official PPA:

  1. stable
  2. unstable
@sledgehammer999 commented on GitHub (Jul 15, 2013): @fbordignon What version of libtorrent? Probably 0.15.10. Can you try with 0.16.x instead? Also what if you disable encryption? (offtopic)official PPA: 1. [stable](https://launchpad.net/~hydr0g3n/+archive/qbittorrent-stable/) 2. [unstable](https://launchpad.net/~hydr0g3n/+archive/qbittorrent-trunk/)
Author
Owner

@fbordignon commented on GitHub (Jul 15, 2013):

libtorrent is 0.15.10-1
disabling the encryption seems to work.

quick way to install libtorrent 0.16 please. I can't find the ppa for this. I have ubuntu 12.04 and I prefer not to update to 12.10 on this machine (others use it and a lot of config to redo if something goes wrong)

@fbordignon commented on GitHub (Jul 15, 2013): libtorrent is 0.15.10-1 disabling the encryption seems to work. quick way to install libtorrent 0.16 please. I can't find the ppa for this. I have ubuntu 12.04 and I prefer not to update to 12.10 on this machine (others use it and a lot of config to redo if something goes wrong)
Author
Owner

@GTRsdk commented on GitHub (Jul 16, 2013):

@fbordignon Run this:
wget https://libtorrent.googlecode.com/files/libtorrent-rasterbar-0.16.10.tar.gz
tar -xvf libtorrent-rasterbar-0.16.10.tar.gz
sudo apt-get build-dep libtorrent-rasterbar
sudo apt-get install build-essential
cd libtorrent-rasterbar-0.16.10
./configure
make
sudo make install

@GTRsdk commented on GitHub (Jul 16, 2013): @fbordignon Run this: wget https://libtorrent.googlecode.com/files/libtorrent-rasterbar-0.16.10.tar.gz tar -xvf libtorrent-rasterbar-0.16.10.tar.gz sudo apt-get build-dep libtorrent-rasterbar sudo apt-get install build-essential cd libtorrent-rasterbar-0.16.10 ./configure make sudo make install
Author
Owner

@GTRsdk commented on GitHub (Jul 16, 2013):

And if anyone is curious... I'm still running qBittorrent-nox, so that gives it an uptime of... 24 hours now!
That's a record! 😄

@GTRsdk commented on GitHub (Jul 16, 2013): And if anyone is curious... I'm still running qBittorrent-nox, so that gives it an uptime of... 24 hours now! That's a record! :smile:
Author
Owner

@fbordignon commented on GitHub (Jul 16, 2013):

built libtorrent 0.16
installed
built qbittorrent 3.1.0alpha, working good!

so the problem is in libtorrent?
funny thing is that I use qbittorrent for a while and just now it started to blow.
thanks everyone

@fbordignon commented on GitHub (Jul 16, 2013): built libtorrent 0.16 installed built qbittorrent 3.1.0alpha, working good! so the problem is in libtorrent? funny thing is that I use qbittorrent for a while and just now it started to blow. thanks everyone
Author
Owner

@GTRsdk commented on GitHub (Jul 17, 2013):

@fbordignon Still running well for you?
I just had it segmentation fault within the last 24 hours.
Same libcrypto RC4 stuff, it seems.

@GTRsdk commented on GitHub (Jul 17, 2013): @fbordignon Still running well for you? I just had it segmentation fault within the last 24 hours. Same libcrypto RC4 stuff, it seems.
Author
Owner

@GTRsdk commented on GitHub (Jul 17, 2013):

A bit off-topic: I had tried to run transmission web interface (with encryption required) on that machine too, and it always crashed. I don't have the output or it even still installed, but perhaps it's related?

@GTRsdk commented on GitHub (Jul 17, 2013): A bit off-topic: I had tried to run transmission web interface (with encryption required) on that machine too, and it always crashed. I don't have the output or it even still installed, but perhaps it's related?
Author
Owner

@Gelmir commented on GitHub (Jul 17, 2013):

It is definitely related to openssl. If you google for "libcrypto" "RC4()" segfault you'll get a lot of results for various programs using openssl.

@Gelmir commented on GitHub (Jul 17, 2013): It is definitely related to openssl. If you google for "libcrypto" "RC4()" segfault you'll get a lot of results for various programs using openssl.
Author
Owner

@GTRsdk commented on GitHub (Jul 17, 2013):

Well that's too bad.
What's recommended?
Or are we hopeless? 😦

@GTRsdk commented on GitHub (Jul 17, 2013): Well that's too bad. What's recommended? Or are we hopeless? :frowning:
Author
Owner

@fbordignon commented on GitHub (Jul 18, 2013):

still running here!
just seedling, didn't dl anything since last report.
but no crashes. maybe someone could build a version of libtorrent 0.16 for ubuntu 12.04, so that these errors would not appear anymore :)

@fbordignon commented on GitHub (Jul 18, 2013): still running here! just seedling, didn't dl anything since last report. but no crashes. maybe someone could build a version of libtorrent 0.16 for ubuntu 12.04, so that these errors would not appear anymore :)
Author
Owner

@sledgehammer999 commented on GitHub (Jul 26, 2013):

This clearly appears that it isn't a qBittorrent bug. I am closing this.

I have reported it to the Debian Bugtracker. You can track the bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717933

Other distros' users please reported it to your distro's bug trakcer too.

@sledgehammer999 commented on GitHub (Jul 26, 2013): This clearly appears that it isn't a qBittorrent bug. I am closing this. I have reported it to the Debian Bugtracker. You can track the bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717933 Other distros' users please reported it to your distro's bug trakcer too.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#616
No description provided.