Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
        I am running debian testing (bookworm) amd64
        I updated my system (apt full-upgrade)
        and after reboot VMs were not starting (virt-manager became unusable)

        running:
        virsh -c qemu:///system
Error registering authentication agent:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of
subject (polkit-error-quark, 0)
error: failed to connect to the hypervisor
error: error from service:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4:
Failed to open file “/proc/3755/status”: No such file or directory

       running virt-manager results in virt manager saying that it is not
connected:
       QEMU/KVM - Not Connected, after clicking on it I get this error:
Unable to connect to libvirt qemu:///system.
error from service:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4:
Failed to open file “/proc/5038/status”: No such file or directory

      process 5038 is virt-manager and file /proc/5038/status do exist on my
system
      *pid will of course change if I restart virt-manager


   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Not sure if this is actually libvirt-daemon bug.
     This can also be polkit or dbus bug, but all apps and my kde-plasma-
desktop
     is running without any issues. I just can't start any Virtual Machines.



   * What was the outcome of this action?

   * What outcome did you expect instead?