Description of problem: The file history part of the "File" menu of gnumeric shows ODT files, even though these ODT files cannot be opened by gnumeric. Version-Release number of selected component (if applicable): 1.10.10. How reproducible: Every time Steps to Reproduce: Go to open office. Open a few ODT files. Go to gnumeric. Click on "File". Look at the list of recently opened files. You'll see the ODT files there, in the other they were most recently used in open office. Expected results: Since the ODT files cannot be opened by gnumeric, they should not appear in the file history list at all. Additional info:
http://projects.gnome.org/gnumeric/doc/sect-file-open-formats.shtml It says these files can be opened.
Created attachment 460946 [details] screenshot of file menu in gnumeric showing file history with two odt files.
Well, then I've got another bug to report I guess. I'm attaching two screenshots; one is of the "file" menu in gnumeric, the second is the error message I get when I click on the second entry (middle-oscar.odt).
Created attachment 460948 [details] error message after trying to open "middle-oscar.odt" in gnumeric from the file history menu.
gnome-chemistry-utils-0.12.5-2.fc13,gnumeric-1.10.12-1.fc13,goffice-0.8.12-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gnome-chemistry-utils-0.12.5-2.fc13,gnumeric-1.10.12-1.fc13,goffice-0.8.12-1.fc13
goffice-0.8.12-1.fc14,gnome-chemistry-utils-0.12.5-2.fc14,gnumeric-1.10.12-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/goffice-0.8.12-1.fc14,gnome-chemistry-utils-0.12.5-2.fc14,gnumeric-1.10.12-1.fc14
gnome-chemistry-utils-0.12.5-2.fc14, gnumeric-1.10.12-1.fc14, goffice-0.8.12-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
goffice-0.8.12-1.fc13, gnome-chemistry-utils-0.12.5-2.fc13, gnumeric-1.10.12-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.