After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736342 - All boxes disappeared after update
All boxes disappeared after update
Status: RESOLVED NOTGNOME
Product: gnome-boxes
Classification: Applications
Component: general
3.12.x
Other Linux
: Normal normal
: 3.22
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-09-09 17:20 UTC by Daniel Korostil
Modified: 2016-03-31 13:22 UTC
See Also:
GNOME target: ---
GNOME version: 3.11/3.12


Description Daniel Korostil 2014-09-09 17:20:54 UTC 
I've updated gnome-boxes to 3.12.3 version and all my boxes suddenly disappeared. Also I can't create a new box.

Startup output: 
(gnome-boxes:13745): Boxes-WARNING **: libvirt-broker.vala:90: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory

Box creating output:
(gnome-boxes:13745): Boxes-WARNING **: wizard.vala:403: Failed to create storage pool: invalid connection pointer in virStoragePoolDefineXML

OS: Archlinux_x64

Any ideas why or where I should dig it out?
Comment 1 Zeeshan Ali 2014-09-09 18:52:40 UTC 
(In reply to comment #0)
> I've updated gnome-boxes to 3.12.3 version and all my boxes suddenly
> disappeared. Also I can't create a new box.
> 
> Startup output: 
> (gnome-boxes:13745): Boxes-WARNING **: libvirt-broker.vala:90: Unable to open
> qemu+unix:///session: Failed to connect socket to
> '/run/user/1000/libvirt/libvirt-sock': No such file or directory
> 
> Box creating output:
> (gnome-boxes:13745): Boxes-WARNING **: wizard.vala:403: Failed to create
> storage pool: invalid connection pointer in virStoragePoolDefineXML
> 
> OS: Archlinux_x64
> 
> Any ideas why or where I should dig it out?

Well all I can say is that most likely your libvirt (installation) is broken.
Comment 2 Daniel Korostil 2014-09-09 22:48:54 UTC 
It seems to be true. 

Libvirt: 1.2.8-1

LANG=C virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory

After downgrade to libvirt-1.2.6-3 it works.

Let me file a bug downstream. Thank you to point it out.
Comment 3 Christophe Fergeau 2014-09-10 08:26:43 UTC 
Known bug in libvirt 1.2.8. You can manually create the /run/user/1000/libvirt/ directory as a workaround, or downgrade.
Comment 4 Daniel Korostil 2014-09-10 22:19:19 UTC 
Probably we need some UX logic to point users about broken backends to disturb you, gnome-boxes developers, less.