Bug 453513 - Discover crashes every time when retrieving updates
Summary: Discover crashes every time when retrieving updates
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-07 17:13 UTC by Udo
Modified: 2022-05-13 13:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot discover crash message (135.17 KB, image/png)
2022-05-07 17:13 UTC, Udo
Details
GDB crash log (3.19 KB, text/plain)
2022-05-10 07:05 UTC, Udo
Details
gdb output (5.31 KB, text/plain)
2022-05-12 09:05 UTC, Udo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Udo 2022-05-07 17:13:15 UTC
Created attachment 148649 [details]
Screenshot discover crash message

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Error message:
Ausführbare Datei: plasma-discover PID: 53568 Signal: Segmentation fault (11) Datum: 07.05.22 19:07:01 CEST

STEPS TO REPRODUCE
1. click on Discover symbol in control panel when having a blue dot
2. Discover starts and is retrieving updates
3. Crash: Ausführbare Datei: plasma-discover PID: 53568 Signal: Segmentation fault (11) Datum: 07.05.22 19:07:01 CEST

OBSERVED RESULT

crash

EXPECTED RESULT

getting updates

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Comment 1 Nate Graham 2022-05-09 17:08:12 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!
Comment 2 Udo 2022-05-10 07:05:13 UTC
Created attachment 148695 [details]
GDB crash log

Hi Nate,
have attached a crash report. Hope it is usable resp. the right one. Could only find GDB as debugger.
When looking at it (I am not a programmer and for sure no system programmer) is the crash reason the:
"../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden." (Means: File or directory not found) ?
Regards
Udo
Comment 3 Udo 2022-05-10 07:06:59 UTC
Sorry, have read, that one should also copy&paste the report:
--------------------------------------------------------------------------------------------------------------------------------------
Haltepunkt 2 at 0x7ffff5c097b0
Haltepunkt 3 at 0x7ffff5c09800
Continuing.
[Detaching after fork from child process 11732]
[Thread 0x7fffb7fff640 (LWP 11574) exited]
[Thread 0x7ffff048c640 (LWP 11528) exited]
[Thread 0x7fffe48e1640 (LWP 11648) exited]
[Thread 0x7fffabfff640 (LWP 11633) exited]
[Thread 0x7fffaaffd640 (LWP 11650) exited]
[Thread 0x7fffaa7fc640 (LWP 11651) exited]
[Thread 0x7fffab7fe640 (LWP 11649) exited]
[Thread 0x7fffa3fff640 (LWP 11638) exited]
[Thread 0x7fffa8ffd640 (LWP 11634) exited]
[Thread 0x7fffb5f7c640 (LWP 11550) exited]
[Thread 0x7fffd33e2640 (LWP 11541) exited]
[Thread 0x7fffd2ad9640 (LWP 11542) exited]

Thread 1 "plasma-disover" received signal SIGSTOP, Stopped (signal).
0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffffffcf90, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
29	../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden.
#0  0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffffffcf90, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007ffff7773808 in  () at /lib/x86_64-linux-gnu/libKF5Crash.so.5
#2  0x00007ffff7774513 in KCrash::defaultCrashHandler(int) () at /lib/x86_64-linux-gnu/libKF5Crash.so.5
#3  0x00007ffff5976520 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007fffe40b8327 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#5  0x00007fffe40c69de in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#6  0x00007ffff6067a53 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ffff5e4dec5 in QFutureWatcherBase::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff71c86b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007ffff603016a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff6033257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff6089ef7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff496a8bb in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff49bdf08 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff4968003 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff6089548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff602ea9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff6037024 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000055555556b637 in  ()
#19 0x00007ffff595dfd0 in __libc_start_call_main (main=main@entry=0x55555556ad40, argc=argc@entry=1, argv=argv@entry=0x7fffffffe528)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x00007ffff595e07d in __libc_start_main_impl (main=
    0x55555556ad40, argc=1, argv=0x7fffffffe528, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe518)
    at ../csu/libc-start.c:409
#21 0x000055555556c045 in  ()
[Inferior 1 (process 11524) killed]
Comment 4 Nate Graham 2022-05-10 15:32:18 UTC
> #4  0x00007fffe40b8327 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
> #5  0x00007fffe40c69de in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so

