Application: plasma-discover (5.27.80) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 6.4.6-060406-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: Discover crashes everytime I try to open a flatpak bundle with it. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #3 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139882045698752) at ./nptl/pthread_kill.c:44 #4 __pthread_kill_internal (signo=6, threadid=139882045698752) at ./nptl/pthread_kill.c:78 #5 __GI___pthread_kill (threadid=139882045698752, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #6 0x00007f38d7a42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x00007f38d7a287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi
Created attachment 160831 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Can you paste a link to one so I can test it out? #3 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139882045698752) at ./nptl/pthread_kill.c:44 #4 __pthread_kill_internal (signo=6, threadid=139882045698752) at ./nptl/pthread_kill.c:78 #5 __GI___pthread_kill (threadid=139882045698752, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #6 0x00007f38d7a42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x00007f38d7a287f3 in __GI_abort () at ./stdlib/abort.c:79 #8 0x00007f38d82b9172 in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #9 0x00007f38d82ba0f7 in qErrnoWarning(char const*, ...) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #10 0x00007f38d82b90c3 in qt_assert_x(char const*, char const*, char const*, int) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #11 0x00007f38b80d8fb8 in FlatpakSource::addResource(FlatpakResource*) (this=0x5628c5729290, resource=<optimized out>) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:143 #12 0x00007f38b80f82e8 in FlatpakBackend::addAppFromFlatpakBundle(QUrl const&, ResultsStream*) (stream=<optimized out>, url=<optimized out>, this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qsharedpointer_impl.h:271 #13 FlatpakFetchRemoteResourceJob::processFile(QUrl const&) (this=<optimized out>, fileUrl=<optimized out>) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:401 #14 0x00007f38d83a777c in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #15 0x00007f38da189596 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #16 0x00007f38d835a128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #17 0x00007f38d835e0f8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #18 0x00007f38d85b5f97 in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #19 0x00007f38d746ed3b in g_main_dispatch (context=0x7f38cc005040) at ../../../glib/gmain.c:3419 #20 g_main_context_dispatch (context=0x7f38cc005040) at ../../../glib/gmain.c:4137 #21 0x00007f38d74c4258 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f38cc005040, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4213 #22 0x00007f38d746c3e3 in g_main_context_iteration (context=0x7f38cc005040, may_block=1) at ../../../glib/gmain.c:4278 #23 0x00007f38d85b57fe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #24 0x00007f38d8366df3 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #25 0x00007f38d8362d06 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #26 0x00005628c347d575 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./discover/main.cpp:225
Created attachment 160874 [details] flatpak bunble I can reproduce with the attached flatpak bundle.
Thanks. I don't get a crash when opening that file in Discover, though. Is the crash reproducible for you?
Yes, I can reproduce consistently.
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!
Created attachment 161885 [details] screenshot Currently I'm unable to reproduce the crash. But Discover looks like what we can see in the attached screenshot after opening the attached flatpak bundle.
Ok, that's something else. Please run `plasma-discover` in a terminal window to see the errors, and paste them into a new bug report. Thanks!
I can reproduce this crash again.
Have you been able to reproduce this with the latest Plasma 6 code?
Can reproduce on neon unstable, cannot on Arch Linux running Plasma 6 RC2.
Hmm, this suggests that maybe differing Flatpak versions could be at play. Can you compare the versions of flatpak/libflatpak between the distros?
flatpak in neon repos: 1.12.7-1 flatpak in Arch repos: 1.15.6
Thanks. With those differences I'm willing to bet this is an issue with the older Flatpak. Neon folks, can we get Flatpak updated?
Created attachment 165903 [details] backtrace generated on Arch Linux Unfortunately Discover also crashes on Arch Linux when opening the same flatpak bundle. It's harder to reproduce though. Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Graphics Platform: Wayland