Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65832 - [gnome-boxes] Fails to connect socket to libvirt, then segmentation fault
Attached to Project:
Community Packages
Opened by Kostas Kardaras (coxackie) - Saturday, 14 March 2020, 08:09 GMT
Last edited by Balló György (City-busz) - Monday, 16 March 2020, 10:46 GMT
Opened by Kostas Kardaras (coxackie) - Saturday, 14 March 2020, 08:09 GMT
Last edited by Balló György (City-busz) - Monday, 16 March 2020, 10:46 GMT
|
DetailsDescription:
Not sure if upstream bug, but here is part of the log (before crash) when starting gnome-boxes 3.36.0-1: (gnome-boxes:5605): Boxes-WARNING **: 08:05:25.655: libvirt-machine.vala:275: Failed to connection to system libvirt: Unable to open qemu+unix:///system: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory (gnome-boxes:5605): Libvirt.GObject-CRITICAL **: 08:05:29.165: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed Segmentation fault (core dumped) |
This task depends upon
https://gitlab.gnome.org/GNOME/gnome-boxes/issues