From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Description of problem: When trying to insert and index in to a writer document by following the Insert -> Indexes and Tables -> Indexes and Tables, I get the below error message. The file "internal/idxexample.sdw" in the "file:///usr/lib/ooo-1.1/share/template/english_uk;file:///home/douglas.furlong/.rhopenoffice1.1/user/template" path could not be found. Version-Release number of selected component (if applicable): openoffice.org-1.1.1-4 How reproducible: Always Steps to Reproduce: 1. Attempt to insert an index/table in to a writer document Actual Results: The following error message appears. The file "internal/idxexample.sdw" in the "file:///usr/lib/ooo-1.1/share/template/english_uk;file:///home/douglas.furlong/.rhopenoffice1.1/user/template" path could not be found I then hit OK, and things appear to progress normally (but I don't know how it "should" look). Expected Results: For then index/template window to appear with out an error message. Additional info:
Odd, I just changed my language settings to English UK (and verified in English US too) that it does work for me. Was this upgraded from Fedora Core 1 or an older release? Can you make sure that /usr/lib/ooo-1.1/share/template/english/ exists (more importantly, /usr/lib/ooo-1.1/share/template/english/internal/idxexample.sxw too)? rpm -q --whatprovides /usr/lib/ooo-1.1/share/template/english/internal/idxexample.sxw openoffice.org-1.1.1-4 Notice you're looking in "english_uk" rather than just "english", not sure if $LANG settings have anything to do with it.
I can reproduce, it seems there is no fallback to english for these types of templates if they aren't installed...
*** Bug 124085 has been marked as a duplicate of this bug. ***
*** Bug 111248 has been marked as a duplicate of this bug. ***
Is any thing being done with this error. I am still finding the problem with openoffice.org 1.1.2-10, the latest release with FC3. Can I provide any assistance in resolving this issue, as far as testing is concerned.
Yeah, should be able to fix this for 1.1.2-11
Seems to work in 1.1.2-11
Seems to work for me as well.