Bugzilla – Bug 169764
VFS support via FUSE
Last modified: 2008-03-26 18:10:04 UTC
Gimp could not edit a file on Windows Share. Step to reproduce ----------------- Open nautilus Open the share (CTRL+L and smb://share) Right click on the picture Open with gimp -> Error can't open file /$HOME/smb:// .... It seems that the gnome-vfs stack has been implemented in the future 2.4 version. See http://developer.gimp.org/NEWS Is it possible to backport this fonctionnality ?
*** This bug has been marked as a duplicate of 67210 ***
This is not really a duplicate; the other bug is about a problem in GtkFileChooser. The GIMP doesn't support arbitrary URIs; I think they have a special mode for HTTP, but that's all. Why is Nautilus listing the GIMP as an option to open a file in a SMB share? Does our .desktop file for the GIMP mention that it can open URIs, and not just local files?
GIMP uses %U. %F can be more appropriate. Could you try to edit your /opt/gnome/share/applications/gimp.desktop and replace Exec=gimp-remote-2.2 %U by Exec=gimp-remote-2.2 %F
using %F produces a similar error : Error can't open file /$HOME/smb:// ....
Than it seems to be a lack of GNOME. Desktop specification says: %f: If files are not on the local file system (i.e. are on HTTP or FTP locations), the files will be copied to the local file system and %f will be expanded to point at the temporary file. Used for programs that do not understand the URL syntax. %F: A list of files. Use for apps that can open several local files at once.
Regarding this bug as well as 169764 and 169754: We need to make sure this is working in the customer environment that Frederic is supporting. Kelli, Pete, Nat and Guy's comment: Not a blocker for RC2.
Talked to Guy earlier this evening. The fix for this is quite torturous upstream and invites too much risk at this late date. We will not fix for FCS. Merry Christmas, JP. In May.
*** Bug 169754 has been marked as a duplicate of this bug. ***
Re-assigning for solving in a general way upstream in the new glib vfs layer.
We are just beginning this, its a large, long term project.
Changing the product to OpenSUSE 10.3, since this depends on upstream work.
Does this mean it will not make it into SLED10 ever? Or are their plans to backport the upstream work for a later SP? How will this be tracked?
*** Bug 264480 has been marked as a duplicate of this bug. ***
This looks fairly likely with gvfs for oS 11.0.
Done for 11.0 and SLED 11.
Changing to component GNOME. Sorry for the spam.