Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Installed F12 a few weeks ago. Everything was working fine. Then I wanted to install perl-cpan, so when I run "yum install perl-cpan", or "yum update", it hangs on "Loaded plugins: presto, refresh-packagekit".
I've let it hang there for hours, nothing ever happens.
For the first week or so, Yum worked fine, I could manually update as I've done on other Fedora versions without any issue.
In the Gnome gui I have automatic updating disabled. As far as I can tell, yum-updatesd isn't running and isn't enabled. I wanted to update things manually for a while until I got this new box "settled in".
I know I can install cpan via other methods, but this strange behavior with Yum has me worried.
If you are wondering what it does:
clean Is used to clean up various things which accumulate in the yum cache directory
over time. More complete details can be found in the Clean Options section
The following are the ways which you can invoke yum in clean mode. Note that "all
files" in the commands below means "all files in currently enabled repositories". If
you want to also clean any (temporarily) disabled repositories you need to use
yum clean expire-cache
Eliminate the local data saying when the metadata and mirrorlists were down-
loaded for each repo. This means yum will revalidate the cache for each repo.
next time it is used. However if the cache is still valid, nothing significant
yum clean packages
Eliminate any cached packages from the system. Note that packages are not
automatically deleted after they are downloaded.
yum clean headers
Eliminate all of the header files which yum uses for dependency resolution.
yum clean metadata
Eliminate all of the files which yum uses to determine the remote availability
of packages. Using this option will force yum to download all the metadata the
next time it is run.
yum clean dbcache
Eliminate the sqlite cache used for faster access to metadata. Using this
option will force yum to recreate the cache the next time it is run.
yum clean all
Runs yum clean packages and yum clean headers, yum clean metadata and yum clean
dbcache as above.
Have you tried the package-cleanup command? Look at man package-cleanup for a description of the various options. One usually starts with package-cleanup --problems to see if they're any problems, and then proceeds from there.
Note that package-cleanup is a script that uses yum so it may "hang" as well. If it's running, your disk access monitor (usually a light) should show disk activity.
If that doesn't help, download the smart package manager (by hand) from a Fedora repository and use rpm to install it. (You'll probably want to install Packagekit-smart, smart, smart-gui, and smart-update. The smart package manager is a Python program, so you'll need Python installed - which is a default installation, so that should be no problem.) Also get the fedora-package-config-smart rpm file to set up the Fedora repository access.
One nice thing about the smart program is that it does its own unpacking, so you can use it when yum is completely non-functional for some reason. I keep a copy installed just to have an alternative to yum available.
Note, however, that the default Fedora setup ignores mirror sites, so downloads are all from the central Red Hat repositories, which are often slow. If the smart developers could automate mirror site identification and usage, smart would be my choice for a "universal" package manager. (It does support all of the "major" package formats now, but its rpm package support is less developed than other formats.)
Second, the "timeout" error usually happens when you're trying to access a repository whilst that repository is being "refreshed" or "updated" from the master site. (Usually, Fedora posts changes to its repositories on Tuesdays and Saturdays, but that's a "usually," not an "always," and other repositories are not so regular.) Have you tried again? Repository updates can take several hours.
Well, have you turned off the automatic update (PackageKit) settings? Fedora uses YUM to run its automatic updates, and, of course, only one YUM instance can be run at one time. so, if you've got the "PackageKit" setting to "Check for updates," any YUM you start will "hang" until the "PackageKit" YUM process finishes and releases the YUM lock.
Note: I manage the PackageKit settings via the KDE interface (KPackageKit). I think that GNOME has a similar app, perhaps just a left-click on the icon in the task bar.
Last edited by PTrenholme; 01-25-2010 at 04:48 PM.