https://bugs.kde.org/show_bug.cgi?id=497966
--- Comment #41 from Wyatt Childers <[email protected]> --- (In reply to Nate Graham from comment #40) > > making discover more resilient to the PackageKit daemon shutting down or > > crashing? > It can't be; PackageKit is below Discover. It could notice that PackageKit is back and check for updates in the moment. I still haven't restarted and today it did find my updates; I'm guessing this is a problem when the point in time DiscoverNotifier decides to check for updates overlaps with the point in time PackageKit is down. However, if PackageKit comes back up at the time DiscoverNotifier tries to check the issue "resolves itself." > > it seems like it would be worth notifying the user in some way that "hey, I > > use PackageKit > > and it just vanished, please contact your distribution maintainers!" > I'm always in favor of blame shifting, and we already do this in the main UI > of the app. But doing it outside of the main UI, as a notification pop-up, > would drive people mad. I'm 100% certain it would lead to bug reports and > mockery on Reddit. > > Ultimately it's up to distros and PackageKit folks to make this part work > reliably. I don't think Reddit should be a benchmark of much of anything. Just about anything can be robbed of all nuance and turned into a hit piece on Reddit. I'm just saying ... if this really is what's going on (as it appears to be) ... the user needs to have some way of knowing that when the updater ran it couldn't talk to PackageKit and that they need to fix and/or report that. Crawling system logs for a hope and prayer of figuring out what's going on is ... terrible. Less technical folks are unlikely to notice there is even a problem / that they're missing updates. I obviously don't want you to deal with social media harassment or a bombardment of issue report because of PackageKit/distro bugs; but users also need to be notified when something is broken. Perhaps using language like "Fetching update information failed: The PackageKit daemon is down." or "There was a problem fetching updates <Click here for more info>" and then describing with a full page of context "The PackageKit daemon could not be reached. Please reach out to your distribution maintainer for further guidance." would help. Alternatively, Discover could track recent update checks failures that occur for some reason other than being offline and notify the user the next time they open it via a banner that update checks have been failing because PackageKit has been unstable. Discover could also attempt to massage the issue and start the PackageKit service itself (if down when the update check is performed). Basically anything other than "silently fail at checking for updates." Anyways; to cross-link back, I've filed https://bugzilla.redhat.com/show_bug.cgi?id=2432516. I appreciate your efforts; and I do hope you'll reconsider doing SOMETHING more on the KDE side to nudge the user. -- You are receiving this mail because: You are watching all bug changes.
