Bug 1458235

Summary: [abrt] ktorrent: std::__atomic_base<QAbstractEventDispatcher*>::load(): ktorrent killed by signal 11
Product: [Fedora] Fedora Reporter: idesmi
Component: ktorrentAssignee: Roland Wolters <roland.wolters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: alekcejk, rdieter, roland.wolters, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/48c82f881b385d8befb1e34f70f1f1dcaf6f3eef
Whiteboard: abrt_hash:6f60485a38efe06a64c65f5f42655a2c24943fec;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:40:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description idesmi 2017-06-02 11:09:50 UTC 
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
Comment 1 idesmi 2017-06-02 11:09:58 UTC 
Created attachment 1284397 [details]
File: backtrace
Comment 2 idesmi 2017-06-02 11:10:00 UTC 
Created attachment 1284398 [details]
File: cgroup
Comment 3 idesmi 2017-06-02 11:10:02 UTC 
Created attachment 1284399 [details]
File: core_backtrace
Comment 4 idesmi 2017-06-02 11:10:04 UTC 
Created attachment 1284400 [details]
File: cpuinfo
Comment 5 idesmi 2017-06-02 11:10:07 UTC 
Created attachment 1284401 [details]
File: dso_list
Comment 6 idesmi 2017-06-02 11:10:08 UTC 
Created attachment 1284402 [details]
File: environ
Comment 7 idesmi 2017-06-02 11:10:10 UTC 
Created attachment 1284403 [details]
File: exploitable
Comment 8 idesmi 2017-06-02 11:10:11 UTC 
Created attachment 1284404 [details]
File: limits
Comment 9 idesmi 2017-06-02 11:10:14 UTC 
Created attachment 1284405 [details]
File: maps
Comment 10 idesmi 2017-06-02 11:10:16 UTC 
Created attachment 1284406 [details]
File: open_fds
Comment 11 idesmi 2017-06-02 11:10:18 UTC 
Created attachment 1284407 [details]
File: proc_pid_status
Comment 12 idesmi 2017-06-02 11:10:19 UTC 
Created attachment 1284408 [details]
File: var_log_messages
Comment 13 Roland Wolters 2017-11-08 02:39:47 UTC 
I filled a bug upstream. However, without knowing what exactly triggered the bug I am not sure if that will be picked up.
Comment 14 Fedora End Of Life 2018-05-03 08:18:40 UTC 
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.
Comment 15 Fedora End Of Life 2018-05-29 11:40:45 UTC 
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.