GNOME Bugzilla – Bug 44932
Error message should know that file could be opened if it were local
Last modified: 2008-05-03 15:28:07 UTC
This is split out from bug 43945. If the user tries to open a remote file, and there are no Nautilus components registered to handle that file type for remote uris, but there are Nautilus components to handle that file type for local uris, the user should get an error message explaining this. Instead, the user just gets a generic "can't open this file" message, without the additional clue that it could be opened if it were local. To reproduce: 1) Navigate to a vault directory containing an rpm file 2) Double-click on the RPM You get an error message that does not mention the fact that if the file were copied locally you could view it. This is closely related to bug 44931. This one is specifically about failing to have separate error messages for the "no component at all" case and the "component exists, but can only handle local files" case. The only specific example of this I know about is for RPM files, though the problem is theoretically more general. I will write another bug about the specific RPM case, because we might consider fixing that with a special case even if we don't fix the general architecture problem described here. ------- Additional Comments From sullivan@eazel.com 2000-12-01 14:20:13 ---- Note that if we fix this one, 4931 and 4932 become moot, and don't need to be fixed independently. This one is probably pretty hard to fix. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:48 -------
Changing to "old" target milestone for all bugs laying around with no milestone set.
I was able to open a remote text-file with the viewer-component. I could even open it in gedit. I am not sure how to test a component that needs the file locally, since I am not aware of such component. I tested with version 2.1.2 I will confirm the bug however, so a maintainer looks at it.
*** Bug 109133 has been marked as a duplicate of this bug. ***
Still an issue, bumping Version fields.
But isn't this a problem for each external app now? I mean if file-roller handles opening external files this would work for archives, but if not, it would be a bug in file-roller, not nautilus?
right, the opening is an application bug. I think that the bug purpose is to explain to user than the application doesn't handle that and than they can copy the file on their box to open it.
I think it would be quiet nice if the dialog contained additional info like "if this file was local, the following viewers would be capable of viewing it"
Mass changing Nautilus version for bugs that have GNOME 2.13 version info.
I'm going to go ahead and close this as obsolete; we've gone through GnomeVFS (which should have fixed it) and now have GIO/GVFS (which definitely does fix it). Applications that currently don't work with remote URIs should have their own bugs for this.