Another app is currently holding the yum lock; waiting for it to exit

I'm trying to install wireshark on Fedora(latest version with gnome3) and I keep getting the error.

Another app is currently holding the yum lock; waiting for it to exit...

I keep killing the offending process after finding it's pid using ps aux | grep yum, but the same process spawns again with a different pid.

root      1605  0.0  3.4  54424 26228 ?   SN   10:51   0:02 /usr/bin/python     
/usr/share/PackageKit/helpers/yum/yumBackend.py get-updates none

How can I properly kill this process, or use yum to install wireshark properly?


That is PackageKit attempting to update the yum database so that it can show you a desktop icon when there are updates to apply.

It should only run for short periods - if it is failing to complete then it suggests there is some sort of problem with your yum configuration such that it is hanging trying to update the status of one of the repositories or something.


If you really don't like PackageKit, you can remove it by running the following command as root:

 yum remove PackageKit

You can also disable PackageKit from checking for updates by running gpk-prefs from the terminal:

 gpk-prefs &disown

In the preferences window, change Check for updates to never.


Stop the daemon of packagekit with:

service packagekitd stop

I don't remember if the name is "packagekitd". I also don't remember if in the last versions of fedora PK is a daemon or only a user process.

If you want disable the process check the command "ntsysv" as root in a terminal and the autostart applications in your desktop preferences.

For your problem with the internet connection and the download of packages, check the plugin fastestmirror for yum. The configuration is very simple. Also use the presto plugin.


I found a way to correct this problem.

You can turn off the system auto update, and can resolve it.

In China, I tested it this way and it works well.


There is a very simple solution to this problem.

The "PackageKit" process will only start if your computer is idle. With this in mind we should just log out of Linux and log back in. We should, then, immediately open a terminal window and run yum before the system can go idle.

That's it!