This is very likely Bug 443745, but I can't know without debug symbols for the Flatpak backend for Discover. Can you install those, reproduce the crash, and get a new backtrace that shows more for these lines?
Comment 5 Udo 2022-05-10 18:30:22 UTC
Sorry, as I wrote, I am not an expert - so when I try, I get an error -see below. Also the next I tried was unsuccessful... see also below....
---------------------------------------------------------------------------------------------------------------------------
xetcst@Tower-Ryzen:~$ flatpak --run plasma-discover
Fehler: 'plasma-discover' is not a flatpak command. Did you mean '--gl-drivers'?

See 'flatpak --help'
xetcst@Tower-Ryzen:~$ flatpak list
Name                                      Application ID                                    Version     Zweig         Ursprung              Installation
AstroMenace                               com.viewizard.AstroMenace                         1.4.1       stable        astromenace-origin    system
Entangle                                  org.entangle_photo.Manager                        3.0         stable        flathub               system
TAP-plugins                               org.freedesktop.LinuxAudio.Plugins.TAP            1.0.1       21.08         flathub               system
SWH                                       org.freedesktop.LinuxAudio.Plugins.swh            0.4.17      21.08         flathub               system
Freedesktop Platform                      org.freedesktop.Platform                          21.08.12    21.08         flathub               system
Mesa                                      org.freedesktop.Platform.GL.default               21.3.8      21.08         flathub               system
nvidia-470-103-01                         org.freedesktop.Platform.GL.nvidia-470-103-01                 1.4           flathub               system
openh264                                  org.freedesktop.Platform.openh264                 2.1.0       2.0           flathub               system
GNOME Application Platform version 42     org.gnome.Platform                                            42            flathub               system
Adwaita theme                             org.kde.KStyle.Adwaita                                        5.15-21.08    flathub               system
KDE Application Platform                  org.kde.Platform                                              5.15-21.08    flathub               system
Kdenlive                                  org.kde.kdenlive                                  22.04.0     stable        flathub               system
xetcst@Tower-Ryzen:~$
------------------------------------------------------------------------------------------------------------------------------------------------------
xetcst@Tower-Ryzen:~$ flatpak install flathub org.kde.Platform//5.13.0-40
Looking for matches…

Fehler: Nothing matches org.kde.Platform in remote flathub
xetcst@Tower-Ryzen:~$ 
xetcst@Tower-Ryzen:~$ flatpak install flathub org.kde.Sdk//5.13.0-40
Looking for matches…
Fehler: Nothing matches org.kde.Sdk in remote flathub
xetcst@Tower-Ryzen:~$
Comment 6 Nate Graham 2022-05-10 18:50:51 UTC
Discover isn't installed as a Flatpak, so you run it with `plasma-discover`. To get debug symbols, you'll need to use the `apt` package manager. Probably something like `sudo apt install plasma-discover-backend-flatpak` or something like that. It might be slightly different (I'm not so familiar with Kubuntu)
Comment 7 Udo 2022-05-12 09:05:56 UTC
Created attachment 148757 [details]
gdb output

gdb output
Comment 8 Udo 2022-05-12 09:08:25 UTC
So I did install "plasma-discover-backend-flatpak" and again did gdb debug:
----------------------------------------------------------------------------------------------------------------------------
"Haltepunkt 2 at 0x7ffff5c097b0
Haltepunkt 3 at 0x7ffff5c09800
Continuing.
[Detaching after fork from child process 11732]
[Thread 0x7fffb7fff640 (LWP 11574) exited]
[Thread 0x7ffff048c640 (LWP 11528) exited]
[Thread 0x7fffe48e1640 (LWP 11648) exited]
[Thread 0x7fffabfff640 (LWP 11633) exited]
[Thread 0x7fffaaffd640 (LWP 11650) exited]
[Thread 0x7fffaa7fc640 (LWP 11651) exited]
[Thread 0x7fffab7fe640 (LWP 11649) exited]
[Thread 0x7fffa3fff640 (LWP 11638) exited]
[Thread 0x7fffa8ffd640 (LWP 11634) exited]
[Thread 0x7fffb5f7c640 (LWP 11550) exited]
[Thread 0x7fffd33e2640 (LWP 11541) exited]
[Thread 0x7fffd2ad9640 (LWP 11542) exited]

Thread 1 "plasma-discover" received signal SIGSTOP, Stopped (signal).
0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffffffcf90, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
29	../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden.
#0  0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffffffcf90, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007ffff7773808 in  () at /lib/x86_64-linux-gnu/libKF5Crash.so.5
#2  0x00007ffff7774513 in KCrash::defaultCrashHandler(int) () at /lib/x86_64-linux-gnu/libKF5Crash.so.5
#3  0x00007ffff5976520 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007fffe40b8327 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#5  0x00007fffe40c69de in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#6  0x00007ffff6067a53 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ffff5e4dec5 in QFutureWatcherBase::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff71c86b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007ffff603016a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff6033257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff6089ef7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff496a8bb in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff49bdf08 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff4968003 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff6089548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff602ea9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff6037024 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000055555556b637 in  ()
#19 0x00007ffff595dfd0 in __libc_start_call_main (main=main@entry=0x55555556ad40, argc=argc@entry=1, argv=argv@entry=0x7fffffffe528)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x00007ffff595e07d in __libc_start_main_impl (main=
    0x55555556ad40, argc=1, argv=0x7fffffffe528, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe518)
    at ../csu/libc-start.c:409
