Bug 317053 - kget crashed after deleting the ~/Downloads folder
Summary: kget crashed after deleting the ~/Downloads folder
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: 2.10.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-03-20 00:07 UTC by Gregory Seaborn
Modified: 2018-10-27 04:20 UTC (History)
0 users

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 Gregory Seaborn 2013-03-20 00:07:46 UTC
Application: kget (2.10.1)
KDE Platform Version: 4.10.1
Qt Version: 4.8.4
Operating System: Linux 3.8.2-206.fc18.x86_64 x86_64
Distribution: "Fedora release 18 (Spherical Cow)"

-- Information about the crash:
- What I was doing when the application crashed:  Deleted the Downloads folder in my home directory

- Unusual behavior I noticed:  had a couple of downloaded files that I was not able to delete

-- Backtrace:
Application: KGet (kget), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f0590cf2880 (LWP 5619))]

Thread 2 (Thread 0x7f0581d64700 (LWP 5625)):
#0  g_main_context_query (context=context@entry=0x7f05780009a0, max_priority=2147483647, timeout=timeout@entry=0x7f0581d63b7c, fds=fds@entry=0x7f05780029b0, n_fds=n_fds@entry=2) at gmain.c:3049
#1  0x00000035ea847c99 in g_main_context_iterate (context=context@entry=0x7f05780009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3272
#2  0x00000035ea847e44 in g_main_context_iteration (context=0x7f05780009a0, may_block=1) at gmain.c:3351
#3  0x0000003ea8fa6126 in QEventDispatcherGlib::processEvents (this=0x7f05780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x0000003ea8f7680f in QEventLoop::processEvents (this=this@entry=0x7f0581d63cd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x0000003ea8f76a98 in QEventLoop::exec (this=0x7f0581d63cd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x0000003ea8e78980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#7  0x0000003ea8f5703f in QInotifyFileSystemWatcherEngine::run (this=0x17e03d0) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x0000003ea8e7b95c in QThreadPrivate::start (arg=0x17e03d0) at thread/qthread_unix.cpp:338
#9  0x0000003c70407d15 in start_thread (arg=0x7f0581d64700) at pthread_create.c:308
#10 0x0000003c700f246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7f0590cf2880 (LWP 5619)):
[KCrash Handler]
#5  0x0000003c70035ba5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#6  0x0000003c70037358 in __GI_abort () at abort.c:90
#7  0x0000003c74060e1d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#8  0x0000003c7405eeb6 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#9  0x0000003c7405eee3 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#10 0x0000003c7405f156 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#11 0x0000003ea8f76d04 in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#12 0x0000003ea8f7b888 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#13 0x0000000000429f27 in main ()

Possible duplicates by query: bug 308801, bug 306218, bug 305584, bug 302555, bug 297788.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-09-30 13:31:29 UTC
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If you can reproduce the crash every time,  please follow the guide[1] and try to run it under gdb to get a better backtrace.  

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 2 Andrew Crouthamel 2018-09-25 03:40:49 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 04:20:49 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!