Created attachment 111038 [details]
Unmet dependency errors while browsing
Recently Discover has started to emit passiveNotifications about unmet dependencies while browsing app lists. There are several problems here:
1. This is not appropriate or something the user needs to be burdened with while browsing. At most, Discover should show an error message during installation of the broken app, not anywhere else.
2. PassiveNotifications should be safely ignorable, e.g. for status updates. These errors are not ignorable; they block installation and must be dealt with. It is not appropriate to use a passiveNotification for these errors.
- While browsing, don't show passiveNotifications about unmet dependencies
- When trying to install an app with broken dependencies, show a real modal error pop-up with the full detailed message, so ensure that the user sees it
Git commit e7cec342b0c2b570450c1b51694ecb36054f75bd by Aleix Pol.
Committed on 27/02/2018 at 13:22.
Pushed by apol into branch 'Plasma/5.12'.
Don't track errors when fetching dependencies
M +0 -1 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp
Created attachment 111221 [details]
Still happening in git master
Still happening, I'm afraid.
Haven't seen 'em in git master. I wonder if maybe my still seeing them was the result of not having had 5.12 content merged back to master?
Will re-open if I see these messages again.