ktorrent crash when quitting

[Beakon Beflo]

Ktorrent version : 3.1.2
KDE version : 4.1.2
Ubuntu version : Intrepid
Frequency : occur only once

Backtrace :
Application: KTorrent (ktorrent), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb5dcc6c0 (LWP 6237)]
[New Thread 0xb4346b90 (LWP 6238)]
[KCrash handler]
#6 0xb64dc19b in ?? () from /usr/lib/libQtXml.so.4
#7 0xb64dd4c1 in ?? () from /usr/lib/libQtXml.so.4
#8 0xb64dc150 in ?? () from /usr/lib/libQtXml.so.4
#9 0xb64dd4c1 in ?? () from /usr/lib/libQtXml.so.4
#10 0xb64dc150 in ?? () from /usr/lib/libQtXml.so.4
#11 0xb64dd4c1 in ?? () from /usr/lib/libQtXml.so.4
#12 0xb64dc150 in ?? () from /usr/lib/libQtXml.so.4
#13 0xb64dc2f9 in ?? () from /usr/lib/libQtXml.so.4
#14 0xb64d473a in QDomNode::~QDomNode () from /usr/lib/libQtXml.so.4
#15 0xb64d6b1d in QDomDocument::~QDomDocument () from /usr/lib/libQtXml.so.4
#16 0xb7b0dd17 in KXMLGUIClient::~KXMLGUIClient () from /usr/lib/libkdeui.so.5
#17 0x08074bcb in _start ()
#0 0xb7fb4430 in __kernel_vsyscall ()

[arno_b (arno.b)]

Can you reproduce the crash?
If yes, can you try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash and on http://live.gnome.org/GettingTraces/Details.
(install packages 'ktorrent-dbg' and 'gdb' and see here for backtrace https://wiki.ubuntu.com/Backtrace)

Marked as incomplete until we have a backtrace.

[Scott Lewin (sclewin)]

+1. It only happened once or twice for me as well, but Ktorrent crashed on me. If it helps I have provided my backtrace. I'm using Kubuntu 8.10, KDE 4.1.2, and Ktorrent 3.1.2. If I have not installed ktorrent-dbg I will now, I can't remember if I did or not.

[arno_b (arno.b)]

@scott: thank for the backtrace. But can you install package libqtcore4-dbgsym and try to make another backtrace please.

[arno_b (arno.b)]

The bug does not seem to come from ktorrent but libqtcore in ~KFilterDev at /usr/include/qt4/QtCore/qbytearray.h:364

[arno_b (arno.b)]

@scott: your problem has nothing to deal with the problem of Beakon (the problem of Beakon is an XML issue). Can you open a new bug report with your backtrace against ktorrent please.
Still waiting for a backtrace from Beakon.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!