Invalid Fedora Updates?


Recommended Posts

I have been having problems with up2date posting errors when retreiving updates from the Fedora site. It identifies the available updates, and when I select them and start the process, I get several that error on me, and pop up a window stating that the signature doesn't match and the file may have been tampered with.

Any other Fedora users having this happen?

It messed up on me over the weekend, and up2date would not finish. I left it over night, but it still was stuck with no response to the GUI. I killed the process, and upon reboot, it failed to start x. I tried rebooting to the original kernel (I have updated my kernel several times since original install, and had no problems there), but that did not help. I put a new drive in as my boot drive (hda), and moved the original drive to the slave drive on my secondary IDE (to use as backup and to restore from). I fresh installed from CDs onto the new drive, but still get this problem with up2date not working.

(on the postitive side, restoring a Linux system is super easy! This is the first 'disaster recovery' I have had to do in Linux, and having the config files so easy to locate and manage is much nicer than fighting the Windows registry!)

Link to comment
Share on other sites

sounds like somebody tampered with the repository files. When it downloads them it does checks to make sure the files are proper, and obviously the checks failed as you said it gave the errors.

Link to comment
Share on other sites

sounds like somebody tampered with the repository files. When it downloads them it does checks to make sure the files are proper, and obviously the checks failed as you said it gave the errors.

That's what I thought at first. However, I find it hard to beleive that it would be this way for a week! :o

When I get back home, I will investigate more and get the exact files and fault messages, and send them an email. I really expected my fresh install to work. (I also need to confirm that the same file(s) have the problem and other ones do not - to eliminate a bad download).

Link to comment
Share on other sites

well, the potential is also that your hard drive is dying. You could be getting i/o errors and not realising it.

Run cfdisk and check it (takes a long time though...painful process but accurate). If you get errors then your disk is dying...if you get LOTS of errors (I was hitting the Y key for 6 hours straight once) then your drive is shot...nothing bad happens if you exit cfdisk though, so feel free to if you get too many errors.

Link to comment
Share on other sites

I have always have had problems with up2date, instead I just use yum with a modded host file, not only do the updates download hell of a lot faster they work =)

Link to comment
Share on other sites

I have always have had problems with up2date, instead I just use yum with a modded host file, not only do the updates download hell of a lot faster they work =)

What do you mean modded host file? Pointing to a different repository? Could you share this, and maybe I can see if one source is different than the other?

Also, I will double-check my hard drives. It is strange, but not impossible, to have two go with similar problems (only when trying up2date). I have 3 installed, and a fourth on a shelf, I should not have a problem replacing a defective drive. ;)

Link to comment
Share on other sites

Hey, Timko!

Thanks for the great resources! I will try the alternate yum repository tonight, if I am not too tired (it is 4am here). Lots of good info for me to digest. :yes:

Link to comment
Share on other sites

Hey, Timko!

Thanks for the great resources!  I will try the alternate yum repository tonight, if I am not too tired (it is 4am here).  Lots of good info for me to digest. :yes:

Using an alternate Yum repos isn't necessarily the solution to your problem (plus Up2Date and Yum are two totally different ways of getting stuff: Up2date does NOT use yum.conf).

You need to import the appropriate GPG-Keys for sites before you can pull stuff down from them. Run this lot as root...

rpm --import http://www.fedora.us/FEDORA-GPG-KEY
rpm --import http://rpm.livna.org/RPM-LIVNA-GPG-KEY
rpm --import http://freshrpms.net/packages/RPM-GPG-KEY.txt
rpm --import http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt
rpm --import http://atrpms.physik.fu-berlin.de/RPM-GPG-KEY.atrpms
rpm --import http://newrpms.sunsite.dk/gpg-pubkey-newrpms.txt
rpm --import http://www.jpackage.org/jpackage.asc

Link to comment
Share on other sites

I've never actually had up2date succeed (but this has been common for me ever since up2date was created - back in the day), so I remove it. Instead, I use yum (used apt until about a week ago) to keep updated now.

Since I don't want to break out of the Fedora mold with odd-ball repositories (I'll install the oddball things myself), I stick to the Fedora Core offical servers, Fedora.us, and Livna.org servers.

You can configure up2date to use a yum repository by:

If you really want to use up2date, look at this yum.conf  and edit your /etc/sysconfig/rhn/sources file to use one the mirrors that are used in the yum.conf. (The sources file itself explains how edits work.)

Don't know how well it works, but if you still want to use up2date, but also want updates to things that aren't included (ie. mp3 support), stick to the Livna.org servers. Think of Livna being an offical site, but like the Non-Free repository for Debian.

I use the yum.conf mentioned above, and have the gpgcheck=1 sections uncommented for the default servers. Used with timko's above recommendation for getting the GPGKeys installed, it works very well.

I'll finish blabbering now. Hope all the stuff in this thread helps and leads to the solution! :)

Link to comment
Share on other sites

Hey, thanks for all the pointers, guys! :D

I have not had time to use my computer over the past few days (working long hours), but have the next few days off. Should be able to get some "tinker time" in then... :yes:

Link to comment
Share on other sites

Just an update to the problem.

I have used yum update and updated everything, and WHAM! I could not boot properly into runlevel 5. (selecting init 3 is fine)

When I select the old kernel, it will boot up and start X fine.

I booted again with the new kernel, and viewed the error logs generated, and it appears that X is having problems with the nVidia selection in my XF86Config.

Could this be that I need to re-install the driver I downloaded from nVidia? Did it get lost/deselected during the update?

Link to comment
Share on other sites

If you used the fedora.artoo.net yum.conf there's a nvidia rpm in livna.org. Use it and you'd be quite safe.

http://fedora.artoo.net/faq/#nVidia

A very good place to look at.

A quick one, I install a icon set through the theme manager at the icons section but somehow the icons unzippped into /.theme instead of /.icon. Anyone has any idea what's wrong? By moving the icons form .theme to .icon works and shows up in the theme manager. Running Fedora Core 1.

Edited by Alvin
Link to comment
Share on other sites

From the FAQ link:

If you update your kernel, make sure that you install the newest nVidia driver before  you start the new kernel.
:pinch:

Now, why wouldn't yum have flagged this?

I think I will try to fix this at a later date... :crazy:

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.