Description of problem: network connection state check is disabled Starting yum child process Client is running in rootmode, starting backend directly YUM: Loaded plugins: auto-update-debuginfo, presto WARNING: Yum is locked : Existing lock /var/run/yum.pid: another copy is running as pid 7889. WARNING: The other application is: PackageKit WARNING: Waiting 10 seconds and tries again !!! WARNING: Yum is locked : Existing lock /var/run/yum.pid: another copy is running as pid 7889. WARNING: The other application is: PackageKit WARNING: Waiting 10 seconds and tries again !!! WARNING: Yum is locked : Existing lock /var/run/yum.pid: another copy is running as pid 7889. WARNING: The other application is: PackageKit WARNING: Waiting 10 seconds and tries again !!! Running non-root does not help. Killing mentioned PID does not help. After several minutes it sometimes works again. When I log out it works again after 2-3 minutes. Happens both when I do remote login and in KDE enviroment locally. I wish I could give more info but it would help to know a likely cause to dig for. Version-Release number of selected component (if applicable): yumex-2.9.7-1.fc12 everything else uptodate as of Feb 25. PS I am mostly offline till March 20th
PackageKit is locking the yum API, so yumex can't use it before PackageKit has completted. If you don't use PackageKit for update checking you can use System -> Perferences -> Startup Application find the PackageKit Entry and remove the checkmark or remove it, then packagekit will not get in your way.
thanks for this info. I was not sure if it was indeed safe to remove PackageKit. For the benefit of other users, could yumex display this info when encountering this condition?
In my case there was no Packagekit entry anywhere in System -> Perferences -> Startup Application or /etc/init.d It appears packagekit was started by kde desktop and even after considerable searching I did not find any option to disable it. "rpm -e kpackagekit" did it for me.
just for reference, if KDE desktop is running and kpackagekit installed then it can be disabled using System Settings / Advanced User Settings / Service Management as it may not appear in system-config-services in this case.