[apport] ktorrent crashed with SIGSEGV in free()

Bug #96529 reported by Erik
4
Affects Status Importance Assigned to Milestone
ktorrent (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ktorrent

crashed on startup

ProblemType: Crash
Architecture: i386
Date: Mon Mar 26 11:50:46 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/ktorrent
Package: ktorrent 2.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/ktorrent /tmp/Magik\ 6\ -\ Live\ in\ Amsterdam.torrent
ProcCwd: /home/erik
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: ktorrent
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 avahi_free () from /usr/lib/libavahi-common.so.3
 ?? () from /usr/lib/libavahi-client.so.3
 ?? ()
 ?? () from /usr/lib/libdbus-1.so.3
Uname: Linux compy-k7 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Erik (eramseth) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
avahi_free (p=0x0) at malloc.c:140
client_set_state (client=0x8509028, state=100) at client.c:85
filter_func (bus=0x8571dd0, message=0x85399e8, userdata=0x8509028) at client.c:300
dbus_connection_dispatch (connection=0x8571dd0) at dbus-connection.c:4267

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in ktorrent:
importance: Undecided → Medium
Revision history for this message
Jussi Schultink (jussi01) wrote :

Happened to me also. atatched is the generated backtrace.

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

Jussi: your bug is a dupe of bug 109184

The original bug can now be confirmed with the retrace.

Changed in ktorrent:
status: Unconfirmed → Confirmed
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
Revision history for this message
Mneo (msneoph) wrote :
Download full text (5.1 KiB)

Ktorrent running on Ubuntu 8.04 LTS crashes after about 1 or 2 minutes running.

Here is the dump =

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb588d6d0 (LWP 6385)]
[New Thread 0xb41e7b90 (LWP 6402)]
[New Thread 0xb39e6b90 (LWP 6401)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symb...

Read more...

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

Other bug subscribers

Remote bug watches

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