Bug 457134 - discover crashes when going in to the installed tab
Summary: discover crashes when going in to the installed tab
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.24.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-25 19:44 UTC by geqch0akc
Modified: 2022-08-25 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description geqch0akc 2022-07-25 19:44:48 UTC
SUMMARY
***
discover crashes when going in to the installed tab

Application: Discover (plasma-discover), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f74981165c7 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#5  0x00007f7498123b3b in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#6  0x00007f74b47a740e in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f74b5918713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007f74b4779e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f74b477cf17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f74b47d3a57 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f74b3070d1b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f74b30c56f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f74b306e3c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f74b47d30a8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f74b477874b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f74b4780ce4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x0000557a2933d638 in  ()
#18 0x00007f74b4095d90 in __libc_start_call_main (main=main@entry=0x557a2933cd40, argc=argc@entry=1, argv=argv@entry=0x7ffdb9da4a88) at ../sysdeps/nptl/libc_start_call_main.h:58
#19 0x00007f74b4095e40 in __libc_start_main_impl (main=0x557a2933cd40, argc=1, argv=0x7ffdb9da4a88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdb9da4a78) at ../csu/libc-start.c:392
#20 0x0000557a2933e075 in  ()
[Inferior 1 (process 119760) detached]

***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
discover crashing

EXPECTED RESULT
discover not crashing

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Celeron® G4900 CPU @ 3.10GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 610
ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-07-26 18:33:25 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

> #4  0x00007f74981165c7 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
> #5  0x00007f7498123b3b in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so

Could you please install debug symbols for Discover's Flatpak backend, 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!
Comment 2 Bug Janitor Service 2022-08-10 04:35:54 UTC
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!
Comment 3 Bug Janitor Service 2022-08-25 04:35:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!