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 746766 - Import of imageless boxes from system broker fails
Import of imageless boxes from system broker fails
Status: RESOLVED DUPLICATE of bug 736097
Product: gnome-boxes
Classification: Applications
Component: general
3.15.x
Other Linux
: Normal normal
: 3.22
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-03-25 17:53 UTC by Chris Murphy
Modified: 2016-03-31 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chris Murphy 2015-03-25 17:53:33 UTC 
gnome-boxes-3.15.92-1.fc22.x86_64


1. Click New > Import 2 boxes from system broker >
## a message appears "Will import 2 boxes from system broker"
2. Click Create


Actual result:

The dialog with "Create" vanishes, and I'm back at the main Boxes window, with no boxes created, just the intro graphic and "State of the art virtualization" title.

Expected result:

Two boxes to be created? I'm not actually clear on the language, what system broker means, or why it thinks there are two of them somewhere.


Additional info:

journalctl -f reports the following for the non-root logged in user:

Mar 25 11:49:17 f22m.localdomain firefox.desktop[6960]: 1427305757181        addons.update-checker        WARN        Update manifest for {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
Mar 25 11:49:47 f22m.localdomain org.gnome.Boxes[1797]: (gnome-boxes:6567): Boxes-WARNING **: libvirt-system-importer.vala:74: Failed to make all libvirt system disks readable: Error when getting information for file '/var/lib/libvirt/images/fedora21.qcow2': No such file or directory
Comment 1 Zeeshan Ali 2015-03-25 18:20:07 UTC 
You have two VMs on your system (privileged & shared that you likely created using virt-manager) and since Boxes discourages the use of that, instead of connecting to those VMs, Boxes allows you to import them to private (unprivileged) session libvirt instance.

Seems you have managed to delete the storage of at least one of those VMs while retaining the VM itself. While this is certainly not supported scenario, Boxes should notify of the failure.
Comment 2 Zeeshan Ali 2015-08-06 13:50:45 UTC 

*** This bug has been marked as a duplicate of bug 736097 ***