Bug 483708

Summary:	Crash
Product:	[Applications] Discover	Reporter:	Maydo Al-Dosery <maydohelp>
Component:	discover	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	aleixpol, sitter
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.27.8
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Maydo Al-Dosery 2024-03-15 21:57:56 UTC

Application: plasma-discover (5.27.8)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-25-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
When I opened the Discover app it's litterly crashed for no reason idk why

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  0x000075765e67abdc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
#5  0x000075765e67ac40 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
#6  0x000075765e67ba16 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
#7  0x000075765e68a225 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
#8  0x000075767a0f99a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x000075767bb6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x000075767a0cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x000075767a0cfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000075767a1286f7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x0000757678a5cb2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x0000757678ab846f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x0000757678a5ad20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x000075767a127daa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x000075767a0cb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000075767a0d3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x0000622f7ac08c0f in ?? ()
#20 0x0000757679628150 in __libc_start_call_main (main=main@entry=0x622f7ac08320, argc=argc@entry=1, argv=argv@entry=0x7ffd4d6c1f08) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x0000757679628209 in __libc_start_main_impl (main=0x622f7ac08320, argc=1, argv=0x7ffd4d6c1f08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd4d6c1ef8) at ../csu/libc-start.c:360
#22 0x0000622f7ac095e5 in ?? ()
[Inferior 1 (process 16619) detached]

Reported using DrKonqi

Comment 1 Harald Sitter 2024-04-03 04:39:54 UTC

Is this still reproducible? If so please read through the wiki page and create a new trace, the existing one unfortunately is missing important data.

https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Comment 2 Maydo Al-Dosery 2024-04-03 05:47:32 UTC

(In reply to Harald Sitter from comment #1)
> Is this still reproducible? If so please read through the wiki page and
> create a new trace, the existing one unfortunately is missing important data.
> 
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

No+ This Site has some issues Please fix the domain name or edit it+ However I resolve it and it causes by high requests.

Comment 3 Bug Janitor Service 2024-04-18 03:47:35 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 4 Maydo Al-Dosery 2024-04-18 04:48:42 UTC

Sorry There's some sensitive information in the log which I cannot provide it due to privacy reasons...

Comment 5 Maydo Al-Dosery 2024-04-18 04:51:44 UTC

However I finally fixed it and the problem was just I was having a lot of apps were running and the computer couldn't handle it which causes crash on Discover App.