Bug 17420

Summary:	mga6: unable to deselect rpm for removal (rpmdrake)
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake-6.21-1.mga6	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	11778

Description Bit Twister 2015-12-30 03:12:36 CET

Description of problem:

unable to deselect rpm for removal or any other rpm.

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


How reproducible: always


Steps to Reproduce:
1. mcc->Software Management->Install & Remove Software 
2. pick a rpm for removal, example old kernel.

3.


Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2016-01-01 17:40:32 CET

Still valid rpmdrake-6.21-1.mga6

When started from a terminal, I see things like:

(drakrpm:28962): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3568:47: The style property GtkProgressBar:min-horizontal-bar-height is deprecated and shouldn't be used anymore. It will be removed in a future version
GLib-CRITICAL **: Source ID 340 was not found when attempting to remove it at /usr/libexec/drakconf line 1034.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.22.0/Gtk3.pm line 779.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.22.0/Gtk3.pm line 779.

etc.

So assuming this is another gtk+3.0 surprise and setting this bug to block bug 11778

Assigning to maintainer

CC: (none) => marja11
Blocks: (none) => 11778
Assignee: bugsquad => thierry.vignaud
Source RPM: rpmdrake-6.20-1.mga5.src.rpm => rpmdrake-6.21-1.mga6

Comment 2 Bit Twister 2016-01-02 00:41:56 CET

(In reply to Marja van Waes from comment #1)

> So assuming this is another gtk+3.0 surprise and setting this bug to block
> bug 11778

Well, there are two faces to the gtk problem. All sorts of stuff dinked up if you test an upgrade instead of a clean install.  :(

I also found problems between a clean install with $HOME carried forward into a clean install. No where near the desktop problems on a new Plasma user as seen with a Mageia 5 kde user install on Mageia 6.

In my opinion you might want to tie those/this problem into bug 15527.

Devel/QA/Document teams need to hash out what is to be delivered on that devel 1 iso. One documentation example. The right mouse click on the desktop for a Mageia 5 user under plasma does not match the same keyboard controls for a new Plasma user even though both are basically configured the same way.

Comment 3 Bit Twister 2016-01-10 05:56:37 CET

last round of updates/reboot has fixed the problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED