Bug 390217

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:
Attachments: screenshot1
screenshot2

Description Patrick Silva 2018-02-10 14:06:40 UTC
Created attachment 110507 [details]
screenshot1

See screenshots.
Comment 1 Patrick Silva 2018-02-10 14:07:15 UTC
Created attachment 110508 [details]
screenshot2
Comment 2 Nate Graham 2018-02-10 20:30:17 UTC
I have the same issue. Possibly related to or a duplicate of Bug 390193.
Comment 3 Patrick Silva 2018-02-10 20:48:35 UTC
my runtimes are correctly updated despite these error messages.
Comment 4 Nate Graham 2018-02-14 17:41:52 UTC
*** Bug 390425 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2018-02-14 17:43:34 UTC
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.
Comment 6 Aleix Pol 2018-02-22 18:39:29 UTC
Do you get these error messages from the CLI?
Comment 7 Nate Graham 2018-02-22 21:20:53 UTC
Yes. Could we suppress non-fatal error messages, perhaps?
Comment 8 Nate Graham 2018-02-23 16:35:06 UTC
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
Comment 9 Andrew Crouthamel 2018-02-23 16:37:15 UTC
(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.
Comment 10 Aleix Pol 2018-10-11 16:31:33 UTC
Porting to FlatpakTransaction should fix this.

*** This bug has been marked as a duplicate of bug 395923 ***