Discover crasFrequent crashes in plasma-discover with libglib-2.0 errorshes after click on apps or extension for apps or plasma extensions

[Paul Schumacher]

Description:
I am experiencing frequent crashes with the application plasma-discover on Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update functions within the Discover UI. Terminal outputs and system logs indicate issues with libglib-2.0, showing repeated trap int3 errors, which are typically used for debug breakpoints in development builds.

Expected Behavior:
Plasma Discover should run smoothly, allowing the management of software updates and installations without crashing.

Actual Behavior:
Discover crashes frequently, especially when trying to access the updates section or other specific parts of the application.

Steps Attempted:

Resetting configuration files for Discover.
Running Discover from the terminal to capture any error outputs.
System update and reinstallation of plasma-discover and its dependencies.
Analyzing system logs with journalctl, which showed repeated issues with libglib-2.0.

System and Package Information:

Ubuntu Version: 22.04.4 LTS
Package Versions:
libglib2.0-0: Installed: 2.72.4-0ubuntu2.2
plasma-discover: Installed: 5.24.7-0ubuntu0.1

This issue significantly impacts the functionality of the Discover application, hindering routine software management and updates. Any assistance or resolution would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libglib2.0-0 2.72.4-0ubuntu2.2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed May 1 09:58:53 2024
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Paul Schumacher (ubuntupaul89)]

I have attached the crash file to this bug report to provide additional information that may assist in diagnosing.

[Sebastien Bacher (seb128)]

Thanks but I'm deleting that file since it might include private/sensitive information and shouldn't be attached to a public report, please follow the instruction from the previous post to submit it properly to the error tracker instead