SUMMARY I just experienced a crash when clicking the discover icon from the system tray. This is the error log that it gave: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007f0024390458 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #5 0x00007f00243961fa in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #6 0x00007f0024399c4e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #7 0x00007f0094c60d6e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f0095d826af in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x00007f0094c3475a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f0094c377a7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f0094c8c733 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f00932bac7b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007f00932baf28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007f00932bafdf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007f0094c8bdb4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f0094c3316b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f0094c3b440 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x000056409dd25f51 in ?? () #19 0x00007f00945d9e4a in __libc_start_main (main=0x56409dd256a0, argc=3, argv=0x7ffd3e5c8858, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd3e5c8848) at ../csu/libc-start.c:314 #20 0x000056409dd2644a in ?? () [Inferior 1 (process 6241) detached] SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD VEGA10
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong: #4 0x00007f0024390458 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #5 0x00007f00243961fa in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #6 0x00007f0024399c4e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so Could you please install debug symbols for Discover's 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 Thanks again!
This is another crash **with** debug symbols installed. It doesn't look like they add anything to the log: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007fb5e4438458 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #5 0x00007fb5e443e1fa in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #6 0x00007fb5e4441c4e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #7 0x00007fb62b505d6e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fb62c6276af in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x00007fb62b4d975a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007fb62b4dc7a7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007fb62b531733 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007fb629b5fc7b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007fb629b5ff28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007fb629b5ffdf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007fb62b530db4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007fb62b4d816b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007fb62b4e0440 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x000055955e0a7f51 in ?? () #19 0x00007fb62ae7ee4a in __libc_start_main (main=0x55955e0a76a0, argc=3, argv=0x7ffd75c7b368, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd75c7b358) at ../csu/libc-start.c:314 #20 0x000055955e0a844a in ?? () [Inferior 1 (process 1720198) detached]
See those instances of " ?? ()" That means there are no symbols for that thing. In this case, it means that your discover flatpak backend package is missing the symbols. We need symbols for that exact package. Nonetheless based on the number of stack frames in the flatpak backend code, I can make an educated guess that it's Bug 443745, which thankfully is already fixed. *** This bug has been marked as a duplicate of bug 443745 ***