Ask Your Question
2

Gnome Softare 'remove' button leaves packages behind..

asked 2017-10-16 01:56:48 -0500

horizonbrave gravatar image

Hi, I'm a Fedora 27 user and I tried to install (succesfully) Chromium thorugh Gnome Software GUI. I then uninstall it through Gnome Software GUI using the remove button but it leaves behind chromium-common, chromium-libs and chromium-libs-media so then when updatin with dnf upgrade i get the following:

 Problem: package chromium-libs-61.0.3163.100-1.fc27.x86_64 requires chromium-libs-media(x86-64) >= 61, but none of the providers can be installed
  - package chromium-libs-media-freeworld-59.0.3071.109-5.fc27.x86_64 obsoletes chromium-libs-media provided by chromium-libs-media-61.0.3163.100-1.fc27.x86_64
  - cannot install the best update candidate for package chromium-libs-media-61.0.3163.100-1.fc27.x86_64
  - cannot install the best update candidate for package chromium-libs-61.0.3163.100-1.fc27.x86_64
  - nothing provides chromium-libs(x86-64) = 61.0.3163.79-1.fc27 needed by chromium-libs-media-freeworld-61.0.3163.79-1.fc27.x86_64
================================================================================
 Package                       Arch   Version              Repository      Size
================================================================================
Skipping packages with broken dependencies:
 chromium-libs-media-freeworld x86_64 61.0.3163.79-1.fc27  rpmfusion-free 2.3 M

Transaction Summary
================================================================================
Skip  1 Package

If I try to remove Chromium with dnf remove chromium everything gets removed properly. Please is it a Gnome Software bug or package bug or what? Thanks :)

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted
1

answered 2017-11-19 19:37:28 -0500

horizonbrave gravatar image

from: https://www.ctrl.blog/entry/packageki...

Use DNF rather than PackageKit on Fedora

Last updated: 2017-07-02

Fedora Workstation comes with two package managers by default: DNF and PackageKit. DNF has all the latest features and the best support, but PackageKit is put front and center in GNOME Software, KDE Plasma Discover, and as of Fedora 26 also in Cockpit’s new Software Update panel.

You may be better off sticking with the DNF package manager in the command line; even though PackageKit is the choice of all the graphical package managers. Here is some of the advantages DNF still gives you over PackageKit based applications.

PackageKit is part of the magic that makes GNOME Software Center and KDE Plasma Discovery — the two most widely used “app stores” on Linux — work across different Linux distributions despite each having their own package manager.

The idea behind PackageKit is to provide a cross-platform front-end and API layer for common operations in popular Linux package managers such as APT for Debian and Ubuntu, DNF for Fedora and RHEL, Zypper for openSUSE and SUSE, and Pacman for Arch Linux. Other package managers and distributions are supported as well. That is to say, you can use the same command line interface — or programming API — for interacting with the host operating system’s package manager regardless of the distribution or underlying package manager.

However, PackageKit in Fedora isn’t great. It relies on the still in-development libdnf library which is a fairly new effort to port DNF from Python to C. To quote the library’s own README file:

“Note that libdnf is currently being reworked and is considered unstable. Once major users like PackageKit and DNF are fully ported, a new stable release will be considered.”

In other words: GNOME Software and Plasma Discover, two front-and-center applications for end-users on Fedora Workstation (and the Fedora KDE Plasma Desktop edition), rely on an unfinished work-in-progress library on Fedora. It’s worth noting here that both the Pacman backend for Arch Linux and APT backend for Ubuntu seem to be in a much better shape than the DNF backend in PackageKit.

Problems quickly show up when comparing pkcon and dnf, the command line interfaces of PackageKit and DNF respectively: Advertisement

The command line dnf utility can automatically identify and remove orphaned packages — unused libraries and other packages — when you upgrade or remove software. PackageKit will simply leave the orphaned packages installed and even keep updating them in the future even though the library sits there without any software ever using it.

libdnf and PackageKit don’t yet support downloading delta RPMs. Which results in PackageKit requiring up to three times more network bandwidth and data usage to keep the system up-to-date compared to updating with delta RPMs. (The exact figures depends on the which packages you’ve installed on your system – and how they’re updated.)

Both libdnf and PackageKit ignores the /etc/dnf/dnf.conf configuration file which lets users enable features in DNF such as ... (more)

edit flag offensive delete link more
1

answered 2017-10-16 07:21:40 -0500

masteroman gravatar image

Most likely GNOME Software bug in Fedora.

Does running:

sudo dnf autoremove

Solves those dependencies issues (aka, removes unneeded packages)?

edit flag offensive delete link more

Comments

you're right! Have a look: https://www.ctrl.blog/entry/packageki... Cheers :)

horizonbrave gravatar imagehorizonbrave ( 2017-10-17 08:36:31 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2017-10-16 01:56:48 -0500

Seen: 252 times

Last updated: Nov 19 '17