Bug 21175

Summary:	Installing xscreensaver leads to adding tainted versions to updates
Product:	Mageia	Reporter:	aguador <waterbearer54>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	xscreensaver-5.36-2.mga6.x86_64	CVE:
Status comment:

Description aguador 2017-07-02 13:14:24 CEST

Description of problem:
After installation of xscreensaver on E21 x86_64 system, updating system shows BOTH the the x86_64 and i586 TAINTED versions of xscreensaver as updates.

Version-Release number of selected component (if applicable):
xscreensaver-5.36-2.mga6.x86_64

Steps to Reproduce:
1. Install xscreensaver-5.36-2.mga6.x86_64 (including dependencies: chbg-2.0.1-24.mga6.x86_64, fortune-mod-1.99.4-1.mga6.x86_64, xscreensaver-common-5.36-2.mga6.x86_64)

2. Wait for xscreensaver to activate

I have checked the XFCE Live and see that the open-source version of xscreensaver is the only one installed, so I have no idea why I would be prompted to update to tainted even though I have that source enabled.

(Note: I see that the SRPM includes building the copyrighted "Matrix" shots that do indeed belong in tainted. However, I do NOT have the "Matrix" screens installed.)

(As an aside, on my system there is a momentary Gtk warning at startup: "Unable to locate theme engine in module_path: 'adwaita'". I assume this is unrelated and do not know if it can be fixed/is worth fixing for those of us running other themes, here Vertex-Dark.)

Comment 1 aguador 2017-07-02 13:20:39 CEST

I forgot to note: In rpmdrake xscreensaver-5.36-2.mga6.x86_64 shows as being installed with the two tainted versions as updates. In terminal:

$ urpmq -f xscreensaver
xscreensaver-5.36-2.mga6.x86_64|xscreensaver-5.36-3.mga6.tainted.x86_64

Comment 2 David Walser 2017-07-02 16:53:02 CEST

This means that you have the tainted/release medium enabled.  This is normal behavior.

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