Description of problem: Every time I close yubico stuff, they crash. Version-Release number of selected component: yubioath-desktop-5.0.2-1.git4df579e.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-launched-yubioath-desktop.desktop-73769.scope cmdline: yubioath-desktop crash_function: QString::~QString executable: /usr/bin/yubioath-desktop journald_cursor: s=35952954a4fc42f5b991ba8ea46ad2b3;i=10b2d4;b=92be42d7512842dd94820e0a85447b59;m=23d2090a7;t=5a1a3450d7f55;x=aeeac7c66a3b5217 kernel: 5.6.0-0.rc5.git0.2.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 QString::~QString at /usr/include/c++/10/bits/atomic_base.h:333 #1 QWindowPrivate::~QWindowPrivate at /usr/include/qt5/QtCore/qpointer.h:53 #2 QQuickWindowPrivate::~QQuickWindowPrivate at items/qquickwindow.cpp:532 #3 QQuickWindowQmlImplPrivate::~QQuickWindowQmlImplPrivate at items/qquickwindowmodule.cpp:57 #5 QQmlPrivate::QQmlElement<QQuickApplicationWindow>::~QQmlElement at /usr/include/qt5/QtQml/qqmlprivate.h:106 #7 qDeleteAll<QList<QObject*>::const_iterator> at /usr/include/qt5/QtCore/qalgorithms.h:319 #8 qDeleteAll<QList<QObject*> > at /usr/include/qt5/QtCore/qalgorithms.h:328 #9 QQmlApplicationEnginePrivate::cleanUp at qml/qqmlapplicationengine.cpp:64 #10 QQmlApplicationEngine::~QQmlApplicationEngine at qml/qqmlapplicationengine.cpp:250
Created attachment 1673230 [details] File: backtrace
Created attachment 1673231 [details] File: core_backtrace
Created attachment 1673232 [details] File: cpuinfo
Created attachment 1673233 [details] File: dso_list
Created attachment 1673234 [details] File: environ
Created attachment 1673235 [details] File: exploitable
Created attachment 1673236 [details] File: limits
Created attachment 1673237 [details] File: maps
Created attachment 1673238 [details] File: mountinfo
Created attachment 1673239 [details] File: open_fds
Created attachment 1673240 [details] File: proc_pid_status
Test with new release.
*** Bug 1835787 has been marked as a duplicate of this bug. ***