Is it just me, or is there a reason for it?

[Chris Jones]

> 
> Well, I don't see the point of it.  The user has already had an on-screen
> error message at the time.  All it seems to say is that the user (or
> a program) tried to open a file that evince couldn't open, probably because
> evince isn't designed to open such files. I can't see how useful an audit
> of that could be.

Personally I *much* prefer a persistent message written to a log file, than a pop up box, all record of which is gone once the user has clicked "go away" without reading what it has to say ....