Bug 15704 - xdg-open should use gvfs-open if available.
Summary: xdg-open should use gvfs-open if available.
Status: RESOLVED FIXED
Alias: None
Product: Portland
Classification: Unclassified
Component: xdg-utils (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Portland Bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-24 19:56 UTC by Jeff Bailes
Modified: 2010-04-30 04:49 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Simple patch which uses gvfs-open if it exists and gnome-open otherwise (337 bytes, patch)
2008-07-22 09:17 UTC, Dylan Grose
Details | Splinter Review

Description Jeff Bailes 2008-04-24 19:56:49 UTC
Since GNOME 2.22, gvfs-open should be used by default for GNOME instead of gnome-open and only use gnome-open if gvfs-open fails.  Nautilus no-longer passes file association changes to gnome-open which can cause files passed to xdg-open to fail with a no associated program error.
Comment 1 Rex Dieter 2008-04-25 04:33:52 UTC
Is the syntax/usage the same (gvs2-open vs gnome-open)?
Comment 2 Jeff Bailes 2008-04-25 16:42:45 UTC
Yes, same syntax, I just replaced 'gnome-open' with 'gvfs-open' in my xdg-open script and it works fine.
Comment 3 Dylan Grose 2008-07-22 09:17:08 UTC
Created attachment 17823 [details] [review]
Simple patch which uses gvfs-open if it exists and gnome-open otherwise

A trivial change to the open_gnome function which checks for /usr/bin/gvfs-open and uses it if it exists, and gnome-open otherwise. Seems like there should be a better way to do this, i.e. by determining if the gvfs-open executable is somewhere on PATH instead of hardcoding the /usr/bin directory, but my shell scripting ability is low.
Comment 4 Pablo Castellano (pablog) 2010-04-30 04:49:04 UTC
I have checked in the code, and a similar workaround is already applied.
Closing bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.