Member Avatar for MasterHacker110

I just installed linux fedora 16. When i want to view my software packages in the "Add/Remove software" it doesnt show any packages. it give the following error when i click on the "Package Collection" tab:

The group list was invalid
The group list could not be loaded
Refreshing your cache may help, although this is normally a software error.

that was the error.
I have already cleanes my cache and i did a system update.

How can i fix this so that it shows my packages.

note: i encrypted my disk at the instalation setup.

Thanks...

  • 4 Contributors
  • 4 Replies
  • 652 Views
  • 2 Years Discussion Span
  • Latest Post Latest Post by Yurok

Dani AI

Generated

Short expert note about this error and how it usually gets fixed.

The message shown by the Add/Remove Software (Package collections) UI is emitted by the GNOME PackageKit frontend when it cannot find any YUM package groups to show — in other words, PackageKit asked the package backend for “groups” and none were returned. Common causes are missing group metadata in the repositories (no comps*.xml in repodata), a mirror/local repo that wasn’t mirrored with group metadata, or a transient PackageKit/YUM metadata problem. (mail.gnome.org)

A short diagnosis checklist (commands below are examples to inspect things, not the only options): confirm that YUM can see group data, confirm repositories are enabled and reachable, and confirm each repo’s repodata directory contains a comps*.xml (or equivalent) file. If repos are local copies made from an ISO or via reposync, the group file sometimes isn’t copied; the usual remedy is to supply a comps.xml to createrepo (or mirror with reposync so metadata is downloaded). For upstream docs and examples see the createrepo/manpage and reposync documentation. (manpages.debian.org)

Suggested inspection commands (examples only — adapt paths/repo IDs to the system):

yum grouplist -v
yum repolist
ls /path/to/repo/repodata/*comps*.xml
createrepo -g /path/to/repodata/comps.xml /path/to/repo
reposync --repoid=<repoid> --downloadcomps --download-metadata -p /srv/repos
systemctl restart packagekit
journalctl -u packagekit -n 200

If a local repo lacks comps.xml, running createrepo with the comps file (or mirroring with the metadata options) restores group info so PackageKit can populate “Package collections.” (manpages.debian.org)

Notes of caution and context: ’s metadata/cache refresh and ’s tip to start PackageKit are both reasonable for transient metadata problems; they’re good first steps. ’s remark about the RPM database points out that very rarely an RPMDB corruption can interfere with metadata tools — rebuilding the RPM DB is a last-resort action and should be done only after logs show DB errors. For details on how repos should expose group metadata (and why minimal ISOs or incomplete mirrors sometimes omit it) see the docs linked above. (itstorage.net)

Recommended Answers

All 4 Replies

Member Avatar for rch1231

Hello,

Try this. open a terminal and become the root user (using su or sudo) then execute the following two commands and it should refresh the YUM distribution cache.

yum clean all
yum list

You should get a list of all applications available via YUM and your add remove packages application should now be working.

Member Avatar for MasterHacker110

No that didnt work at all, now what do i do?

Member Avatar for jbennet

Rebuild the rpm database? This is long and dangerous.

Member Avatar for Yurok

run /usr/sbin/packagekitd before

Edited by Yurok
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.