Summary: | kget crashes during transfer | ||
---|---|---|---|
Product: | [Applications] kget | Reporter: | michael w. ransom <ran31som> |
Component: | general | Assignee: | KGet authors <kget> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, christophe, ran31som |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
michael w. ransom
2008-11-28 21:45:54 UTC
This backtrace is not usable; please see: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Kget stopped transfer of Suse 11.1-rc1 @ 96%, I tried to restart/resume kget, but it would not. I closed kget and restarted it crashed upon restart. I printed the result as seen above Application: KGet (kget), signal SIGSEGV [?1034h(no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5f8b8e0 (LWP 5315)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7760b2e in KJob::processedAmount () from /usr/lib/libkdecore.so.5 #7 0xb7bea75d in ?? () from /usr/lib/libkgetcore.so.4 #8 0xb7bead6a in ?? () from /usr/lib/libkgetcore.so.4 #9 0xb7bd4c15 in ?? () from /usr/lib/libkgetcore.so.4 #10 0xb755b740 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb755c4c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb7596bc7 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #13 0xb75621de in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #14 0xb75561ff in QObject::event () from /usr/lib/libQtCore.so.4 #15 0xb672582c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #16 0xb672d6ce in QApplication::notify () from /usr/lib/libQtGui.so.4 #17 0xb7dab31d in KApplication::notify () from /usr/lib/libkdeui.so.5 #18 0xb7546a71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #19 0xb7574de6 in ?? () from /usr/lib/libQtCore.so.4 #20 0xb75712b0 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb60ac2d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0xb60af85b in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #23 0xb60af9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0xb7571208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb67be885 in ?? () from /usr/lib/libQtGui.so.4 #26 0xb754514a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb754530a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #28 0xb75479a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #29 0xb67256a7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #30 0x080961ba in _start () #0 0xffffe430 in __kernel_vsyscall () @michael: you need to install the "-debuginfo" packages in order to get an useful backtrace. Please install them and check if you can still reproduce this crash. If you do, please post the completa backtrace here. Thanks :) No useful backtrace was provided for this bug report (see comment #1). Changing its status. 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 mark the bug 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! 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! |