Version: 2.1.3 (using KDE KDE 3.5.6) Installed from: Gentoo Packages Compiler: gcc-4.1.2 OS: Linux Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47247877533808 (LWP 4612)] [New Thread 1090525504 (LWP 5605)] [New Thread 1082132800 (LWP 5604)] [KCrash handler] #5 dht::ParseRsp (dict=0xf14ae0, srv=0x92a830) at rpcmsg.cpp:163 #6 0x00002af8bcae20ab in dht::MakeRPCMsg (dict=0xf14ae0, srv=0x92a830) at rpcmsg.cpp:203 #7 0x00002af8bcae222c in dht::RPCServer::readPacket (this=0x92a830) at rpcserver.cpp:131 #8 0x00002af8bcae250d in dht::RPCServer::qt_invoke (this=0x92a830, _id=2, _o=0x7fffee4d9a90) at rpcserver.moc:82 #9 0x00002af8be87055c in QObject::activate_signal (this=0x92a700, clist=<value optimized out>, o=0x7fffee4d9a90) at kernel/qobject.cpp:2356 #10 0x00002af8be871203 in QObject::activate_signal (this=0x7fffee4d9890, signal=<value optimized out>) at kernel/qobject.cpp:2325 #11 0x00002af8bdcb21af in KNetwork::KClientSocketBase::qt_invoke ( this=0x92a700, _id=2, _o=0x7fffee4d9b80) at kclientsocketbase.moc:204 #12 0x00002af8bdcb224a in KNetwork::KDatagramSocket::qt_invoke ( this=0x92a700, _id=2, _o=0x7fffee4d9b80) at kdatagramsocket.moc:87 #13 0x00002af8be87055c in QObject::activate_signal (this=0x895920, clist=<value optimized out>, o=0x7fffee4d9b80) at kernel/qobject.cpp:2356 #14 0x00002af8be871135 in QObject::activate_signal (this=0x895920, signal=<value optimized out>, param=<value optimized out>) at kernel/qobject.cpp:2449 #15 0x00002af8be88ac6b in QSocketNotifier::event (this=0x895920, e=0x7fffee4d9e80) at kernel/qsocketnotifier.cpp:258 #16 0x00002af8be819fe5 in QApplication::internalNotify ( this=<value optimized out>, receiver=0x895920, e=0x7fffee4d9e80) at kernel/qapplication.cpp:2635 #17 0x00002af8be81abe7 in QApplication::notify (this=0x7fffee4da0e0, receiver=0x895920, e=0x7fffee4d9e80) at kernel/qapplication.cpp:2358 #18 0x00002af8bdc7abee in KApplication::notify (this=0x7fffee4da0e0, receiver=0x895920, event=0x7fffee4d9e80) at kapplication.cpp:550 #19 0x00002af8be8101cb in QEventLoop::activateSocketNotifiers (this=0x5f0ff0) at kernel/qapplication.h:496 #20 0x00002af8be7d0ef3 in QEventLoop::processEvents (this=0x5f0ff0, flags=<value optimized out>) at kernel/qeventloop_x11.cpp:383 #21 0x00002af8be82e722 in QEventLoop::enterLoop (this=0x7fffee4d9890) at kernel/qeventloop.cpp:198 #22 0x00002af8be82e5d2 in QEventLoop::exec (this=0x7fffee4d9890) at kernel/qeventloop.cpp:145 #23 0x000000000042eaab in main (argc=<value optimized out>, argv=0x7fffee4da418) at main.cpp:125 #24 0x00002af8c0d2d374 in __libc_start_main (main=0x42e7a0 <main>, argc=3, ubp_av=0x7fffee4da418, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffee4da408) at libc-start.c:238 #25 0x0000000000423459 in _start () Current language: auto; currently c
SVN commit 655895 by guisson: Fixed crash in DHT, failed to check for empty QByteArray BUG: 144416 M +6 -1 rpcmsg.cpp --- trunk/extragear/network/ktorrent/libktorrent/kademlia/rpcmsg.cpp #655894:655895 @@ -160,7 +160,12 @@ } - Uint8 mtid = (Uint8)dict->getValue(TID)->data().toByteArray().at(0); + QByteArray ba = dict->getValue(TID)->data().toByteArray(); + // check for empty byte arrays should prevent 144416 + if (ba.size() == 0) + return 0; + + Uint8 mtid = (Uint8)ba.at(0); // find the call const RPCCall* c = srv->findCall(mtid); if (!c)
*** Bug 144603 has been marked as a duplicate of this bug. ***
*** Bug 144610 has been marked as a duplicate of this bug. ***
So when exactly was this fixed? Is there a specific version I need to upgrade to?
Are you sure that http://bugs.kde.org/show_bug.cgi?id=144603 and http://bugs.kde.org/show_bug.cgi?id=144610 is the same this bug?? in this bug, there is not reference to library /usr/lib/libqt-mt.so.3 who have many reference those bugs line 10,11 and from 16 to 28 #10 0xb6e3188b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 (...) #28 0xb6dca609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
Yes this the same bloody bug which has been reported about six times in the last 3 days.
*** Bug 144622 has been marked as a duplicate of this bug. ***
I assume there are so many duplicates being posted because (Ku|Edu|U)buntu Feisty seems to suffer from it, and there are a bunch of new users out there now that it was released. Still, it says that this is RESOLVED, but what version has the fix?
*** Bug 144634 has been marked as a duplicate of this bug. ***
Like I already mentioned in every dupe, the fix is in 2.1.4
*** Bug 144656 has been marked as a duplicate of this bug. ***
*** Bug 144658 has been marked as a duplicate of this bug. ***
*** Bug 144705 has been marked as a duplicate of this bug. ***
*** Bug 144704 has been marked as a duplicate of this bug. ***
*** Bug 144716 has been marked as a duplicate of this bug. ***
*** Bug 144737 has been marked as a duplicate of this bug. ***
*** Bug 144736 has been marked as a duplicate of this bug. ***
*** Bug 144768 has been marked as a duplicate of this bug. ***
*** Bug 144776 has been marked as a duplicate of this bug. ***
*** Bug 144790 has been marked as a duplicate of this bug. ***
*** Bug 144824 has been marked as a duplicate of this bug. ***
*** Bug 144813 has been marked as a duplicate of this bug. ***
*** Bug 144833 has been marked as a duplicate of this bug. ***
*** Bug 144808 has been marked as a duplicate of this bug. ***
*** Bug 144908 has been marked as a duplicate of this bug. ***
*** Bug 144906 has been marked as a duplicate of this bug. ***
*** Bug 144926 has been marked as a duplicate of this bug. ***
*** Bug 144971 has been marked as a duplicate of this bug. ***
*** Bug 144991 has been marked as a duplicate of this bug. ***
*** Bug 145025 has been marked as a duplicate of this bug. ***
*** Bug 145048 has been marked as a duplicate of this bug. ***
*** Bug 145066 has been marked as a duplicate of this bug. ***
*** Bug 145069 has been marked as a duplicate of this bug. ***
*** Bug 145070 has been marked as a duplicate of this bug. ***
*** Bug 145071 has been marked as a duplicate of this bug. ***
*** Bug 145088 has been marked as a duplicate of this bug. ***
*** Bug 145098 has been marked as a duplicate of this bug. ***
*** Bug 145201 has been marked as a duplicate of this bug. ***
*** Bug 145208 has been marked as a duplicate of this bug. ***
*** Bug 145255 has been marked as a duplicate of this bug. ***
*** Bug 145260 has been marked as a duplicate of this bug. ***
*** Bug 145304 has been marked as a duplicate of this bug. ***
*** Bug 145273 has been marked as a duplicate of this bug. ***
*** Bug 145272 has been marked as a duplicate of this bug. ***
By the way, I've found that disabling DHT has stopped the application from crashing.
Same here.
*** Bug 145509 has been marked as a duplicate of this bug. ***
*** Bug 145659 has been marked as a duplicate of this bug. ***
*** Bug 145675 has been marked as a duplicate of this bug. ***
*** Bug 145689 has been marked as a duplicate of this bug. ***
*** Bug 145694 has been marked as a duplicate of this bug. ***
*** Bug 145869 has been marked as a duplicate of this bug. ***
2 things: 1) For me, it still crashes randomly when not using DHT 2) When i try to stop or start multiple torrents at once, there is a 50% Chance that it will crash
Then that is another bug, open a new bug and post backtrace, and don't forget to mention the version of ktorrent you are using
UPDATE: FIXED! The error is with the Ubuntu that is the EXE version (https://wiki.ubuntu.com/install.exe/Prototype). I installed from the CD that i recieved from Ubuntu (7.04) and uninstalled the exe one. and the problem is no more!
*** Bug 146137 has been marked as a duplicate of this bug. ***
*** Bug 146148 has been marked as a duplicate of this bug. ***
*** Bug 146310 has been marked as a duplicate of this bug. ***
*** Bug 146558 has been marked as a duplicate of this bug. ***
*** Bug 146604 has been marked as a duplicate of this bug. ***
*** Bug 146645 has been marked as a duplicate of this bug. ***
*** Bug 146656 has been marked as a duplicate of this bug. ***
*** Bug 146772 has been marked as a duplicate of this bug. ***
Uhm - I'm one of the newbies running feisty and I get this problem too. I am using KTorrent 2.1 (KDE 3.5.6) and I don' seem to have an upgrade function in Adept or anywhere. Did I report this the right place and why is this being bug "resolved", what is the fix, if any? Regards, Kristian Lund
Upgrade to 2.1.4 or later, there are feisty packages available on the ktorrent.org
Newbies should report bugs exclusively with their distro... it would've prevented the million duplicates... The fix is to upgrade. Ask for help in #ubuntu...
> ------- Additional Comments From lundse gmail com 2007-06-19 10:58 > ------- Uhm - I'm one of the newbies running feisty and I get this > problem too. I am using KTorrent 2.1 (KDE 3.5.6) and I don' seem to > have an upgrade function in Adept or anywhere. Did I report this the > right place and why is this being bug "resolved", what is the fix, if > any? > > Regards, > Kristian Lund Switch off DHT: Settings > Configure KTorrent > General and uncheck the box "Use DHT to get additional peers" Zebidiah
*** Bug 147183 has been marked as a duplicate of this bug. ***
*** Bug 147242 has been marked as a duplicate of this bug. ***
*** Bug 148078 has been marked as a duplicate of this bug. ***
*** Bug 148099 has been marked as a duplicate of this bug. ***
Should be reopened...! Please see the report for bug 148176...
No it shouldn't
i really could care less about the contents of the bug! KTORRENTS IS STILL CRASHING !!! RANDOMLLY !!! I COULD POST A FOREST WORTH OF EMAILS AND IT DONT/WONT MAKEA DIFFERENCE . ITS NOT WORKING RIGHT!! HELLO A CRASH IS A CRASH !! ILL PUT IT IN ENGLISH FOR YOU..... UNTILL THE UPGRADE TO FEISTY FAWN IT NEVER FREAKING CRASHED !! EVER!! SO JUST FIX THE FLIPPING THING ALLREADY SHEESH WHAT PART OF THAT IS TOO HARD FOR YOU GUYS TO UNDERSTAND !! I KNOW IM NOT THE ONLY ONE POSTING THAT KTORRENTS CRASH'S..... THANK YOU FOR ALL OF THE ATTENTION TO FIXING THIS PODS
It has been mentioned a few times that "the fix is in 2.1.4" ...If you have at least 2.1.4, this bug is FIXED. Thus the status of "RESOLVED" and the resolution as "FIXED"
Mister MY CAPSLOCK KEY IS STUCK, what version are you running ?
*** Bug 148461 has been marked as a duplicate of this bug. ***
*** Bug 148500 has been marked as a duplicate of this bug. ***
*** Bug 149511 has been marked as a duplicate of this bug. ***
*** Bug 149551 has been marked as a duplicate of this bug. ***
*** Bug 150152 has been marked as a duplicate of this bug. ***
*** Bug 150292 has been marked as a duplicate of this bug. ***
*** Bug 150356 has been marked as a duplicate of this bug. ***
KTorrent crashed and caused the signal 11 (SIGSEGV) This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1".
Created attachment 28446 [details] BackLog
I'm experiencing the same problem. Running fedora 9, KDE 4.1.2 and kTorrent 3.1.4 The backlog is attached in previous message.
First of all, this bug has long been fixed, second your problem has nothing to do with this, and third your problem has already been fixed. The fix will be part of 3.1.5.
<Tnx for the prompt reply. I'll wait for 3.1.5 and stick to Deluge in the mean time.
Created attachment 31010 [details] A Fatal Error Occurred The application KTorrent (ktorrent) crashed and caused the signal 11 (SIGSEGV).