Application: plasma-discover (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: That's it. That's it. That's it. That's it. That's it. The crash does not seem to be reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007ff40c4bc2f0 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so #5 0x00007ff42db88163 in TransactionListener::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/plasma-discover/libDiscoverCommon.so #6 0x00007ff42c8e0a93 in () at /lib64/libQt5Qml.so.5 #7 0x00007ff42c7bbf8d in () at /lib64/libQt5Qml.so.5 #8 0x00007ff42c7bf00b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt5Qml.so.5 #9 0x00007ff42c7dbd2f in () at /lib64/libQt5Qml.so.5 #10 0x00007ff42c7df42f in () at /lib64/libQt5Qml.so.5 #11 0x00007ff42c771c92 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /lib64/libQt5Qml.so.5 #12 0x00007ff42c8fb61d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /lib64/libQt5Qml.so.5 #13 0x00007ff42c8ac5cf in QQmlBoundSignalExpression::evaluate(void**) () at /lib64/libQt5Qml.so.5 #14 0x00007ff42c8ad7b0 in () at /lib64/libQt5Qml.so.5 #15 0x00007ff42c8e0565 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /lib64/libQt5Qml.so.5 #16 0x00007ff42bb24ced in () at /lib64/libQt5Core.so.5 #17 0x00007ff4250f3a02 in QQuickAction::triggered(QObject*) () at /lib64/libQt5QuickTemplates2.so.5 #18 0x00007ff4250f607e in () at /lib64/libQt5QuickTemplates2.so.5 #19 0x00007ff4250f6378 in QQuickAbstractButtonPrivate::trigger() () at /lib64/libQt5QuickTemplates2.so.5 #20 0x00007ff4250f9211 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () at /lib64/libQt5QuickTemplates2.so.5 #21 0x00007ff4251134b5 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5QuickTemplates2.so.5 #22 0x00007ff42ce86de8 in QQuickItem::event(QEvent*) () at /lib64/libQt5Quick.so.5 #23 0x00007ff42d3a52ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #24 0x00007ff42baecb28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #25 0x00007ff42cea1b5a in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at /lib64/libQt5Quick.so.5 #26 0x00007ff42cea3289 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at /lib64/libQt5Quick.so.5 #27 0x00007ff42bf88b35 in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 #28 0x00007ff42d3a52ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #29 0x00007ff42baecb28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #30 0x00007ff42bf7ca1b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #31 0x00007ff42bf500dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5 #32 0x00007ff426b1816a in () at /lib64/libQt5XcbQpa.so.5 #33 0x00007ff42a116f96 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #34 0x00007ff42a117358 in () at /lib64/libglib-2.0.so.0 #35 0x00007ff42a1173ec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #36 0x00007ff42bb460b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #37 0x00007ff42baeb5cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #38 0x00007ff42baf3a50 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #39 0x00005596cfec62a0 in () #40 0x00007ff42b22cbb0 in __libc_start_call_main () at /lib64/libc.so.6 #41 0x00007ff42b22cc79 in __libc_start_main_impl () at /lib64/libc.so.6 #42 0x00005596cfec6c85 in () [Inferior 1 (process 10177) detached] The reporter indicates this bug may be a duplicate of or related to bug 464357. Reported using DrKonqi
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #4 0x00007ff40c4bc2f0 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so > #5 0x00007ff42db88163 in TransactionListener::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/plasma-discover/libDiscoverCommon.so Could you please install debug symbols for Discover and its Flatpak backend package, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. Thanks again!
(In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong: > > > #4 0x00007ff40c4bc2f0 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so > > #5 0x00007ff42db88163 in TransactionListener::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/plasma-discover/libDiscoverCommon.so > > Could you please install debug symbols for Discover and its Flatpak backend > package, reproduce the crash, and attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports for details about how to do this. > > Thanks again! I can't really reproduce it again myself, but I suspect it was because of X11 or the old qt. A bit of an off topic, but could you probably suggest any way to update qt for my distro (openSUSE Tumbleweed)?
Tumbleweed should already have an up-to-date Qt; it's a rolling release distro. According to your bug report, you have Qt 5.15.8 which is current for Plasma. If you can't reproduce the crash, you can always install debug symbols and use `coredumpctl` to re-symbolicate the existing crash report and then paste it in here. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!