Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1366909 - gpgconf: Libgcrypt warning: missing initialization - please fix the application
Summary: gpgconf: Libgcrypt warning: missing initialization - please fix the application
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg2
Version: 24
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-14 17:25 UTC by Harald Reindl
Modified: 2016-09-07 01:50 UTC (History)
3 users (show)

Fixed In Version: gnupg2-2.1.13-2.fc24 gnupg2-2.1.13-2.fc25 gnupg2-2.1.13-2.fc23
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 13:52:14 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Harald Reindl 2016-08-14 17:25:25 UTC 
package maintainers should look in their syttempgs (and complain to stuff which floods them like systemd which makes without filters such messages not that obvious than on clean systems)

every single call of yum leads to:
gpgconf: Libgcrypt warning: missing initialization - please fix the application

[root@srv-rhsoft:~]$ which gpgconf
/usr/bin/gpgconf

[root@srv-rhsoft:~]$ rpm -q --file /usr/bin/gpgconf
gnupg2-2.1.13-1.fc24.x86_64
Comment 1 Fedora Update System 2016-08-23 13:11:12 UTC 
gnupg2-2.1.13-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4de7497ac4
Comment 2 Fedora Update System 2016-08-23 13:11:19 UTC 
gnupg2-2.1.13-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9056ffc685
Comment 3 Fedora Update System 2016-08-23 13:11:23 UTC 
gnupg2-2.1.13-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-dd840304be
Comment 4 Fedora Update System 2016-08-23 23:20:54 UTC 
gnupg2-2.1.13-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-dd840304be
Comment 5 Fedora Update System 2016-08-24 17:25:45 UTC 
gnupg2-2.1.13-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9056ffc685
Comment 6 Fedora Update System 2016-08-24 17:53:06 UTC 
gnupg2-2.1.13-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4de7497ac4
Comment 7 Fedora Update System 2016-08-25 13:52:11 UTC 
gnupg2-2.1.13-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Comment 8 Fedora Update System 2016-08-27 10:14:34 UTC 
gnupg2-2.1.13-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2016-09-07 01:50:01 UTC 
gnupg2-2.1.13-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.