Ubuntu
ktorrent package

[apport] ktorrent crashed with SIGSEGV

Bug #112509 reported by Søren Holm
14
Affects Status Importance Assigned to Milestone
ktorrent (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ktorrent

Crash when added a torrent. I think it happened in relation to just having pressed OK in the where-to-place-file dialogbox for another torrent.

So the sequence seems to be
1. add a torrent. Choose location and press ok
2. Quickly add another torrent.

I most certainly can not reproduce the crash, but it is a hint anyway.

ProblemType: Crash
Architecture: i386
Date: Sat May 5 03:37:17 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/ktorrent
Package: ktorrent 2.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: ktorrent -icon ktorrent -miniicon ktorrent -caption KTorrent
ProcCwd: /home/sgh
ProcEnviron:
 PATH=/home/sgh/bin:/home/sgh/arm-elf-tools/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: ktorrent
StacktraceTop:
 ?? () from /usr/lib/libdbus-1.so.3
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libdbus-1.so.3
Uname: Linux phoenix 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Søren Holm (sgh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dbus_message_add_size_counter_link (message=0x84d3c28, link=0xb4fcab34) at dbus-message.c:216
_dbus_message_add_size_counter (message=0x84d3c28, counter=0x812c6c0) at dbus-message.c:239
_dbus_transport_queue_messages (transport=0x85cdf60) at dbus-transport.c:941
do_reading (transport=0x85cdf60) at dbus-transport-socket.c:770

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Brian Murray (brian-murray)
Changed in ktorrent:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
tdn (spam-thomasdamgaard) wrote :
Download full text (4.6 KiB)

I think this is the same that happened to me:

Here is a trace:

(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 -1235999024 (LWP 7884)]
[New Thread -1252009072 (LWP 8177)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0xb7d9dbcb in dht::ParseRsp () from /usr/lib/libktorrent-2.1.so
#7 0xb7d9ddf2 in dht::MakeRPCMsg () from /usr/lib/libktorrent-2.1.so
#8 0xb7d92f51 in dht::RPCServer::readPacket ()
   from /usr/lib/libktorrent-2.1.so
#9 0xb7d93252 in dht::RPCServer::qt_invoke ()
   from /usr/lib/libktorrent-2.1.so
#10 0xb6dd788b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6dd8330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb756102c in KNetwork::KClientSocketBase::readyRead ()
   from ...

Read more...

Revision history for this message
tdn (spam-thomasdamgaard) wrote :

I would like to install the debug symbols package for ktorrent, so that I can produce a more meaningful trace.
When I try to do that, I get this:

~ $ sudo aptitude install ktorrent-dbgsym
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
  ktorrent-dbgsym
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 9701kB of archives. After unpacking 25,2MB will be used.
The following packages have unmet dependencies:
  ktorrent-dbgsym: Depends: ktorrent (= 2.1-0ubuntu2.2) but 2.1-0ubuntu2.1 is installed.
Resolving dependencies...
The following actions will resolve these dependencies:

Install the following packages:
ktorrent-dbgsym [2.1-0ubuntu2.1 (<NULL>, <NULL>)]

Score is -10040

Accept this solution? [Y/n/q/?]

I use these sources:

~ $ cat /etc/apt/sources.list.d/debug-packages.list
deb http://people.ubuntu.com/~pitti/ddebs feisty main universe
deb http://people.ubuntu.com/~pitti/ddebs feisty-updates main universe
deb http://people.ubuntu.com/~pitti/ddebs feisty-proposed main universe
deb http://people.ubuntu.com/~pitti/ddebs feisty-security main universe

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Kubuntu 7.04 has ended its supported life. Seeing as there have been no similar crashes in a long time, this bug is most likely fixed in a more recent version of Kubuntu. If you still are experiencing this bug in a more recent version of Kubuntu, please feel free to re-open this bug.

Changed in ktorrent:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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