Application: plasma-discover (5.19.5) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.8-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: I clicked to install Kdictionary from Snap and after a few seconds clicked to cancle, because I changed my mind. Discover (on Fedora 33 x86_64) crashed immediately. Custom settings of the application: My Discover is using Flatpak (set up by default by the distribution), Snap - which I installed with the offical repo rpm, and RPM Fusion free and non-free (all stable, no debug or sources or anything besides quick easy use for stable packages). -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007f9d8833c659 in QObjectPrivate::maybeSignalConnected(unsigned int) const () from /lib64/libQt5Core.so.5 #5 0x00007f9d88346e04 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x00007f9d44268b4e in update_changes () from /lib64/libsnapd-glib.so.1 #7 0x00007f9d44269259 in parse_response () from /lib64/libsnapd-glib.so.1 #8 0x00007f9d442695bd in read_cb () from /lib64/libsnapd-glib.so.1 #9 0x00007f9d861feccb in socket_source_dispatch () from /lib64/libgio-2.0.so.0 #10 0x00007f9d868f77ef in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #11 0x00007f9d869495d8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #12 0x00007f9d868f4bc3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #13 0x00007f9d88363a2f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #14 0x00007f9d8831764b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #15 0x00007f9d8831f010 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #16 0x0000557f4febdf10 in main () [Inferior 1 (process 23927) detached] Possible duplicates by query: bug 429344, bug 429000, bug 428876, bug 428480, bug 428403. Reported using DrKonqi
Backtrace indicates the crash is entirely upstream of us. I suppose you would have to open this on the Fedora bug tracker since it doesn't seem like any KDE code is involved. Hopefully they can figure out what's going on.