Comment # 4 on bug 1202796 from Archer Allstars

@Michael Andres

Hi, thanks for your support.

> zypper sends a dbus request asking PackageKit to quit and release the lock ASAP.

Unfortunately. PackageKit won't listen to Zypper at all, no matter how many
times I tell Zypper to stop it. The only way to stop PackageKit is to fire:
sudo systemctl stop packagekit, as explained in the first post.

> OTOH should PK hold the lock only while performing some action. If you are constantly blocked by PK, then something broke. The logs should reveal it.

I don't think PackageKit is broken in my system. Because PackageKit doesn't
block Zypper constantly, as it only hold the lock while performing its action
(after logging in to my user ID). But the problem is, this process takes a very
long time in some instances (sometimes, I experienced 10-30 mins).

It might take this long on Fedora and Ubuntu also, but it's transparent to the
user since DNF and APT work without having PackageKit to stop, or they are able
to stop PackageKit successfully and also be able to restart PackageKit
automatically after finished their operations. From my experiences with DNF and
APT, never once they fail to perform their operation when I asked them to.
Zypper on the other hand, has this issue.