GNOME Bugzilla – Bug 723399
Names of gvfs-fuse directories should be more application friendly
Last modified: 2018-09-21 17:38:44 UTC
If configured so, gvfs mounts each accessed resource to ~/.gvfs/NAME (or /run/uid/gvfs/NAME). NAME is derived from the accessed resource, for example: smb-share:server=SERVERNAME,share=SHARENAME Some applications, especially all windows applications running on wine or crossover, cannot access this paths. This is a real big drawback in user experience since it avoids easily opening documents from linux desktop with wine apps. Solution: Only use characters here that are supported on all platforms (at least no colons).
http://support.microsoft.com/kb/177506: Characters that are valid for naming files, folders, or shortcuts include any combination of letters (A-Z) and numbers (0-9), plus the following special characters: ^ Accent circumflex (caret) & Ampersand ' Apostrophe (single quotation mark) @ At sign { Brace left } Brace right [ Bracket opening ] Bracket closing , Comma $ Dollar sign = Equal sign ! Exclamation point - Hyphen # Number sign ( Parenthesis opening ) Parenthesis closing % Percent . Period + Plus ~ Tilde _ Underscore
*** Bug 758564 has been marked as a duplicate of this bug. ***
Fuse mountpoint is based on mount->stable_name. We can't simply change stable_name, because it is used for naming metadata databases. However it might be possible to change only fuse_mountpoint... Alex, is this good idea?
Created attachment 316231 [details] draft
Note that the list of "valid characters" for naming files and folders mentioned in comment 1 is obviously wrong. This list only applies to "system objects which do not follow the same naming convention as files, folders, and shortcuts" as told in the cited KB article. For regular files and folders the only forbidden characters are \ / : * ? " < > | as mentioned in the same KB article.
-- 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/gvfs/issues/224.