Bug 400398

Summary:	KPackagekitDaemon crashes on void repositories
Product:	[Unmaintained] plasma-pk-updates	Reporter:	Martin van Es <bugs>
Component:	general	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED FIXED
Severity:	crash	CC:	justin.zobel
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Martin van Es 2018-10-28 08:59:59 UTC

Plasma systray shows me an icon telling me updates are available. When I click this icon, Discover is openened. While Discover fetches list of new packages (check for updates equivalent), kpackagekitd crashes.

The only way to stop the crashing is to remove all repositories that cause packagekit to output a line containing:

E: The repository 'http://ppa.launchpad.net/freecad-maintainers/freecad-legacy/ubuntu cosmic Release' does not have a Release file.

I am aware that the repository might not have valid packages for cosmic YET, but I want to be notified as soon as (and if) the maintainer has moved on to cosmic without constantly having to check launchpad.

My expectation would be that any package management system would gracefully ignore such errors and continue with valid configuration. Aptitude e.g. shows, but ignores these errors. I also may make mistakes editing the repository file(s) and expect to be gracefully forgiven for such mistakes, albeit without the expected updates from that repository.

STEPS TO REPRODUCE
1. Add possible future (but invalid) repository location to /etc/apt/sources.list.d/ directory
2. Start Discover, check for updates
3. Tail .xsession-errors file
4. See '... does not have a Release file.' error(s) and kpackagekitd crash

OBSERVED RESULT
kpackagekit crashes

EXPECTED RESULT
Gracefully ignore the errors and continue to update valid repositories

SOFTWARE VERSIONS
KDE Plasma Version: 5.14.2
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.1

Comment 1 Justin Zobel 2020-12-04 04:58:15 UTC

Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.

Comment 2 Martin van Es 2020-12-07 13:42:55 UTC

It's fixed for me.
Check with Discover 5.19.5.