Version-Release number of selected component: lxqt-panel-0.10.0-5.fc24 Additional info: reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: lxqt-panel crash_function: QObject::disconnect executable: /usr/bin/lxqt-panel global_pid: 13859 kernel: 4.5.1-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 QObject::disconnect at kernel/qobject.cpp:2949 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1126 #3 QDBusConnectionManager::run at qdbusconnection.cpp:191 #4 QThreadPrivate::start at thread/qthread_unix.cpp:340
Created attachment 1150509 [details] File: backtrace
Created attachment 1150510 [details] File: cgroup
Created attachment 1150511 [details] File: core_backtrace
Created attachment 1150512 [details] File: dso_list
Created attachment 1150513 [details] File: environ
Created attachment 1150514 [details] File: exploitable
Created attachment 1150515 [details] File: limits
Created attachment 1150516 [details] File: maps
Created attachment 1150517 [details] File: mountinfo
Created attachment 1150518 [details] File: namespaces
Created attachment 1150519 [details] File: open_fds
Created attachment 1150520 [details] File: proc_pid_status
Created attachment 1150521 [details] File: var_log_messages
I've also seen this crash (100% reproducible) since updating to Qt 5.6 with my PyQt application. I've now reported it upstream: https://bugreports.qt.io/browse/QTBUG-52988
Propably: https://codereview.qt-project.org/#/c/147261/ Is that patch included in our package?
That change was abandoned and replaced by [1] which made it into Qt 5.6.0. It's also a fix for a Windows-only bug[2] so I'm not sure if it's related. [1] https://codereview.qt-project.org/#/c/147866/ [2] https://bugreports.qt.io/browse/QTBUG-49870
*** Bug 1330463 has been marked as a duplicate of this bug. ***
No, the change reference in [1] was abandoned as the wrong approach
(Sorry, I referenced comment #15), comment #16 got it right
Rawhide, see bug #1363936 and bug #1330419. Line numbers of backtrace differ with a small offset, propably cause of Qt 5.7 (f25) vs. Qt 5.6 (f24).
*** Bug 1363936 has been marked as a duplicate of this bug. ***
Some bugs filed against the mscore package have backtraces that look the same: bug 1336203, bug 1351523, bug 1352381, and bug 1364759. I'm getting that same mscore crash on F-25, which has Qt 5.7.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
I'm seeing this on Fedora 25 too, perhaps the version should be updated.
it's fixed in 5.7.1-19, i will push the it into f26 update today.
qt5-qtbase-5.7.1-19.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b0863592f6
qt5-qtbase-5.7.1-19.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b0863592f6
qt5-qtbase-5.7.1-19.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e229cf5d7c
qt5-qtbase-5.7.1-19.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
qt5-qtbase-5.7.1-19.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.