Ubuntu
ktorrent package

KTorrent crashed without warning (fixed upstream)

Bug #109184 reported by Anders
142
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KTorrent
Fix Released
High
ktorrent (Ubuntu)
Fix Released
High
Unassigned
Feisty
Fix Released
Undecided
John Dong

Bug Description

Binary package hint: ktorrent

I've never had any problems with KTorrent crashing earlier, but during the night sometime KTorrent crashed and left a message with the KDE Crash handler with Signal 11 (SIGSEGV) and this stacktrace:

(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 -1235282224 (LWP 22108)]
[New Thread -1242596464 (LWP 22169)]
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7e4cb9b in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e4cdc2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e41f21 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e42222 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e8688b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e87330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb761004c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb7610086 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#14 0xb7622143 in KNetwork::KClientSocketBase::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb76221e6 in KNetwork::KDatagramSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0xb6e8688b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6e871a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb7213877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#19 0xb6ea944a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#20 0xb6e1da60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6e1f88f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb75e1ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6db01e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6e0fe59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6dc4d07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6e38136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6e1f587 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3
#28 0xb703b3e9 in QDialog::exec () from /usr/lib/libqt-mt.so.3
#29 0xb78dfd79 in KMessageBox::createKMessageBox ()
   from /usr/lib/libkdeui.so.4
#30 0xb78e04c7 in KMessageBox::createKMessageBox ()
   from /usr/lib/libkdeui.so.4
#31 0xb78e2662 in KMessageBox::errorListWId () from /usr/lib/libkdeui.so.4
#32 0xb78e2823 in KMessageBox::error () from /usr/lib/libkdeui.so.4
#33 0xb4e7da41 in kt::RssLinkDownloader::processLink ()
   from /usr/lib/kde3/ktrssfeedplugin.so
#34 0xb4e880ec in kt::RssLinkDownloader::qt_invoke ()
   from /usr/lib/kde3/ktrssfeedplugin.so
#35 0xb6e8688b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#36 0xb7aad58e in KIO::Job::result () from /usr/lib/libkio.so.4
#37 0xb7aeff6d in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#38 0xb7af03ce in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#39 0xb7af0add in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.4
#40 0xb7ac36a3 in KIO::SimpleJob::slotError () from /usr/lib/libkio.so.4
#41 0xb7aefa43 in KIO::SimpleJob::qt_invoke () from /usr/lib/libkio.so.4
#42 0xb7aefb63 in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4
#43 0xb7aefe26 in KIO::StoredTransferJob::qt_invoke ()
   from /usr/lib/libkio.so.4
#44 0xb6e8688b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#45 0xb7aacde0 in KIO::SlaveInterface::error () from /usr/lib/libkio.so.4
#46 0xb7b0d4cb in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#47 0xb7b15f0a in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#48 0xb7abce8c in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#49 0xb7b06410 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#50 0xb6e8688b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#51 0xb6e871a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#52 0xb7213877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#53 0xb6ea944a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#54 0xb6e1da60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#55 0xb6e1f88f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#56 0xb75e1ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#57 0xb6db01e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#58 0xb6e0fe59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#59 0xb6dc4d07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#60 0xb6e38136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#61 0xb6e37f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#62 0xb6e1f609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#63 0x080653d6 in ?? ()
#64 0xb6637ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#65 0x08064ec1 in ?? ()

I'm using latest Feisty with all updates installed

Tags: ktorrent
Revision history for this message
Heikki Mäntysaari (heikki-mantysaari) wrote :

I can confirm this bug. (KTorrent 2.1)

Revision history for this message
Anders (andersja+launchpad-net) wrote :
Download full text (4.6 KiB)

It happened again:
(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 -1235306800 (LWP 21085)]
[New Thread -1243808880 (LWP 21127)]
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7e46b9b in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e46dc2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e3bf21 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e3c222 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e8088b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e81330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb760a04c in KNetwork::KClientSocketBase::readyRe...

Read more...

Revision history for this message
rvadmin (rvadmin) wrote :

I can confirm this. I used Kubuntu Edgy and all was OK!
When I downloaded and installed Kubuntu Feisty DVD, ktorrent randomly crashes (with kcrash error and without) (and not only ktorrent, for example Kftpgrabber, akregator,azureus, many programs that use internet connection)!

Sorry for my English!

Revision history for this message
Anders (andersja+launchpad-net) wrote :
Download full text (4.5 KiB)

And again:

(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 -1235474736 (LWP 10073)]
[New Thread -1242793072 (LWP 10090)]
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7e1db9b in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e1ddc2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e12f21 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e13222 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e5788b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e58330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb75e104c in KNetwork::KClientSocketBase::readyRead ()
 ...

Read more...

Revision history for this message
Anders (andersja+launchpad-net) wrote :

