Bug 220838 - chrash on every start
Summary: chrash on every start
Status: RESOLVED WORKSFORME
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-12-31 19:37 UTC by Robert Sela
Modified: 2018-10-27 04:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Sela 2009-12-31 19:37:01 UTC
Application that crashed: ktorrent
Version of the application: 3.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.8-1mdv i686
Distribution: "Mandriva Linux 2010.0"

What I was doing when the application crashed:
It is imposible to start aplication.

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

Thread 2 (Thread 0xb3479b70 (LWP 28697)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6836d12 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0
#2  0xb68b5f3c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb68ab402 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb68b4e83 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb6832885 in start_thread () from /lib/i686/libpthread.so.0
#6  0xb5cc457e in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb4c5c6d0 (LWP 28684)):
[KCrash Handler]
#6  0xb68af9f7 in QMutex::lock () from /usr/lib/libQtCore.so.4
#7  0xb768e8c0 in ?? () from /usr/lib/libbtcore.so.12
#8  0xb767f02d in ?? () from /usr/lib/libbtcore.so.12
#9  0xb767eaa4 in ?? () from /usr/lib/libbtcore.so.12
#10 0xb69c2144 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb69c2e65 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb69fda15 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#13 0xb69c7a76 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#14 0xb69bbdfb in QObject::event () from /usr/lib/libQtCore.so.4
#15 0xb5f9468c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb5f9c0ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb700fa21 in KApplication::notify () from /usr/lib/libkdeui.so.5
#18 0xb69abc0e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb69da2c1 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb69d7c05 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb52beb92 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb52c2468 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb52c258e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb69d78f1 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb60364ba in ?? () from /usr/lib/libQtGui.so.4
#26 0xb69aa26d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb69aa6b9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb64930e1 in QDialog::exec () from /usr/lib/libQtGui.so.4
#29 0x08068f22 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-31 22:47:59 UTC
Thanks for the report!
- If you can reproduce the crash at will (or you experience this regularly), can you install the "ktorrent-debug" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports ) Thanks
Comment 2 Robert Sela 2010-01-01 04:06:00 UTC
Sorry, but  don't   have it in repository!
I'll try nevertheles to instal it from source
Comment 3 Dario Andres 2010-01-01 04:12:37 UTC
You need to enable the custom repository named "debug_main". Thanks
Comment 4 Adrián Chaves (Gallaecio) 2012-09-18 06:03:23 UTC
Robert, could you reproduce the issue? Else, can this report be closed?
Comment 5 Andrew Crouthamel 2018-09-23 02:37:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 04:16:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!