English
Ask Your Question
1

Error while upgrading from Fedora 25 to 26 using System Update message

asked 2017-11-13 09:50:23 +0000

Kashifbsi gravatar image

Hi,

If anyone could help on the error below, then it would be great. Currently I am using Fedora 25 where I had to fight my way for display to work, and the mouse touch pad was also disabled and I had to use an external mouse for it. Now I wanted to upgrade it to Fedora 26, hoping the out-standing issue with the touch pad would go away. So When I click on the Fedora 26 Now available System message and try to upgrade, I receive this error: Detailed errors from the package manager follow:

package python2-pip-9.0.1-9.fc26.noarch cannot be verified and repo fedora is GPG enabled: failed to lookup digest in keyring for /var/cache/PackageKit/26/metadata/fedora/packages/python2-pip-9.0.1-9.fc26.noarch.rpm

Thanks in advance for your time and help.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2017-11-14 07:25:49 +0000

masteroman gravatar image

updated 2017-11-14 14:58:05 +0000

genodeftest gravatar image

Have you tried performing DNF system upgrade? Procedure is outlined on the following website:

Please note that it is recommended to update system to the latest set of packages before proceeding. I would do the following:

sudo dnf clean all
sudo dnf clean metadata
sudo dnf  upgrade --refresh

and then proceed with system upgrade procedure after installing all of the available updates.

edit flag offensive delete link more

Comments

thank you for your help. I managed to upgrade but now I have different issues and it won't boot saying something like: Couldn't get size Couldn't get UEFIDBlist Couldn't get size: ox.... Bluetooth:hc10: Failed to send Firmware data (-38) stopping user manager for uid 42... I had similar issues when I was on 25 may be some of my hardware is not supported by default. I remember downloading some wifi drivers or files someone recommended at some forum. May be I'll have to do that all again....errrrrr

Kashifbsi ( 2017-11-14 16:05:36 +0000 )edit

You are running into this bug, but it is harmless. "Failed to send Firmware data" sounds like a different bug but it should not prevent you from getting to a login screen. "stopping user manager for uid 42" sounds like GDM crashed. Can you please go to a console and get some logs? dmesg and journalctl -b should help.

genodeftest ( 2017-11-14 16:13:34 +0000 )edit

I have a number of boot options, a mix bag of fedora 25, fedora 26, windows, fedora 25 rescue, not that I wanted those but somehow I have ended up with all of those. Now I can only get onto the console while using the rescue Fedora option, and the output of journalctl -b is sadly so small, that it is very difficult to exactly share. However I managed to gather few of the red lines saying: Unknown Chipset Can't open initialName conf file: /etc/iscsi/initiatorName.iscsi Can't open initiatorAlias Conf file: /etc/iscsi/initiatorName.iscsi Can't open ISCSID.safe-logout configuration file: /etc/iscs

Kashifbsi ( 2017-11-14 18:12:19 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Stats

Asked: 2017-11-13 09:50:23 +0000

Seen: 37 times

Last updated: Nov 14