Comment # 16 on bug 1202796 from Jonathan Kang

(In reply to Michael Andres from comment #15)
> (In reply to Jonathan Kang from comment #12)
> > What I did at PackageKit side only mitigates this issue. The bug was meant
> > to let zypper stop PackageKit on user request. This is not fixed yet.
> 
> Jonathan, how? Zypper sends     
> > dbus-send --system --dest=org.freedesktop.PackageKit --type=method_call \
> > /org/freedesktop/PackageKitorg.freedesktop.PackageKit.SuggestDaemonQuit
> 
> But this neither stops PK faster nor does it prevent PK from being
> respawned. As Bug 1224475 reports it seems to be impossible to disable PK:
> > # systemctl stop packagekit
> > # systemctl disable packagekit
> > # systemctl status packagekit
> > ○ packagekit.service - PackageKit Daemon
> >      Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
> >      Active: inactive (dead)
> > hobbes:~ (1)# pkcon  search foobaa
> > Searching by details          [=========================]         
> > Starting                      [=========================]         
> > Refreshing software list      [=========================]         
> > Querying                      [=========================]         
> > Finished                      [=========================]         
> > hobbes:~ (0)# systemctl status packagekit
> > ● packagekit.service - PackageKit Daemon
> >      Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
> >      Active: active (running) since Tue 2024-05-21 17:51:27 CEST; 12s ago
> 
> 
> I almost think we can drop all this PK handling from zypper because it's
> useless. From the user's POV it does not matter whether zypper does not stop
> PK or PK does not respond or PK respawns so fast. 
> 
> 
The current implementation of PackageKit's SuggestDaemonQuit isn't as quick as
we expected. It simply waits for the last job to be finished and then quit. It
doesn't ask jobs in queue to cancel so that it quit asap.

So this is definitely a PackageKit issue.