Hi,

I've used Ktorrent for a couple of weeks without problems untill yesterday.
It started when 4 torrents that had completed downloading all of a sudden showed up as though they had been seeding for 49710 days and 6hrs.
See snapshot:


When I try to remove these torrents ktorrent crashes.

Later on it started crashing everytime a download finishes, or when i try to alter any of the settings.

I use:

Qt: 3.3.7
KDE: 3.5.8
KTorrent: 2.2.4

Any idea what can be the problem??

Got any backtraces of those crashes ?

I use a fully updated Gutsy.

How would I go about clearing settings and such?

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)
[Thread debugging using libthread_db enabled]
[New Thread -1235212608 (LWP 1057)]
[New Thread -1251349616 (LWP 1094)]
[New Thread -1242956912 (LWP 1093)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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  0xb7e4a310 in bt::PeerDownloader::getMaxChunkDownloads ()
   from /usr/lib/libktorrent-2.2.4.so
#7  0xb7e37158 in bt::Downloader::normalUpdate ()
   from /usr/lib/libktorrent-2.2.4.so
#8  0xb7e37208 in bt::Downloader::update () from /usr/lib/libktorrent-2.2.4.so
#9  0xb7e43277 in bt::TorrentControl::update ()
   from /usr/lib/libktorrent-2.2.4.so
#10 0x080775a1 in ?? ()
#11 0x0807b672 in ?? ()
#12 0xb6ead893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb6eae338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb723b9b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#15 0xb6ed55ba in QTimer::event () from /usr/lib/libqt-mt.so.3
#16 0xb6e44af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#17 0xb6e4691f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#18 0xb760bca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#19 0xb6dd7209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#20 0xb6e3753b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#21 0xb6debd49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb6e5f1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb6e5efde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb6e46699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x0808da52 in ?? ()
#26 0xb6649050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x0806a8e1 in ?? ()


This is unlikely to be a settings problem. First time I see a crash like this.

Would it be possible to compile a debug load ? That should give some more information on the backtrace.

Also, look in /var/crash for any apport crash reports for KTorrent? Those we can stick on the retracer in Launchpad to generate a wealth of info.

Nothing in /var/crash.

Not sure how I would compile the debug load.. If you can give me some pointers, I could try it out. Normally I only use packages from the repositories.

AM

First download the source package here: http://ktorrent.org/index.php?page=downloads

Extract that, and then just compile like it is mentioned on the faq page, but then use

Code: Select all

./configure --enable-debug=full


After make is done you do a

Code: Select all

sudo make install


to install ktorrent.

Remember to first aptitude remove ktorrent before you install the compiled version.

When running ./configure.. I get this:

Code: Select all

checking for X... configure: error: Can't find X libraries. Please check your installation and add the correct paths!


You are probably missing the package xlib-dev or something familiar.

I can't find a package by that name, and I'm not sure if I should install xorg-dev or x11-dev (or something entirely different). Sorry I can't help you out, I'll just wait for the new version to hit the repos.

AM

I think it is x11-dev then.

2.2.4 has been running without a crash since restarting after that last posting. I'm beginning to think it's more voodoo than a bug. I'm now afraid to upgrade to the new version as the problem may be reintroduced. I'll take the leap at the next crash.

AM