Here is the crash log I get which pops up every few hours (3 or 4 times a day)

Code: Select all

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235482928 (LWP 19440)]
[New Thread -1251411056 (LWP 19455)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7e1bbcb in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7  0xb7e1bdf2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8  0xb7e10f51 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9  0xb7e11252 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e5588b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e56330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb75df04c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb75df086 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#14 0xb75f1143 in KNetwork::KClientSocketBase::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb75f11e6 in KNetwork::KDatagramSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0xb6e5588b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6e561a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb71e2877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#19 0xb6e7844a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#20 0xb6deca60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6dee88f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb75b0ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6d7f1e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6ddee59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6d93d07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6e07136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6e06f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb6dee609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x080653d6 in ?? ()
#30 0xb6606ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x08064ec1 in ?? ()


before this all started a few days ago, I could have KTorrent running for weeks without a single crash.

I have four theories as to the problem:

1) I installed Kubuntu right before these crashed started. I was using regular ol' Ubuntu before and KTorrent was working fine. Maybe a package that was installed with the kubuntu-desktop package is conflicting with one that KTorrent uses in Gnome? Note: the crashing even happens when I'm using KDE

2) Around the time this started, I had an incident where I tried to play a game called "racer", and it crashed on me. I had to ctrl+F1 to log out, then log back in. When I got back into gnome, KTorrent gave me it's first error ever, one that said "unable to communicate with klauncher" (or something like that. A logout/login produced the same result, then a hard reboot fixed it completely.

3) I also discovered DHT around this time too. I had DHT turned off, but just a few hours earlier, I turned it on. Could DHT be causing it to crash like this?

4) I also discovered that enabling "use protocol encryption" allows me to connect to a bunch more peers. Could this surge of peers be causing KTorrent to crash like this?

For reference, I'm using Ubuntu 7.04, AMD 3200+ 1GB RAM

Upgrade to 2.1.4 or newer

MoDaX wrote:Upgrade to 2.1.4 or newer

Are you saying that because this crash is a known issue that has been fixed with the newest version? Or are you just saying that for the hell of it? I'm using the latest version from the ubuntu repos. Going to a version not in the repo is not something I want to do.

I turned off DHT and that seems to make the crashes go away, but all my torrents seem to me going much slower now. Is there any way to tell that my crashes are directly connected to DHT?

nbv4 wrote:

MoDaX wrote:Upgrade to 2.1.4 or newer

Are you saying that because this crash is a known issue that has been fixed with the newest version?

Yes

nbv4 wrote:I turned off DHT and that seems to make the crashes go away, but all my torrents seem to me going much slower now. Is there any way to tell that my crashes are directly connected to DHT?

Yes, they are DHT related. See KDE bug #144416 for more info if you're interested in details.