Application: DiscoverNotifier (5.26.4) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 5.15.82-1-MANJARO-ARM-RPI aarch64 Windowing System: X11 Distribution: Manjaro ARM DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: Discover notifier crashes at Plasma session start This seems to happen everytime since I installed : local/flatpak 1:1.15.1-1 Linux application sandboxing and distribution framework (formerly xdg-app) local/libpamac-flatpak-plugin 11.4.1-1 Flatpak plugin for Pamac And the call stack suggests this is actually related. The crash can be reproduced every time. -- Backtrace: Application: Notificateur de Discover (DiscoverNotifier), signal: Segmentation fault [KCrash Handler] #4 0x0000ffff94f6bea4 in flatpak_installation_create_monitor () at /usr/lib/libflatpak.so.0 #5 0x0000ffff95033e98 in () at /usr/lib/qt/plugins/discover-notifier/FlatpakNotifier.so #6 0x0000ffff95033fc8 in () at /usr/lib/qt/plugins/discover-notifier/FlatpakNotifier.so #7 0x0000ffff95034594 in () at /usr/lib/qt/plugins/discover-notifier/FlatpakNotifier.so #8 0x0000aaaabc459660 in () #9 0x0000ffffa4175d1c in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x0000ffffa4de50bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x0000ffffa413f2e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x0000ffffa4142dd8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #13 0x0000ffffa41aaff0 in () at /usr/lib/libQt5Core.so.5 #14 0x0000ffffa2183b58 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #15 0x0000ffffa2184130 in () at /usr/lib/libglib-2.0.so.0 #16 0x0000ffffa2184214 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x0000ffffa41aa398 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #18 0x0000ffffa413d4a4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #19 0x0000ffffa4147c3c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #20 0x0000aaaabc456e4c in () #21 0x0000ffffa3a57b80 in () at /usr/lib/libc.so.6 #22 0x0000ffffa3a57c60 in __libc_start_main () at /usr/lib/libc.so.6 #23 0x0000aaaabc457070 in () [Inferior 1 (process 1024) detached] The reporter indicates this bug may be a duplicate of or related to bug 460503. Reported using DrKonqi
Can you try t get a build with debug symbols? It would make all the difference to us.
Hello, I'm sorry but I'm using distro provided packages and cannot compile my own custom KDE on this machine. I don't have the time resources to dig into this and need to keep the machine fairly stable.
I would recommend switching to a distro that provides proper debuggability for crashes, otherwise their choices are causing you to waste your own time, and that of others. :( In the absence of any way to track it down more, I'm marking this as a dupe of Bug 460503, which looks like it has the same backtrace and is caused by disk automounting happening after autostarted apps, due to Bug 323151. *** This bug has been marked as a duplicate of bug 460503 ***
Jeez I'm sorry to have reported a bug as a vanilla user as it seems you're not ready to consider bug reports from “simple users” that are just reporting that something went bad with all possible detail, but without going thru installing a whole lot of development debug packages on their everyday workhorse... If KDE bug reports are reserved to developers that have the complete development tools with bells and whistles installed on their system, I suppose that it should be mentioned somewhare... However DrKonqi generates bug reports without any mention of this... Sorry for the disturbance.
As https://community.kde.org/Get_Involved/Issue_Reporting says, bug reporting involves some responsibility. It's not just a "throw the bug report over the wall and it gets fixed" thing; there may be further information that developers need from you. In this case, the information we needed from you was impossible for you to provide because your distro made the decision to not provide debug symbols. That's not your fault, but you're affected by that issue anyway. Regardless, I was able to piece together that this is probably a duplicate of Bug 460503 anyway even without the debug symbols, so there's nothing more you need to do here. :) But for future reference, if you do want to submit more crash reports, I would recommend either switching to a distro that provides debug symbols for software they ship, or else learning to compile software so you can provide them yourself. Crash reports with no debug symbols are rarely actionable, except in the case where it's obvious even without debug symbols that it's the same as another already-known crash.