After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 541695 - Evince has unclear error message when opening non-existent files
Evince has unclear error message when opening non-existent files
Status: RESOLVED DUPLICATE of bug 529129
Product: evince
Classification: Core
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-05 18:33 UTC by gwern
Modified: 2008-07-08 22:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gwern 2008-07-05 18:33:56 UTC
$ evince foo

Evince opens up, and immediately errors out (foo is not a actual file, of course). The error, however, is "Unable to open document" "Unknown MIME type".

This is bad from a usability standpoint for several reasons. For starters, who knows what a MIME type is in the first place - why is it being mentioned? For anyone who doesn't already know the problem, this sounds for all the world like the file is corrupt or 'bad'. Because if there is no file but we can still speak of not opening it, then we start getting into Zen territory: "What is the MIME type of one hand clapping?" "Does this dog have the read-write nature?" "What was your file size before you were born?" "This day 15 years from now - open that document!"

Basically, if there is no file there, it should say "Hey, bub, there's no file by that name." Not this.

Other information:
Comment 1 Nickolay V. Shmyrev 2008-07-05 18:40:40 UTC
What version are you talking about? In trunk it says "no such file" as requested.
Comment 2 gwern 2008-07-05 23:12:42 UTC
gwern@craft:12528~>evince --version                                                         [ 7:12PM]
GNOME evince 2.22.2
Comment 3 Nickolay V. Shmyrev 2008-07-08 22:22:50 UTC
Ah, sorry, this one was recently fixed in development version.


Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 529129 ***