Bug 13793

Summary: gnome keyring 32 bits warning during 64bits upgrade from mageia3 to mageia 4
Product: Mageia Reporter: Neo Futur <mageia.org>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Normal CC: mageia.org, sysadmin-bugs
Version: 4Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: p11-kit CVE:
Status comment:

Description Neo Futur 2014-07-23 21:52:15 CEST
Description of problem:

getting hundreds of gnome keyring 32 bits warning during 64bits upgrade from mageia3 to mageia 4 :

p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

gnome-keyring-pkcs11.so is here in usr/lib64 folder, but urpmf wont find any 32 bit version


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


How reproducible:

Steps to Reproduce:
1.network upgrade 64 bits from mageia 3 to magia 4



Reproducible: 

Steps to Reproduce:
Neo Futur 2014-07-23 23:57:18 CEST

CC: (none) => mageia.org

Comment 1 Marja Van Waes 2015-09-21 10:51:31 CEST
Installer and Release bugs should always be set to cauldron, because once the isos for a stable version have been created, they cannot be changed.

This bug was filed very long ago, for Mageia 4. Was this bug still valid for Mageia 5?

(If so, please do _not_ set the version to "5". Only asking because if it was still valid for Mageia 5, that then we'll know we'll have to pay attention to this issue when testing the 6 alpha's and later).

Please close this bug report if the problem was solved in Mageia 5hhhh

Keywords: (none) => NEEDINFO
Version: 4 => Cauldron

Rémi Verschelde 2015-09-21 11:26:18 CEST

Component: Release (media or process) => RPM Packages
Version: Cauldron => 4

Comment 2 Samuel Verschelde 2015-09-21 11:29:26 CEST
Not an installer bug actually.
Comment 3 Samuel Verschelde 2015-09-21 13:19:46 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Marja Van Waes 2015-10-27 06:57:05 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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