Bug 468875

Summary:	[System Settings] Crash when opening Flatpak Permissions KCM
Product:	[KDE Neon] neon	Reporter:	popov895 <popov895>
Component:	general	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	crash	CC:	joshiesuhaas0, jr, neon-bugs-null, popov895, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description popov895 2023-04-23 19:09:07 UTC

SUMMARY

After removing the flatpak package using the `apt purge flatpak` command, System Preferences crashes when trying to open the Flatpak Permissons KCM page. I assume this happens when trying to access something in the /var/lib/flatpak/, which is removed by the`apt purge`.

STEPS TO REPRODUCE

1. remove the flatpak package using the `apt purge flatpak`
2. Open System Settings
3. Open Flatpak Permissons KCM page

SOFTWARE/OS VERSIONS

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.15.0-60-generic (64-bit)
Graphics Platform: X11

Comment 1 ratijas 2023-04-24 12:49:40 UTC

Did you expect an application to keep working after you removed a library that it relied on?  FWIW if you were able to "purge" flatpak AND keep flatpak-kcm package in place, then it suggests a packaging issue, like missing dependency requirement in package meta-data.

Comment 2 popov895 2023-04-24 13:49:27 UTC

It makes sense to make the `flatpak-kcm` package dependent on the `flattpak` package. Is it possible?

Comment 3 Carlos De Maine 2025-09-20 09:36:03 UTC

Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!