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 743714 - Trying to "Import X boxes from system broker" fails with "Empty location"
Trying to "Import X boxes from system broker" fails with "Empty location"
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.15.x
Other Linux
: Normal major
: 3.22
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-01-29 21:55 UTC by Adam Williamson
Modified: 2016-03-31 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Williamson 2015-01-29 21:55:45 UTC 
Pretty much as per summary. When I run Boxes on current Fedora Rawhide (22), click "New", and click "Continue", it offers a choice:

"Import 8 boxes from system broker"

When I click it, I see an error(?) message "Empty location" pop down from the top of the window for a bit, then disappear. It has an X I can click to make it disappear faster. Clicking 'Continue' afterwards produces the same message. And...that's it, really. Doesn't help me know what's wrong (if something is wrong), doesn't offer any obvious way forward.
Comment 1 Adam Williamson 2015-01-29 21:58:29 UTC 
If I enter the URL "qemu:///system", it correctly imports the VMs from the system scope.
Comment 2 Zeeshan Ali 2015-02-02 14:55:59 UTC 
(In reply to comment #1)
> If I enter the URL "qemu:///system", it correctly imports the VMs from the
> system scope.

That is not importing anything, just connecting you to system libvirt instance.
Comment 3 Zeeshan Ali 2015-02-02 20:42:45 UTC 
Fixed in master. Also added a testcase for this, which i'll push soon after the fix for bug#732761.

commit: c0aa16e55d58dcd0d87a07db5897d6a6bf79f896
Date:   Mon Feb 2 19:44:56 2015 +0000

    wizard: Skip URI validation for system broker import
    
    We don't have a URI when importing VM from system broker so attempting
    to validate that only leads to import failing with a weird 'Empty
    location' error message.