Bug 21111 - Missing pinentry-qt5 after upgrading Mageia5 to Mageia 6
Summary: Missing pinentry-qt5 after upgrading Mageia5 to Mageia 6
Status: RESOLVED DUPLICATE of bug 21222
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2017-06-19 10:14 CEST by Daniel Tartavel
Modified: 2017-08-11 11:52 CEST (History)
2 users (show)

See Also:
Source RPM: pinentry-1.0.0-2.mga6.src.rpm
CVE:
Status comment:


Attachments
report.bug (154.96 KB, application/x-xz)
2017-06-20 08:23 CEST, Daniel Tartavel
Details

Description Daniel Tartavel 2017-06-19 10:14:24 CEST
Description of problem:
After upgrading mageia 5 to Mageia 6 kwalletd don't open password request and display an error because pinentry-qt5 is missing.

Version-Release number of selected component (if applicable):
pinentry-1.0.0-2.mga6.src.rpm

How reproducible:
upgrade Mageia 5 to Mageia 6

How to reproduce:
upgrade Mageia ( to Mageia6
Connect to your account, kwallet display an error and don't ask for password
Marja Van Waes 2017-06-19 16:00:12 CEST

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 1 Marja Van Waes 2017-06-19 16:02:45 CEST
Daniel, could you please attach /root/drakx/report.bug that was created at the time of the upgrade?

Please compress it with xz before attaching to this bug report.

Keywords: (none) => NEEDINFO
Summary: Missing pinentry-qt5 after upgardeing Mageia5 to Mageia 6 => Missing pinentry-qt5 after upgrading Mageia5 to Mageia 6

Comment 2 Daniel Tartavel 2017-06-20 08:23:19 CEST
Created attachment 9431 [details]
report.bug
Comment 3 Nicolas Lécureuil 2017-08-11 11:52:32 CEST
closing as dupplicate, all will be fixed in bug 21222

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
CC: (none) => mageia


Note You need to log in before you can comment on or make changes to this bug.