Bug 242176 - Crash just after opeing Ktorrent
Summary: Crash just after opeing Ktorrent
Status: RESOLVED DUPLICATE of bug 221333
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-19 17:03 UTC by Tony Clifton
Modified: 2010-06-21 08:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.17 KB, text/plain)
2010-06-19 17:08 UTC, Tony Clifton
Details
New crash information added by DrKonqi (4.12 KB, text/plain)
2010-06-20 12:31 UTC, Tony Clifton
Details
New crash information added by DrKonqi (4.33 KB, text/plain)
2010-06-20 12:38 UTC, Tony Clifton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Clifton 2010-06-19 17:03:36 UTC
Application: ktorrent (4.0beta1)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.5-124.fc13.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
opened the application, the GUI was created, it crashed

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f74a3a20840 (LWP 5828))]

Thread 2 (Thread 0x7f7499f11710 (LWP 5830)):
#0  0x0000003e9deda033 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x000000325e2a7c1e in dht::RPCServerThread::run (this=0x1f99d80) at /usr/src/debug/ktorrent-4.0beta1/libbtcore/dht/rpcserver.cpp:107
#2  0x000000325a270995 in QThreadPrivate::start (arg=0x1f99d80) at thread/qthread_unix.cpp:248
#3  0x0000003e9ea07761 in start_thread (arg=0x7f7499f11710) at pthread_create.c:301
#4  0x0000003e9dee14dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f74a3a20840 (LWP 5828)):
[KCrash Handler]
#5  QMutex::lock (this=0x30) at thread/qmutex.cpp:150
#6  0x000000325e2b6abd in bt::PreallocationThread::isStopped (this=0x0) at /usr/src/debug/ktorrent-4.0beta1/libbtcore/diskio/preallocationthread.cpp:82
#7  0x000000325e2b6d9d in bt::PreallocationJob::finished (this=0x2259220) at /usr/src/debug/ktorrent-4.0beta1/libbtcore/diskio/preallocationjob.cpp:60
#8  0x000000325e243800 in bt::PreallocationJob::qt_metacall (this=0x2259220, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>)
    at /usr/src/debug/ktorrent-4.0beta1/x86_64-redhat-linux-gnu/libbtcore/moc_preallocationjob.cpp:74
#9  0x000000325a366d11 in QObject::event (this=0x2259220, e=0x7f748c001e00) at kernel/qobject.cpp:1248
#10 0x000000325bbaa9cc in QApplicationPrivate::notify_helper (this=0x1d804b0, receiver=0x2259220, e=0x7f748c001e00) at kernel/qapplication.cpp:4304
#11 0x000000325bbb098b in QApplication::notify (this=<value optimized out>, receiver=0x2259220, e=0x7f748c001e00) at kernel/qapplication.cpp:4187
#12 0x000000325ca06e86 in KApplication::notify (this=0x7fff6fb69800, receiver=0x2259220, event=0x7f748c001e00) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#13 0x000000325a357cdc in QCoreApplication::notifyInternal (this=0x7fff6fb69800, receiver=0x2259220, event=0x7f748c001e00) at kernel/qcoreapplication.cpp:704
#14 0x000000325a358a27 in sendEvent (receiver=0x0, event_type=0, data=0x1d4eaf0) at kernel/qcoreapplication.h:215
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1d4eaf0) at kernel/qcoreapplication.cpp:1345
#16 0x000000325a37dac3 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#17 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#18 0x0000003e9f63bd02 in g_main_dispatch (context=0x1d8ac40) at gmain.c:1960
#19 IA__g_main_context_dispatch (context=0x1d8ac40) at gmain.c:2513
#20 0x0000003e9f63fae8 in g_main_context_iterate (context=0x1d8ac40, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#21 0x0000003e9f63fc9c in IA__g_main_context_iteration (context=0x1d8ac40, may_block=1) at gmain.c:2654
#22 0x000000325a37d603 in QEventDispatcherGlib::processEvents (this=0x1d4e210, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x000000325bc49a8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x000000325a356722 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x000000325a3569ec in QEventLoop::exec (this=0x7fff6fb69770, flags=...) at kernel/qeventloop.cpp:201
#26 0x000000325a358cd9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#27 0x0000000000425dbb in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/ktorrent-4.0beta1/ktorrent/main.cpp:171

Possible duplicates by query: bug 221333.

Reported using DrKonqi
Comment 1 Tony Clifton 2010-06-19 17:08:25 UTC
Created attachment 48143 [details]
New crash information added by DrKonqi

the application wouldn't start
the machine has been re-booted, Ktorrent is the only application I'm running
Ktorrent appears to be non-functional
Comment 2 Joris Guisson 2010-06-20 00:08:09 UTC
Upgrade to 4.0.1, this has been fixed

*** This bug has been marked as a duplicate of bug 221333 ***
Comment 3 Tony Clifton 2010-06-20 12:31:51 UTC
Created attachment 48156 [details]
New crash information added by DrKonqi

this was originally marked as a dunplicate of another bug, which was marked FIXED, it's obviously not fixed or it wouldn't crash before opening the GUI
Comment 4 Tony Clifton 2010-06-20 12:38:30 UTC
Created attachment 48157 [details]
New crash information added by DrKonqi

I have run yum update ktorrent - there is no update, I rebooted the machine and opened Ktorrent - it crashed 
- in what way is crashing a product of an application having been fixed by KDE developers ?

It is still a bug, this behaviour is new to this version of KDE and Fedora, I was able to run Ktorrent quite happily with no problem with earlier versions of the OS and KDE
Comment 5 Joris Guisson 2010-06-21 08:52:43 UTC
If you don't upgrade your version of ktorrent, to a version which contains the fix, it will keep crashing.