Summary: | Error messages during runtime updates | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Patrick Silva <bugseforuns> |
Component: | Updates (interactive) | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andrew.crouthamel, nate |
Priority: | NOR | ||
Version: | 5.12.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=390193 https://bugs.kde.org/show_bug.cgi?id=390959 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
screenshot1
screenshot2 |
Created attachment 110508 [details]
screenshot2
I have the same issue. Possibly related to or a duplicate of Bug 390193. my runtimes are correctly updated despite these error messages. *** Bug 390425 has been marked as a duplicate of this bug. *** These messages aren't very user-friendly, and are becoming a source of bug reports. Perhaps we should have Discover try to do a better job of handing any error conditions internally, and suppress informational or warning messages that aren't actionable to the user. Do you get these error messages from the CLI? Yes. Could we suppress non-fatal error messages, perhaps? Another case of useless, un-actionable warnings. Shall we mark this as a duplicate of that bug that tracks suppressing them on the GUI? Bug 390959 (In reply to Nate Graham from comment #8) > Another case of useless, un-actionable warnings. Shall we mark this as a > duplicate of that bug that tracks suppressing them on the GUI? Bug 390959 Makes sense to me. Porting to FlatpakTransaction should fix this. *** This bug has been marked as a duplicate of bug 395923 *** |
Created attachment 110507 [details] screenshot1 See screenshots.