Bug 284515 - KGet crashed on completion of download
Summary: KGet crashed on completion of download
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-10-20 05:26 UTC by James Cain
Modified: 2018-10-27 03:58 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 James Cain 2011-10-20 05:26:12 UTC
Application: kget (2.7.1)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed: Switching to Dolphin (alt-tab) to view downloaded file. Although the emtire file was downloaded, it appears as a 0 kb empty file in Dolphin. So the crash must have happened during file transfer or in the process of marking the download complete(?)

-- Backtrace:
Application: KGet (kget), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4c55720 (LWP 9873))]

Thread 3 (Thread 0xb3cb9b70 (LWP 9875)):
#0  0x0065f34a in __pthread_mutex_lock (mutex=0xb33004ec) at pthread_mutex_lock.c:51
#1  0x08645802 in g_main_context_release () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x0864704f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x08647524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x04963577 in QEventDispatcherGlib::processEvents (this=0xb3300468, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x04935289 in QEventLoop::processEvents (this=0xb3cb9280, flags=...) at kernel/qeventloop.cpp:149
#6  0x04935522 in QEventLoop::exec (this=0xb3cb9280, flags=...) at kernel/qeventloop.cpp:201
#7  0x0483f2a0 in QThread::exec (this=0x960b868) at thread/qthread.cpp:492
#8  0x04916fdb in QInotifyFileSystemWatcherEngine::run (this=0x960b868) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x04841da2 in QThreadPrivate::start (arg=0x960b868) at thread/qthread_unix.cpp:320
#10 0x0065ce99 in start_thread (arg=0xb3cb9b70) at pthread_create.c:304
#11 0x021f473e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb24beb70 (LWP 9880)):
#0  0x009aa416 in __kernel_vsyscall ()
#1  0x021e5f76 in __poll (fds=0x9608bf8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0865784b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x086471af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x08647524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x04963577 in QEventDispatcherGlib::processEvents (this=0x95cb820, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x04935289 in QEventLoop::processEvents (this=0xb24be280, flags=...) at kernel/qeventloop.cpp:149
#7  0x04935522 in QEventLoop::exec (this=0xb24be280, flags=...) at kernel/qeventloop.cpp:201
#8  0x0483f2a0 in QThread::exec (this=0x9671700) at thread/qthread.cpp:492
#9  0x04916fdb in QInotifyFileSystemWatcherEngine::run (this=0x9671700) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x04841da2 in QThreadPrivate::start (arg=0x9671700) at thread/qthread_unix.cpp:320
#11 0x0065ce99 in start_thread (arg=0xb24beb70) at pthread_create.c:304
#12 0x021f473e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb4c55720 (LWP 9873)):
[KCrash Handler]
#7  QMetaObject::activate (sender=0x98e6af8, m=0x4175f8, local_signal_index=1, argv=0xbfeea234) at kernel/qobject.cpp:3235
#8  0x00379ab9 in TransferHandler::transferChangedEvent(TransferHandler*, int) () from /usr/lib/libkgetcore.so.4
#9  0x00396d43 in TransferTreeModel::timerEvent(QTimerEvent*) () from /usr/lib/libkgetcore.so.4
#10 0x0494b214 in QObject::event (this=0x932ad18, e=0xbfeea7bc) at kernel/qobject.cpp:1190
#11 0x01303d24 in QApplicationPrivate::notify_helper (this=0x926a4c0, receiver=0x932ad18, e=0xbfeea7bc) at kernel/qapplication.cpp:4462
#12 0x013088ce in QApplication::notify (this=0xbfeeaaf8, receiver=0x932ad18, e=0xbfeea7bc) at kernel/qapplication.cpp:3862
#13 0x00d8bc9a in KApplication::notify (this=0xbfeeaaf8, receiver=0x932ad18, event=0xbfeea7bc) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x049360bb in QCoreApplication::notifyInternal (this=0xbfeeaaf8, receiver=0x932ad18, event=0xbfeea7bc) at kernel/qcoreapplication.cpp:731
#15 0x049661e4 in sendEvent (this=0x926a8a4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x926a8a4) at kernel/qeventdispatcher_unix.cpp:604
#17 0x04962df4 in timerSourceDispatch (source=0x926a870) at kernel/qeventdispatcher_glib.cpp:184
#18 0x08646aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#19 0x08647270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#20 0x08647524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0x0496353c in QEventDispatcherGlib::processEvents (this=0x9200610, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#22 0x013ba1e5 in QGuiEventDispatcherGlib::processEvents (this=0x9200610, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x04935289 in QEventLoop::processEvents (this=0xbfeeaa54, flags=...) at kernel/qeventloop.cpp:149
#24 0x04935522 in QEventLoop::exec (this=0xbfeeaa54, flags=...) at kernel/qeventloop.cpp:201
#25 0x04939ecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#26 0x013018e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#27 0x080f16b0 in _start ()

This bug may be a duplicate of or related to bug 207778.

Possible duplicates by query: bug 207778.

Reported using DrKonqi
Comment 1 Matthias Fuchs 2011-10-23 14:25:49 UTC
Can you reproduce this issue?

If yes please install the kget debug symbols (might bei kdenetwork debug package) and update the backtrace. As right now the backtrace is unfortunately of no use.
Comment 2 Andrew Crouthamel 2018-09-22 02:03:59 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 3 Andrew Crouthamel 2018-10-27 03:58:57 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!