#21 0x000055555556c045 in  ()
[Inferior 1 (process 11524) killed]
Haltepunkt 2 at 0x7ffff5c097b0
Haltepunkt 3 at 0x7ffff5c09800
Continuing.
[Detaching after fork from child process 16674]
[Thread 0x7fffd15eb640 (LWP 16507) exited]
[Thread 0x7fffad9f1640 (LWP 16594) exited]
[Thread 0x7fffae9f3640 (LWP 16577) exited]
[Thread 0x7fffae1f2640 (LWP 16593) exited]
[Thread 0x7fffb7fff640 (LWP 16581) exited]
[Thread 0x7fffe48e0640 (LWP 16591) exited]
[Thread 0x7ffff048b640 (LWP 16472) exited]
[Thread 0x7fffb6c44640 (LWP 16592) exited]
[Thread 0x7fffd2ad9640 (LWP 16492) exited]
[Thread 0x7fffd0ad6640 (LWP 16486) exited]
[Thread 0x7fffd33e2640 (LWP 16485) exited]

Thread 1 "plasma-discover" received signal SIGSTOP, Stopped (signal).
0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffffffcf90, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
29	../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden.
Continuing.

Thread 3 "QDBusConnection" received signal SIGCONT, Continued.
[Switching to Thread 0x7fffece2a640 (LWP 16473)]
0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffe001b140, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
29	in ../sysdeps/unix/sysv/linux/poll.c
#0  0x00007ffff5a4bd3f in __GI___poll (fds=0x7fffe001b140, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007ffff49bdea6 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff4968003 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff6089548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007ffff602ea9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ffff5e428c2 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007ffff6efcefb in  () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007ffff5e43a71 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff59c8947 in start_thread (arg=<optimized out>) at pthread_create.c:435
#9  0x00007ffff5a58a44 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
[Inferior 1 (process 16468) killed]
Comment 9 Nate Graham 2022-05-12 16:56:25 UTC
Gotta install the debug package for the flatpak backend package too, or else the backtrace is missing debus symbols and we can't tell where it's crashing. Can you do that?
Comment 10 Udo 2022-05-13 08:48:53 UTC
Hello,
well shame on my. When trying to get the flatpak-backend debug symbols installed I found out, that something was named as "broken" in Muon Softwaremanager when looking at the plasma-discover package. So I removed completely the package - including the flatpak part. Then I reinstalled the whole thing - Muon did NOT requested the flatpak part to be installed. And to my surprise discover is working now...
I do not know when and why the flatpak part was additonally installed since I did not install discover as an extra package. It was part of my Kubuntu installation from the beginning.
Then I also reinstalled the flatpak-backend part - and even that is now working.... maybe there have been some problems with updating the plasma-discover package in the past without any notice or something similar...

So I have set it to resolved and "not a bug" - again, sorry for creating such an effort....
Comment 11 Nate Graham 2022-05-13 13:13:47 UTC
Thanks for the info! Glad you fixed it. If Kubuntu shipped this way, I would recommend that you report the bug to them.