This is split out from bug 43945.

There is a general architecture problem described in bug 44932 where the error
message displayed when there's no component available to display a remote file
can't distinguish between the case when there's no component for that file type
in general and the case when there's a component that only works on local files.

This bug report is about that same problem, but specifically for RPM files. We
could consider special-casing the error message for RPM files to explain this
situation, even if we don't fix the general architecture problem in 4932.

To reproduce:
1) Navigate to a vault directory containing an rpm file
2) Double-click on the RPM

Note that the error message doesn't explain that it would work if it were local.
That's what this bug is about.



------- Additional Comments From don@eazel.com 2000-12-15 09:32:09 ----

Batch move all 254 PR3 P5 bugs to 1.0.1.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:48 -------