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 676122 - can't get photos off my phone
can't get photos off my phone
Status: RESOLVED DUPLICATE of bug 586367
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2012-05-15 18:17 UTC by William Jon McCann
Modified: 2013-05-20 07:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (60.73 KB, image/png)
2012-05-15 18:17 UTC, William Jon McCann
Details

Description William Jon McCann 2012-05-15 18:17:36 UTC
Created attachment 214144 [details]
screenshot

I can't seem to access my phone using the file chooser. I can see it with Nautilus.
Comment 1 Bastien Nocera 2012-05-15 18:35:19 UTC
The problem is that instead of showing gvfs mounts if fuse support is installed, we're restricted to using local paths if "local-only" is set to TRUE.

Instead, the filechooser should be checking with the gvfs daemon whether fuse support is available. If it is, show remote mounts too, as they will be accessed through fuse.
Comment 2 Federico Mena Quintero 2012-05-15 22:37:19 UTC
We do a bunch of "if (impl->local_only && g_file_is_native (file))" in the file chooser.  However, I just noticed that the docs for g_file_is_native() say:

 * On some systems non-native files may be available using
 * the native filesystem via a userspace filesystem (FUSE), in
 * these cases this call will return %FALSE, but g_file_get_path()
 * will still return a native path.

So we need to see each of those calls in the file chooser's code, and see which can be replaced by a helper function that does g_file_is_native() and checks for the file actually having a filesystem path.
Comment 3 Bastien Nocera 2012-05-16 10:26:24 UTC
You'll need to replace those by a g_file_get_path() call that wouldn't leak memory (a new g_file_has_path for example), and make sure that URIs you give back to the application go through:
file = g_file_new_for_uri (uri);
path = g_file_get_path (file);
ret = g_filename_to_uri (path, NULL, NULL);

So you give back a URI but in the file:/// scheme.
Comment 4 Timothy Arceri 2013-05-20 07:35:53 UTC

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