Bug 1069833

Summary:	[GUI] Yumex hides current selections
Product:	[Fedora] Fedora	Reporter:	Raphael Groner <projects.rg>
Component:	yumex	Assignee:	Tim Lauridsen <tim.lauridsen>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-04 06:32:23 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:

Description Raphael Groner 2014-02-25 18:05:32 UTC

Description of problem:
In Installed packages tab, selected packages for outstanding removal aren't remarked after the user has cancelled a dependency check dialog.

Version-Release number of selected component (if applicable):
3.0.13-1

How reproducible:
yes

Steps to Reproduce:
1. Go to Installed tab
2. Check some installed package to be removed (bin icon appears)
3. Click on Apply, wait for yum, then cancel the dependencies dialog

Actual results:
Previously checked packages are unchecked and can't be rechecked. Though, a second Apply remembers the old selection what packages need to be removed.

Expected results:
Consistent check marks in the package list, according to the next yum transaction. That means: Packages that have a "to remove" mark should be iconized as such.

Additional info:
I tried with kdepim package, for instance.

Comment 1 Raphael Groner 2014-09-14 12:51:57 UTC

Still reproducible with yumex-3.0.15-1.fc20.noarch

I have to swith the tab, e.g. to Available, and back to Installed to hide all check marks. The Apply button is then without any function, similar to bug #1140371.

Raising severity cause could insult usability experience.

Comment 2 Tim Lauridsen 2014-09-15 07:43:43 UTC

I can reproduce this bug, I will look into the issue and fix it

Comment 3 Tim Lauridsen 2014-10-04 06:32:23 UTC


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