I get a SIGSEGV signal 11 every time I quit from Ktorrent - i had this problem 2 or 3 versions ago and it went. But now every time I quit same thing. I'm running it on Ubuntu 7.04.

This is the backtrace from the crash handler -

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 -1235147056 (LWP 15703)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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  0x0063002f in ?? ()
#7  0xb7dd96fc in kt::PluginManager::unloadAll ()
   from /usr/lib/libktorrent-2.2.1.so
#8  0x08076ea3 in ?? ()
#9  0x08070112 in ?? ()
#10 0xb77cde30 in KMainWindow::shuttingDown () from /usr/lib/libkdeui.so.4
#11 0xb792d031 in KMainWindow::qt_invoke () from /usr/lib/libkdeui.so.4
#12 0xb7d21943 in KParts::MainWindow::qt_invoke ()
   from /usr/lib/libkparts.so.2
#13 0x080c20d3 in ?? ()
#14 0x0815b1f8 in ?? ()
#15 0x00000048 in ?? ()
#16 0xbffb5bfc in ?? ()
#17 0x00000048 in ?? ()
#18 0xbffb5bfc in ?? ()
#19 0x0815b1f8 in ?? ()
#20 0xbffb5b68 in ?? ()
#21 0x08071fb0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

This has already been fixed, the fix will be part of the 2.2.2 version.

ok thanks

Just came in to post my error log, and saw this. Thanks, George.

George wrote:This has already been fixed, the fix will be part of the 2.2.2 version.

How long will it take to the 2.2.2 version? I really need this fix!

This bug should be fixed in the latest Ubuntu Backports version of 2.2.1-0ubuntu3

At least it would be fixed if I grabbed the right SVN.... Verify that it's 2.2.1-0ubuntu3 that's installed (apt-cache policy ktorrent)

I'm not using Ubuntu.

Ive read that some Ubuntu packages have been fixed so far but I don't benefit from that. I'm using ArchLinux. Thats why I'm wanting the new version so bad.

You are right, it's time for a bugfix release. I'm aiming for the weekend.