Version-Release number of selected component: ktorrent-5.0.1-3.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/ktorrent crash_function: std::__atomic_base<QAbstractEventDispatcher*>::load executable: /usr/bin/ktorrent journald_cursor: s=8306104e751a400c8f7e62d9974e79b9;i=108d0;b=0a6ea02d91c8402c8d5dc402d8631b89;m=e72f986a;t=550f7ea0def0a;x=4682aeb9b02c8c9d kernel: 4.11.2-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 std::__atomic_base<QAbstractEventDispatcher*>::load at /usr/include/c++/7/bits/atomic_base.h:713 #1 std::atomic<QAbstractEventDispatcher*>::load at /usr/include/c++/7/atomic:452 #2 QAtomicOps<QAbstractEventDispatcher*>::load<QAbstractEventDispatcher*> at ../../src/corelib/arch/qatomic_cxx11.h:227 #3 QBasicAtomicPointer<QAbstractEventDispatcher>::load at ../../src/corelib/thread/qbasicatomic.h:235 #4 QSocketNotifier::setEnabled at kernel/qsocketnotifier.cpp:237 #5 socketNotifierSourceCheck at kernel/qeventdispatcher_glib.cpp:88 #6 g_main_context_check at gmain.c:3801 #8 g_main_context_iteration at gmain.c:4029 #9 QEventDispatcherGlib::processEvents at kernel/qeventdispatcher_glib.cpp:425 #10 QEventLoop::exec at kernel/qeventloop.cpp:212
Created attachment 1284397 [details] File: backtrace
Created attachment 1284398 [details] File: cgroup
Created attachment 1284399 [details] File: core_backtrace
Created attachment 1284400 [details] File: cpuinfo
Created attachment 1284401 [details] File: dso_list
Created attachment 1284402 [details] File: environ
Created attachment 1284403 [details] File: exploitable
Created attachment 1284404 [details] File: limits
Created attachment 1284405 [details] File: maps
Created attachment 1284406 [details] File: open_fds
Created attachment 1284407 [details] File: proc_pid_status
Created attachment 1284408 [details] File: var_log_messages
I filled a bug upstream. However, without knowing what exactly triggered the bug I am not sure if that will be picked up.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.