Created attachment 151673 [details] Backlog for the crash SUMMARY I have trouble using Discover because it constantly crashes. I get the same error message when it starts "Error updating appstream2" and it always eventually crashes. Im pretty new to Linux and cant find a solution, please help! STEPS TO REPRODUCE 1. Open Discover 2. Click 'Installed' OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Steam OS 3.3 (Steam Deck) (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Hello Steven! Just to set expectations accordingly, this is a bug tracker, not a user support channel. So we can investigate the bug and fix it, but I can't guarantee that you personally will experience it being fixed soon. See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations. That said, we'll be happy to help investigate the bug! To proceed, we need a backtrace of the crash. Can you attach one? If you're not familiar with the process for how to do so, see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Created attachment 151717 [details] plasma-discover-20220813-123212.kcrash Nate,Thank you for your help, I'm at a loss but hopefully it's an easy fix! I ran it through the konsole once and the crash app automade a backtrace, hope it helps! On Tuesday, August 30, 2022 at 03:42:23 PM CDT, Nate Graham <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=458452 Nate Graham <nate@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |BACKTRACE CC| |nate@kde.org Status|REPORTED |NEEDSINFO --- Comment #1 from Nate Graham <nate@kde.org> --- Hello Steven! Just to set expectations accordingly, this is a bug tracker, not a user support channel. So we can investigate the bug and fix it, but I can't guarantee that you personally will experience it being fixed soon. See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations. That said, we'll be happy to help investigate the bug! To proceed, we need a backtrace of the crash. Can you attach one? If you're not familiar with the process for how to do so, see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Created attachment 151718 [details] Discover Crash
I'm afraid that's not a backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
(In reply to Nate Graham from comment #4) > I'm afraid that's not a backtrace. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. Ah my fault! Sorry still new to this, I read over carefully and I believe I have it here: (gdb) backtrace #0 0x00007fffa47d1b67 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #1 0x00007fffa47db7dc in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #2 0x00007ffff6223e86 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #3 0x00007ffff72701a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #4 0x00007ffff620017a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #5 0x00007ffff6200c79 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #6 0x00007ffff6247558 in () at /usr/lib/libQt5Core.so.5 #7 0x00007ffff4a9cf13 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #8 0x00007ffff4af30d9 in () at /usr/lib/libglib-2.0.so.0 #9 0x00007ffff4a9a485 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x00007ffff624b45a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #11 0x00007ffff61f845b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #12 0x00007ffff6203ba7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #13 0x0000555555568950 in () #14 0x00007ffff5bb7b25 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x000055555556931e in () (gdb) Quit
Thanks! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #0 0x00007fffa47d1b67 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so > #1 0x00007fffa47db7dc in () at /usr/lib/qt/plugins/discover/flatpak-backend.so Could you please install debug symbols for discover's flatpak backend, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again!
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!