Setting to confirmed as Heikki and rvadmin confirm the same experience.

Changed in ktorrent:
status: Unconfirmed → Confirmed
Revision history for this message
berg (berg-foss) wrote :

I can confirm this bug and I put in kde bugzilla this post
http://bugs.kde.org/show_bug.cgi?id=144603 what was marked as duplicate of http://bugs.kde.org/show_bug.cgi?id=144416.
Then there is a bug in this version. The manteiner said to upgrade to version 2.1.4 that will resolve this bug

Revision history for this message
balrok (balrok) wrote :

i use version 2.1 and have absolutely the same error-output
i also noticed, that this bug only happens if i up/download something.. if i stop all torrents i can leave the program open for hours without the bug..

Revision history for this message
John Dong (jdong) wrote :

Well, just lovely. We can't exactly import 2.1.4 into Feisty because they mixed bugfixes with translation updates and other changes... but I will see if I can isolate some patches just for crashfixing and prepare a SRU.

Revision history for this message
navegante (navegante) wrote :

I can confirm this bug, kopete confirm the same experience.

Revision history for this message
rvadmin (rvadmin) wrote :

and again, [apport] ktorrent crashed with SIGSEGV in dbus_connection_dispatch()
version 2.1.4!!! Not all bugs are fixed! May be some libraries in feisty are bad?

Bug Watch Updater (bug-watch-updater)
Changed in ktorrent:
status: Unknown → Fix Released
Revision history for this message
piccobello (piccobello) wrote :

I have exactly the same problem (with 2.1 dapper), backtrace looks the same.

I found this bug duplicated a few times on bugs.kde.org, they all refer to version 2.1.4 as the solution.

When I start it from the shell, I always see this warning:
Qt: Warning: QGArray::at: Absolute index 0 out of range
before it crashes. No idea if that is related.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

Temporary fix (while we wait for 2.1.4 to tricle into Ubuntu): The bug seems to be related to DHT, which can be switched off in the preferences. I switched it off and it didn't crash again (until now)

Revision history for this message
piccobello (piccobello) wrote :
Revision history for this message
Andrew Ash (ash211) wrote :

Just another "me too" here.

Revision history for this message
Flink Del Dinky (flinkdeldinky) wrote :

Just want to say that I can confirm this bug on Feisty with ktorrent 2.1 However, Azuerus, kopete, etc. all seem to work fine unlike the reports of others. But I don't like to run Azuerus because java seem to steal a lot of cpu for a few seconds every few minutes. This causes programs like Kaffeine to stutter when playing a divx.

I leave this box on 24/7 so this bad ktorrent build is a real downer. If the kubuntu team can't offer a patch then maybe they should downgrade the version in the Feisty repositories. Regardless the current ktorrent shouldn't be in there (assuming this bug is across the board, which it may not be).

By the way I'm runnning the 64 bit version of kubuntu on an AMD64.

Revision history for this message
Sander Jonkers (jonkers) wrote : Re: [Bug 109184] Re: KTorrent crashed without warning (fixed upstream)

Flink Del Dinky wrote:
> Just want to say that I can confirm this bug on Feisty with ktorrent 2.1
>
 <snip>
> I leave this box on 24/7 so this bad ktorrent build is a real downer.
>

Solved (meaning: personal workaround) by installing ktorrent 2.1.4 from
http://ktorrent.org/index.php?page=downloads :
http://buntudot.org/people/~jdong/ktorrent/2.1.4/feisty/ktorrent_2.1.4~0jdong1~7.04prevu1_i386.deb

Revision history for this message
. (asfg-deactivatedaccount) wrote :

