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 747857 - no feedback when using a remote url
no feedback when using a remote url
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: wizard
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
: 747858 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-04-14 14:43 UTC by Matthias Clasen
Modified: 2018-01-11 10:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2015-04-14 14:43:34 UTC
I entered a remote url, and clicked create. I ended up in the overview with no indication that anything is happening, or that anything has gone wrong. Of course, no vm appeared :-(


The logs have some errors that would be nice to be informed about:

Apr 14 10:02:56 localhost.localdomain org.gnome.Boxes[1985]: (gnome-boxes:15273): Boxes-WARNING **: wizard.vala:451: source is not remote machine: qemu+ssh://mclasen@desktop-v
Apr 14 10:03:26 localhost.localdomain org.gnome.Boxes[1985]: (gnome-boxes:15273): Boxes-WARNING **: wizard.vala:451: source is not remote machine: qemu+ssh://desktop-virthost1
Apr 14 10:03:30 localhost.localdomain org.gnome.Boxes[1985]: (gnome-boxes:15273): Boxes-WARNING **: libvirt-broker.vala:104: Unable to open qemu+ssh://desktop-virthost1.lab.bo

A spinner would also be nice to indicate that something is still happening.
Comment 1 Zeeshan Ali 2015-04-15 11:18:14 UTC
Hmm.. yeah I think we should connect to remote source as part of "preparation" step of wizard so that you get a spinner and also an error if connection fails. Moreover, if first time connection fails, we should ensure the source added is properly cleaned-up.
Comment 2 Zeeshan Ali 2015-04-15 11:19:25 UTC
(In reply to Zeeshan Ali (Khattak) from comment #1)
> Hmm.. yeah I think we should connect to remote source as part of
> "preparation" step of wizard so that you get a spinner and also an error if
> connection fails. Moreover, if first time connection fails, we should ensure
> the source added is properly cleaned-up.

Ah i see that you filed a separate bug for the latter already: bug#747858.
Comment 3 Zeeshan Ali 2015-05-21 22:58:33 UTC
*** Bug 747858 has been marked as a duplicate of this bug. ***
Comment 4 Zeeshan Ali 2015-05-21 23:00:01 UTC
(In reply to Zeeshan Ali (Khattak) from comment #3)
> *** Bug 747858 has been marked as a duplicate of this bug. ***

To ensure I remember while fixing this, pasting the comment from bug#747858: "Actually I think this will automatically be resolved when we fix bug#747857 by moving the first time connection to 'preparation' page on wizard."
Comment 5 GNOME Infrastructure Team 2018-01-11 10:15:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/48.