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 688797 - Should support non-local image selection
Should support non-local image selection
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks: 696727
 
 
Reported: 2012-11-21 11:03 UTC by Bastien Nocera
Modified: 2016-03-31 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Revert "wizard: Confine file chooser dialog to local filesystem" (1.06 KB, patch)
2013-05-08 18:37 UTC, Zeeshan Ali
committed Details | Review
Revert "wizard: Confine file chooser dialog to local filesystem" (1.10 KB, patch)
2014-07-03 11:38 UTC, Zeeshan Ali
none Details | Review

Description Bastien Nocera 2012-11-21 11:03:17 UTC
I have my ISOs on a samba server. gvfs-fuse allows having a local filename for remote SMB shares.
Comment 1 Zeeshan Ali 2012-11-21 14:11:41 UTC
(In reply to comment #0)
> I have my ISOs on a samba server. gvfs-fuse allows having a local filename for
> remote SMB shares.

That *should* work already. What happens when you run `gnome-boxes LOCAL_PATH_TO_ISO`?
Comment 2 Bastien Nocera 2012-11-21 14:16:40 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > I have my ISOs on a samba server. gvfs-fuse allows having a local filename for
> > remote SMB shares.
> 
> That *should* work already. What happens when you run `gnome-boxes
> LOCAL_PATH_TO_ISO`?

Missed the point. The file chooser doesn't show them to me.

(and what happens is that it breaks, see bug 688798)
Comment 3 Alexander Larsson 2013-01-11 10:50:18 UTC
Yeah, we need to disnable the local-only flag in the file selector, and then do all i/o via gio and use GFile instead of pathnames for this to work.
Comment 4 Zeeshan Ali 2013-01-11 14:29:10 UTC
(In reply to comment #3)
> Yeah, we need to disnable the local-only flag in the file selector, and then do
> all i/o via gio and use GFile instead of pathnames for this to work.

How would you tell qemu/libvirt to do that? Or you are thinking of downloading it before install if its non-local?
Comment 5 Alexander Larsson 2013-01-21 08:25:46 UTC
It might be that the fuse based emulation of local files doesn't work well enough for qemu, i guess we'd need to make a copy then.
Comment 6 Zeeshan Ali 2013-05-08 18:37:39 UTC
Created attachment 243610 [details] [review]
Revert "wizard: Confine file chooser dialog to local filesystem"

This reverts commit cd688ab2d4b6bdfbeb8dfe4a6f86391cb8a1c1ce.

Conflicts:
	src/wizard-source.vala
Comment 7 Zeeshan Ali 2013-05-08 18:40:28 UTC
The attached patch should fix at least this bug. Related bug#688798 is a different story.
Comment 8 Christophe Fergeau 2013-05-13 12:08:32 UTC
If things are still broken, better to keep remote files hidden for now. Any idea why you disabled this in the past?
Comment 9 Zeeshan Ali 2013-05-13 13:32:08 UTC
(In reply to comment #8)
> If things are still broken, better to keep remote files hidden for now.

As per comment#0, at least some types of remote files have local paths and apparently confining dialog to local-only hides those as well.

> Any
> idea why you disabled this in the past?

IIRC I didn't know this flag also covers remote filesystems with local paths.
Comment 10 Christophe Fergeau 2013-05-13 15:26:50 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > If things are still broken, better to keep remote files hidden for now.
> 
> As per comment#0, at least some types of remote files have local paths and
> apparently confining dialog to local-only hides those as well.

My understanding of comment #2 and of bug #688798 is that these remote files made available through gvfs-fuse can't be successfully used by Boxes.
Comment 11 Zeeshan Ali 2013-08-23 00:09:49 UTC
With bug#688798, I think this patch makes complete sense.

Attachment 243610 [details] pushed as a84c9ad - Revert "wizard: Confine file chooser dialog to local filesystem"
Comment 12 Zeeshan Ali 2014-07-03 11:38:15 UTC
Created attachment 279833 [details] [review]
Revert "wizard: Confine file chooser dialog to local filesystem"

This reverts commit cd688ab2d4b6bdfbeb8dfe4a6f86391cb8a1c1ce.

Conflicts:
	src/wizard-source.vala
Comment 13 Zeeshan Ali 2014-07-03 11:40:41 UTC
Comment on attachment 279833 [details] [review]
Revert "wizard: Confine file chooser dialog to local filesystem"

Ouch resubmitted the old and wrong patch. :(
Comment 14 Zeeshan Ali 2014-07-03 11:41:17 UTC
commit: f32e682 f32e682583ad695f2edcdec167b2de3173e87815
Author: Zeeshan Ali (Khattak) <zeeshanak@gnome.org>
Date:   Thu Jul 3 12:33:40 2014 +0100

    wizard-source: Allow selecting file from remote shares
    
    This was supposed to be covered by a84c9ad (Revert "wizard: Confine file
    chooser dialog to local filesystem") but what I didn't realize at that
    time was that the underlying Gtk.FileChooser.local_only property is by
    default true and not false. :(
    
    Explicitly setting this property now to enable access to remote shares.
Comment 15 Mikhail 2014-07-03 11:43:04 UTC
(In reply to comment #14)
> commit: f32e682 f32e682583ad695f2edcdec167b2de3173e87815
> Author: Zeeshan Ali (Khattak) <zeeshanak@gnome.org>
> Date:   Thu Jul 3 12:33:40 2014 +0100
> 
>     wizard-source: Allow selecting file from remote shares
> 
>     This was supposed to be covered by a84c9ad (Revert "wizard: Confine file
>     chooser dialog to local filesystem") but what I didn't realize at that
>     time was that the underlying Gtk.FileChooser.local_only property is by
>     default true and not false. :(
> 
>     Explicitly setting this property now to enable access to remote shares.

Same problem with meld
Why local_only property is by default true? :(
Comment 16 Mikhail 2014-07-03 11:44:51 UTC
It's occurs after update to 3.12 GTK
Comment 17 Zeeshan Ali 2014-07-03 12:10:36 UTC
(In reply to comment #16)
> It's occurs after update to 3.12 GTK

That would be question to gtk+ devs.
Comment 18 Zeeshan Ali 2014-07-03 12:23:49 UTC
(In reply to comment #16)
> It's occurs after update to 3.12 GTK

Are you sure about that cause in the gtk+ git history, I see that default value for this property has always been 'TRUE'.
Comment 19 Mikhail 2014-07-03 12:28:51 UTC
Ahhh understand meld 3.10 use GTK 2 and 3.12 use GTK 3 dialog