This regressed in jammy: # id libvirtdbus uid=120(libvirtdbus) gid=125(libvirtdbus) groups=125(libvirtdbus)
This was supposed to be fixed in https://salsa.debian.org/libvirt-team/libvirt-dbus/-/commit/cd5b637db51de64368723996cc770f323b6c1f53 (and hence the package was synced), but this does not work. This once again completely breaks cockpit-machines. I'll have a closer look, send a fix to Debian, and apply it to jammy. ** Changed in: libvirt-dbus (Ubuntu) Importance: Undecided => High ** Changed in: libvirt-dbus (Ubuntu) Status: Fix Released => Triaged ** Changed in: libvirt-dbus (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Also affects: libvirt (Ubuntu Jammy) Importance: Medium Status: Won't Fix ** Also affects: libvirt-dbus (Ubuntu Jammy) Importance: High Assignee: Martin Pitt (pitti) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1802005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
