Bug 195483 - Kget crashed, when i restarted transfer
Summary: Kget crashed, when i restarted transfer
Status: RESOLVED DUPLICATE of bug 199056
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-06 19:12 UTC by Mieszko Ślusarczyk
Modified: 2009-07-05 23:05 UTC (History)
1 user (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 Mieszko Ślusarczyk 2009-06-06 19:12:08 UTC
Application that crashed: kget
Version of the application: 2.2.85
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-8-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Kget crashed, when i restarted transfer.

 -- Backtrace:
Application: KGet (kget), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f1130d12020 in TransferGroup::handler () from /usr/lib/libkgetcore.so.4
#6  0x00007f1130d0e830 in TransferTreeModel::timerEvent () from /usr/lib/libkgetcore.so.4
#7  0x00007f112f1f0b83 in QObject::event (this=0x788110, e=0x0) at kernel/qobject.cpp:1082
#8  0x00007f112fd673fc in QApplicationPrivate::notify_helper (this=0x6f1210, receiver=0x788110, e=0x7fff59358fc0) at kernel/qapplication.cpp:4057
#9  0x00007f112fd6e6ae in QApplication::notify (this=0x7fff59359300, receiver=0x788110, e=0x7fff59358fc0) at kernel/qapplication.cpp:4022
#10 0x00007f1131ab3526 in KApplication::notify (this=0x7fff59359300, receiver=0x788110, event=0x7fff59358fc0) at ../../kdeui/kernel/kapplication.cpp:307
#11 0x00007f112f1e13ec in QCoreApplication::notifyInternal (this=0x7fff59359300, receiver=0x788110, event=0x7fff59358fc0) at kernel/qcoreapplication.cpp:610
#12 0x00007f112f20cd22 in QTimerInfoList::activateTimers (this=0x6f3960) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#13 0x00007f112f20a7bd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#14 0x00007f112b2668be in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0x00007f112b269f98 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x00007f112b26a0c0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0x00007f112f20a706 in QEventDispatcherGlib::processEvents (this=0x6c8d10, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#18 0x00007f112fdfd1de in QGuiEventDispatcherGlib::processEvents (this=0x2c0000000000000, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#19 0x00007f112f1dfcc2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#20 0x00007f112f1e0094 in QEventLoop::exec (this=0x7fff59359260, flags=) at kernel/qeventloop.cpp:200
#21 0x00007f112f1e2189 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#22 0x000000000045c56c in _start ()
Comment 1 Dario Andres 2009-06-19 16:17:35 UTC
Probably related to bug 192775. Thanks
Comment 2 Dario Andres 2009-07-05 23:05:35 UTC
Bug 199056 has the same description and better backtrace. Merging.

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