Created attachment 1484256 [details] Full backtrace exported from gdb Description of problem: I am running a custom build of QuiteRSS which is built against Qt5 instead of Qt4. You can see the changes at [1] Version-Release number of selected component (if applicable): qt5-qtbase-5.11.1-7.fc28.x86_64 qtsingleapplication-qt5-2.6.1-32.fc28.x86_64 qt5-qtwebkit-5.212.0-0.27.alpha2.fc28.x86_64 qt5-qtwebengine-5.11.1-4.fc28.x86_64 How reproducible: always with this application Steps to Reproduce: 1. update qt5 to 5.11.1-7 2. start quiterss Actual results: Quiterss fails to start. The backtrace is deep in Qt code so I think that QuiteRSS code is not to blame. This is the truncated backtrace (full backtrace attached): #0 0x00007ffff2722edf in memcpy.5 () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:141 #1 0x00007ffff39627c9 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:34 #2 0x00007ffff39627c9 in QString::append(QString const&) (this=this@entry=0x7fffffffccf8, str=...) at tools/qstring.cpp:2444 #3 0x00005555556795fe in QString::operator+=(QString const&) (s=..., this=0x7fffffffccf8) at /usr/include/qt5/QtCore/qstring.h:474 #4 0x00005555556795fe in operator+(QString const&, char const*) (s2=0x555555729f59 "/debug.log", s1=...) at /usr/include/qt5/QtCore/qstring.h:1341 #5 0x00005555556795fe in LogFile::msgHandler(QtMsgType, QMessageLogContext const&, QString const&) (type=QtInfoMsg, msg=...) at src/application/logfile.cpp:40 #6 0x00007ffff38e1955 in qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) (msgType=QtInfoMsg, context=..., message=...) at /usr/include/c++/8/bits/atomic_base.h:82 #7 0x00007ffff38e319c in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) (msgType=QtInfoMsg, context=..., message=...) at global/qlogging.cpp:1851 #8 0x00007ffff39cb658 in QDebug::~QDebug() (this=0x7fffffffcee8, __in_chrg=<optimized out>) at io/qdebug.cpp:154 #9 0x00007ffff3fd03e2 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x5555559fb070) at kernel/qguiapplication.cpp:1306 #10 0x00007ffff3fd0595 in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1389 #11 0x00007ffff3a8b5f5 in QCoreApplicationPrivate::init() (this=<optimized out>) at kernel/qcoreapplication.cpp:845 #12 0x00007ffff3fd2463 in QGuiApplicationPrivate::init() (this=0x5555559fb070) at kernel/qguiapplication.cpp:1418 #13 0x00007ffff73be10d in QApplicationPrivate::init() (this=0x5555559fb070) at kernel/qapplication.cpp:565 #14 0x00007ffff78cf235 in QtSingleApplication::QtSingleApplication(int&, char**, bool) (this=0x7fffffffd210, argc=<optimized out>, argv=<optimized out>, GUIenabled=<optimized out>) at ../../src/qtsingleapplication.cpp:154 Expected results: QuiteRSS should start just fine. Additional info: with Qt 5.10.1, anything worked fine. "Good" Qt versions: qt5-qtbase-5.10.1-6 qt5-qtwebkit-5.10.1-4 qt5-qtwebkit-5.212.0-0.20.alpha2.fc28.x86_64 same version of qtsingleapplication-qt5 [1] https://src.fedoraproject.org/rpms/quiterss/pull-request/2 PS: Does anyone know why this pull request is not being merged? It seems like it is completely ignored. The previous version (pull #1) has been open unanswered for a year.
Others have run upstream QuiteRSS on Qt 5.11 before. Also, rebuilding QuiteRSS against Qt 5.11 does not fix the issue. Workaround: Downgrade to Qt 5.10.
#7 0x00007ffff38e319c in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) (msgType=QtInfoMsg, context=..., message=...) at global/qlogging.cpp:1851 #8 0x00007ffff39cb658 in QDebug::~QDebug() (this=0x7fffffffcee8, __in_chrg=<optimized out>) at io/qdebug.cpp:154 #9 0x00007ffff3fd03e2 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x5555559fb070) So here, your application is trying to load a platform plugin and sending some logging output. That logging output may be helpful to debug. Since this is specific to a particular application, I'm going to tentatively re-assign this there (even if the bug doesn't occur in it's default distro configuration). This way, it's maintainer(s) will see this and be able to comment (and potentially reply to your pull request query).
I've created an upstream bug report as this issue not only affects my own builds but any QuiteRSS build running with Qt 5.11 under a GNOME/Wayland session. I added a few details and also some workarounds.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
I have not seen this bug in a while on Fedora 29.