Created attachment 83426 [details] DOC - Runtime Error Don't open a document from an attachment
*** Bug 67705 has been marked as a duplicate of this bug. ***
This is a regression in 4.1.0.3; in 4.1.0.2 it worked OK.
triggered by d1fc3fce16172d7d619b6826de44528030ab36f8 fdo#64448: Don't get type name from incorrect filter
I'm afraid that the fix for bug 64448 made more new problems than solved. I would suggest to change that fix not to drop the data from "incorrect filter", but instead to notify user that it is not a filetype that is expected; that the program supposes that this is some other file type; and suggest to try that guessed filter. So, from the end-user perspective, there should be these cases when a file os opening: 1. File is detected unambiguously: simply open it. 1.1. An error happens while loading: instead of uninformative "i/o error", provide a more verbose information with a suggestion that this file is of some other (unrecognized) type. It would be simply awesome if it then would provide an option to send it for analisys, or use some (online) utility to detect etc., but it is a separate feature request. 2. File is detected as one type, but some filter claims that it is its type: try the main filter, catch general i/o error, provide a warning and a choice to try other detected filters. Without this, this is a real problem for quite a number of users that receive such files from others/from some (badly designed) programs. And this is the regression from the UX perspective!
Caolan, could you verify that my fix for Bug 67699 also fixes this? I tested it after my fix, and the RTF file with .doc extension opens fine now.
yup, that fixes this too *** This bug has been marked as a duplicate of bug 67699 ***