Bug 1695043

Summary:	Software should clean error messages between launches
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Krajnak <mkrajnak>
Component:	gnome-software	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	jkoten, klember, mclasen
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 07:39:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1739559

Description Martin Krajnak 2019-04-02 11:24:08 UTC

Description of problem:
If I managed to get an error when working with gnome-software and close the application, the error message is still there when I launch the app for the second, even third time.

Version-Release number of selected component (if applicable):
gnome-software-3.30.6-1.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1.Launch gnome-software, get some error message e.g. click Update All in update section (Unable to update "(null)"
2.close gnome-software
3.Launch gnome-software

Actual results:
Error message is still there until it is closed manually.

Expected results:
Error message should gone since it is unrelated to "fresh" start of the app and migh be confusing opening the app half day later.

Additional info:

Comment 3 Richard Hughes 2019-12-12 14:21:44 UTC

Fixed upstream: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/391

Comment 8 RHEL Program Management 2021-02-01 07:39:56 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.