The problem is with the DHT in KTorrent. Disabling it fixes the crashes, but you get slower downloads (=fewer peers).
Also, a 64-bit deb of 2.1.4 would be lovely (I'm staring at you, jdong;).

-Martin

Revision history for this message
John Dong (jdong) wrote :

I have already submitted a SRU request to update Ubuntu's packaging with 10 or so crashfixing and related patches, and it is pending review.

In addition, KTorrent 2.1.4 is entering Gutsy soon....

http://ktorrent.org/forum/viewtopic.php?t=1539 has amd64 packages contributed from someone else. I took a quick glance at it and it looks good to me, but again, I didn't make them so I can't even support them.

Please hang tight, the bug is being worked on.

Revision history for this message
datakid (datakid) wrote :

Cheers all, good to hear - it's starting to drive me nuts with 2+
crashes a day, and it's all started so recently :)

L.

On 4/30/07, John Dong <email address hidden> wrote:

Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

Jo, I´m confirming this bug too, it is rellay annoying cause it worked very good in dapper.
I deactivated DHT at the moment. But I hope it will be fixed soon in Feisty.

Revision history for this message
Motasim Sakallah (m-sakallah-deactivatedaccount) wrote :

Just adding my confirmation of the bug. Didn't start happening till I upgraded from Edgy to Feisty.

Revision history for this message
Matthew W. A. Schibler (m-schibler+ubuntu-bugs) wrote :

i'm having the same problem here, on a new install of feisty (desktop i386, running the standard gnome packages). I can post a gdb backtrace, but it's basically the same thing others have posted.

Revision history for this message
digimars (kenneth-l-armstrong) wrote :
Download full text (4.6 KiB)

Me too, Kubuntu Fiesy Fawn, i386 install. KTorrent just randomly crashes. I have made NO modifications to my install whatsoever.

Here's my bug backtrace:

(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 -1235106096 (LWP 7128)]
[New Thread -1250366576 (LWP 7142)]
(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 0xb7e77b9b in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e77dc2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e6cf21 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e6d222 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6eb188b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6eb2330 in QObject::activate_signal () fro...

Read more...

Revision history for this message
Andrew Ash (ash211) wrote :

Thanks all for continuing to provide backtraces, but they are no longer necessary for this bug report. Trust me, the developers are well aware of this issue!

If you would like to follow the process of getting the fixes SRU'd into Feisty, please subscribe to bug 110881. Please no comments on that report unless you are very knowledgeable about packaging, patching, working with code, and such. Any extra comments now only clog up these bug reports and slow things down. In the hopes of expediting this process, please be content just sitting back and watching unless you have something brand new to contribute to the report.

Revision history for this message
DavidWhyte (david-whyte) wrote :

I too get this running KTorrent under Ubuntu (Gnome).

Running from the command prompt I get...
djwhyte@myth:/myth/temp$ ktorrent
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
Qt: Warning: QObject::disconnect: Unexpected null parameter
djwhyte@myth:/myth/temp$ Qt: Warning: QGArray::at: Absolute index 0 out of range
KCrash: Application 'ktorrent' crashing...
KCrash cannot reach kdeinit, launching directly.

djwhyte@myth:/myth/temp$
djwhyte@myth:/myth/temp$

I need to run with DHT and so to help my downloads continue through the night, I run ktorrent in a script, which automagically restarts it when it dissappears. It is attached for other people assistance. Just run the script 'restartKTorrent' instead of 'ktorrent'.

Revision history for this message
datakid (datakid) wrote :

I installed the deb mentioned in the Sander J post above (direct link: https://bugs.launchpad.net/ubuntu/+source/ktorrent/+bug/109184/comments/16 )

I have had no problems since I installed this, about five days ago.

Revision history for this message
John Dong (jdong) wrote :

Going to mark this In Progress: SRU is being reviewed

I have also approved and uploaded backports for Dapper, Edgy, and Feisty of 2.1.4, so if you have the -backports repository enabled, you will get this new version.

Changed in ktorrent:
status: Confirmed → In Progress
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

This is fixed in Gutsy, opening a task for Feisty

Changed in ktorrent:
importance: Undecided → High
status: In Progress → Fix Released
assignee: nobody → jdong
status: Unconfirmed → In Progress
Revision history for this message
FuLcRuM (lennert-raes) wrote :
Download full text (4.4 KiB)

Same problem here!

(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 -1235310896 (LWP 11869)]
[New Thread -1256117360 (LWP 11888)]
[New Thread -1246921840 (LWP 11870)]
(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 0xb7e45bcb in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e45df2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e3af51 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e3b252 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e7f88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e80330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb760904c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb7609086 in KNetwork::KClientSocketBase::slotReadActivity ()
 ...

Read more...

Revision history for this message
Andy Brook (javahollic) wrote :

Yea got this with feisty i386. Until the fix filters through to feisty I use the following script configured in my 'session' to auto start ktorrent, then call itself (thankfully ktorrent is bright enough to figure out its already running!):

#!/bin/bash
/usr/bin/ktorrent &
sleep 60
/usr/local/bin/kto &

In the last 12hours it crashed 8times (but restarted). a KISS solution :)

Revision history for this message
Michael Gefen (gefenm11) wrote :

i confirm the crash:
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235253552 (LWP 29499)]
[New Thread -1250002032 (LWP 29505)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6 0xb7e53bcb in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e53df2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e48f51 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e49252 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e8d88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e8e330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb761704c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb7617086 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#14 0xb7629143 in KNetwork::KClientSocketBase::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb76291e6 in KNetwork::KDatagramSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0xb6e8d88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6e8e1a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb721a877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#19 0xb6eb044a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#20 0xb6e24a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6e2688f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb75e8ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6db71e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6e16e59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6dcbd07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6e3f136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6e3ef46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb6e26609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x080653d6 in ?? ()
#30 0xb663eebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x08064ec1 in ?? ()

Revision history for this message
John Dong (jdong) wrote :

Attention Bug Sufferers:

(1) The proposed update, bug 110881, has already been approved for uploading, and I am awaiting a generous sponsor to upload it into the feisty-proposed repository. This will resolve this crash along with several other crash, CPU usage, and performance related issues with KTorrent.

(2) All the -backports repositories now have 2.1.4, which is another option for the impatient. Enable Backports, then do an update of ktorrent, and this crash should be history.

There is no further need to confirm this bug with "me too"s or backtraces -- it is well known and being fixed.

Thanks for the patience, and sorry for the inconvenience.

Revision history for this message
John Dong (jdong) wrote :

A fix is committed to feisty-proposed. More info is at https://bugs.launchpad.net/ubuntu/+source/ktorrent/+bug/110881 -- if you suffer from this bug, enable feisty-proposed and help test the fix.

thanks for the patience, and hopefully this puts the bug to rest finally!

Changed in ktorrent:
status: In Progress → Fix Committed
Revision history for this message
David Stahl (othernerd) wrote :

I have enabled feisty-proposed and I have version 2.1-0ubuntu2.2 (feisty proposed) installed and I'm still seeing the crash. Anything I might have forgotten to do?

Revision history for this message
Andrew Ash (ash211) wrote :

Restart KTorrent?

Revision history for this message
David Stahl (othernerd) wrote :

Nah, done that. Rebooted the machine a few times as well in between crashes. Right now I'm running without DHT to see if that might be the cause for me.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

I can confirm this is now working for me - with DHT enabled. Have been seeding > 20 gigs of the Ubuntu Feisty DVD image. Yay! :-)

Revision history for this message
John Dong (jdong) wrote :

Glad to hear that -- it works great for me too. David, is it the same crash
log as before?

On 6/28/07, Anders <email address hidden> wrote:
>
> I can confirm this is now working for me - with DHT enabled. Have been
> seeding > 20 gigs of the Ubuntu Feisty DVD image. Yay! :-)
>
> --
> KTorrent crashed without warning (fixed upstream)
> https://bugs.launchpad.net/bugs/109184
> You received this bug notification because you are the registrant for
> KTorrent.
>

Revision history for this message
David Stahl (othernerd) wrote :

Yeah, I think so. I didn't copy it after the last crash, but I'll try again and see if I can make sure.

I've been running without DHT for a while and no crashes so let me turn it back on and see what happens.

Revision history for this message
John Dong (jdong) wrote :

Thanks for keeping me up to date on this, David.

Revision history for this message
David Stahl (othernerd) wrote :

No problem.

And yeah, same trace. Here's the last bit:

[KCrash handler]
#6 0xb7e3e81b in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7e3ea42 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7e33b01 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7e33e02 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6e7888b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6e79330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb760204c in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#13 0xb7602086 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#14 0xb7614143 in KNetwork::KClientSocketBase::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb76141e6 in KNetwork::KDatagramSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#16 0xb6e7888b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6e791a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb7205877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#19 0xb6e9b44a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#20 0xb6e0fa60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6e1188f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb75d3ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6da21e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6e01e59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6db6d07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6e2a136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6e29f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb6e11609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x080653d6 in ?? ()
#30 0xb6629ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x08064ec1 in ?? ()

Revision history for this message
David Stahl (othernerd) wrote :

I actually experienced the crash when I had Ktorrent open but all torrents stopped. Can this be the same issue? I didn't copy the stack trace (oops) but I'll try get it next time.

Revision history for this message
John Dong (jdong) wrote :

Yeah, it coudl very well be the same crash, as long as DHT was enabled it doesn't matter if any torrents are running.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to -updates, see bug 110881.

Changed in ktorrent:
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in ktorrent:
importance: Unknown → High
Revision history for this message
Sander Jonkers (jonkers) wrote :

Question: why is Bug Watch Updater changing the importance of a *2007* bug from Unknown to High?

Revision history for this message
datakid (datakid) wrote :

I've no idea - I didn't do anything to provoke it...

On Sun, Feb 27, 2011 at 23:28, Sander Jonkers <email address hidden> wrote:
> Question: why is Bug Watch Updater changing the importance of a *2007*
> bug from Unknown to High?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (110171).
> https://bugs.launchpad.net/bugs/109184
>
> Title:
>  KTorrent crashed without warning (fixed upstream)
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ktorrent/+bug/109184/+subscribe
>

--
Crunchiness is the gustatory sensation of muffled grinding of a
foodstuff. Crunchiness differs from crispiness in that a crispy item
is quickly atomized, while a crunchy one offers sustained, granular
resistance to jaw action. While crispiness is difficult to maintain,
crunchiness is difficult to overcome.
from The Best of Wikipedia http://bestofwikipedia.tumblr.com/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.