Red Hat Bugzilla – Bug 73256
up2date crashed with rpm error due to lack of GPG key on kernel
Last modified: 2015-01-07 19:00:08 EST
Description of Problem:
When I ran up2date and told it to grab the new kernel, I got a dialog indicating
that the package was not signed and asking whether I should continue. I clicked
"OK" and up2date crashed issuing an error message about an rpm error.
Sadly, I do not have the exact details anymore, and can no longer reproduce the
problem, so the above is the best I can do as far as specific details or error
messages. But see below for some additional information.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install (null) from scratch
2. manually update to the following by downloading and installing:
3. run up2date
observe behavior described in "Problem Description"; i.e., up2date crashes after
OK is selected on warning dialog about unsigned package
It should have continued downloading
I worked around this by turning off use of GPG. Now my system is up to date, so
I can no longer reproduce the problem.
I think this was a combo of a weird rpm bug, a glibc bug, and
up2date not handling the exception it got.
It seems to work fine with current code bases of rpm/up2date
(slightly newer versions of up2date/rpm than you list)
2.9.64 for up2date and I belive rpm-4.1-1.04
I'm setting this to modified since it seems to work
for me in the current code base, and sounds like a
bug thats known fixed.
This does seem to be fixed.... any reason why it's still open?
Closing out based on feedback from the original poster.