Public bug report changed: https://launchpad.net/malone/bugs/34594
Comment: Nautilus displays that the RTF (rich text format) file from the Ubuntu example-content directory is associated with abiword when viewing the file properties via an SMB network share however nautilus displays an error message when the file is double-clicked unless the file is copied locally. When local it opens perfectly in abiword. Nautilus displays that the SPX (speex) file from the Ubuntu example- content directory is not associated with any applications when viewing the file properties via an SMB network share and nautilus displays an error message when the file is double-clicked unless the file is copied locally. When the file is local, nautilus displays that the file is associated with beep-media-player, easytag, mplayer, totem, rhythmbox, xmms, and gxine with totem set as the default. When local it opens perfectly in totem. Nautilus displays that the XCF file from the Ubuntu example-content directory is associated with gimp when viewing the file properties via an SMB network share. Gimp starts when it is double-clicked however gimp displays an error message. I suspect that this is a separate bug with gimp and VFS. Nautilus displays that a WMA (windows media audio) file is not associated with any applications when viewing the file properties via an SMB network share and Nautilus displays an error message when the file is double-clicked unless the file is copied locally. When the file is local, Nautilus displays that the file is associated with gxine, totem, and mplayer with totem set as the default. When local the file opens perfectly with totem. Nautilus displays that a desktop.ini (Windows configuration) file is not associated with any applications when viewing the file properties via an SMB network share and nautilus displays an error message when the file is double-clicked unless the file is copied locally. When the file is local, Nautilus displays that the file is associted with abiword and gedit with gedit set as the default. When local the file opens as expected. I'm sure that GNOME developers have their reasons for the current implementation but it sure would be nice if VFS worked as a transparent backend that automatically copies files somewhere locally (e.g. /tmp or ~/Desktop) and would therefore allow any application to open a file on a network share whether the application is VFS-aware or not. Or maybe a better solution would be for GNOME to automatically mount network shares so that they can be accessed by any program like any other filesystem. In any case, files should open consistently for the user regardless of whether they are local or not. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
