Bug 222006

Summary: KTorrent crashed while adding a load of torrents
Product: [Applications] ktorrent Reporter: Jan Girke <jangirke>
Component: generalAssignee: Joris Guisson <joris.guisson>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jan Girke 2010-01-10 02:53:47 UTC
Application that crashed: ktorrent
Version of the application: 3.2.4
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was adding torrents while it happened, but it happens a lot on different computers
 intel and amd
 generic kernel .14 to .17
I think the bug is somewhere in the packages installed with Ktorrent,
it happens with the live cd and a fresh installation and
it doesnt happen that often anymore on my laptop
it happens while up and downloading and while adding torrents

 -- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7759700 (LWP 2087))]

Thread 3 (Thread 0xb4f0eb70 (LWP 2199)):
#0  0x00cda422 in __kernel_vsyscall ()
#1  0x03b1c396 in gettimeofday () from /lib/tls/i686/cmov/libc.so.6
#2  0x0013dfd6 in bt::Now () at ../../libbtcore/util/functions.cpp:171
#3  0x00151334 in net::DownloadThread::update (this=0x9027040) at ../../libbtcore/net/downloadthread.cpp:65
#4  0x00151d38 in net::NetworkThread::run (this=0x9027040) at ../../libbtcore/net/networkthread.cpp:48
#5  0x00f71e32 in QThreadPrivate::start (arg=0x9027040) at thread/qthread_unix.cpp:188
#6  0x011c980e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0x03b607ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb3f0cb70 (LWP 2200)):
#0  0x00cda422 in __kernel_vsyscall ()
#1  0x011cde15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x03b6d78d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x00f72e67 in QWaitConditionPrivate::wait (this=0x9027328, mutex=0x902732c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x9027328, mutex=0x902732c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x00150a6d in net::UploadThread::update (this=0x90272f0) at ../../libbtcore/net/uploadthread.cpp:73
#6  0x00151d38 in net::NetworkThread::run (this=0x90272f0) at ../../libbtcore/net/networkthread.cpp:48
#7  0x00f71e32 in QThreadPrivate::start (arg=0x90272f0) at thread/qthread_unix.cpp:188
#8  0x011c980e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#9  0x03b607ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7759700 (LWP 2087)):
[KCrash Handler]
#6  KIO::Slave::deref (this=0x961db40) at ../../kio/kio/slave.cpp:242
#7  0x00436af6 in KIO::Slave::gotInput (this=0x961db40) at ../../kio/kio/slave.cpp:335
#8  0x00438ee3 in KIO::Slave::qt_metacall (this=0x961db40, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfeef04c) at ./slave.moc:76
#9  0x01078263 in QMetaObject::activate (sender=0x9620098, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0x01078ec2 in QMetaObject::activate (sender=0x9620098, m=0x5298a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0x00340f97 in KIO::Connection::readyRead (this=0x9620098) at ./connection.moc:86
#12 0x00342d5e in KIO::ConnectionPrivate::dequeue (this=0x9627088) at ../../kio/kio/connection.cpp:82
#13 0x00342e8e in KIO::Connection::qt_metacall (this=0x9620098, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x96b9f68) at ./connection.moc:73
#14 0x01070f0b in QMetaCallEvent::placeMetaCall (this=0x953ab20, object=0x9620098) at kernel/qobject.cpp:477
#15 0x010725fe in QObject::event (this=0x9620098, e=0x953ab20) at kernel/qobject.cpp:1111
#16 0x05b10f54 in QApplicationPrivate::notify_helper (this=0x9050bd0, receiver=0x9620098, e=0x953ab20) at kernel/qapplication.cpp:4056
#17 0x05b1867c in QApplication::notify (this=0xbfeef8d4, receiver=0x9620098, e=0x953ab20) at kernel/qapplication.cpp:3603
#18 0x00a42bfa in KApplication::notify (this=0xbfeef8d4, receiver=0x9620098, event=0x953ab20) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x010626cb in QCoreApplication::notifyInternal (this=0xbfeef8d4, receiver=0x9620098, event=0x953ab20) at kernel/qcoreapplication.cpp:610
#20 0x010632b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9024d10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9024d10) at kernel/qcoreapplication.cpp:1247
#22 0x0106347d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#23 0x0108d3ff in QCoreApplication::sendPostedEvents (s=0x904a110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=0x904a110) at kernel/qeventdispatcher_glib.cpp:210
#25 0x06e93e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x06e97730 in ?? () from /lib/libglib-2.0.so.0
#27 0x06e97863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x0108d02c in QEventDispatcherGlib::processEvents (this=0x9024ee8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0x05bb1be5 in QGuiEventDispatcherGlib::processEvents (this=0x9024ee8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x01060c79 in QEventLoop::processEvents (this=0xbfeef844, flags=) at kernel/qeventloop.cpp:149
#31 0x010610ca in QEventLoop::exec (this=0xbfeef844, flags=...) at kernel/qeventloop.cpp:201
#32 0x0106353f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x05b10dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x08065b98 in main (argc=5, argv=0xbfeefc94) at ../../ktorrent/main.cpp:171

This bug may be a duplicate of or related to bug 207017

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-10 15:25:42 UTC
This is indeed related to bug 207017 / bug 191589. Thanks

*** This bug has been marked as a duplicate of bug 207017 ***