Apache OpenOffice (AOO) Bugzilla – Issue 128094
Error when performing a fresh install with German version
Last modified: 2023-10-03 15:36:21 UTC
Created attachment 86664 [details] Error after fresh install I have encountered an error when performing a fresh install with the German version on Windows 7 64-bit (see attachment). It seems that the error is related to the French dictionary (bundled with the German binary) when the profile is created. After the installation the dictionary is marked as inactive in the Extension Manager with an "unknown state". Same problem with French binaries (and bundled French dictionary)
Beware: On some Windows systems it shows the error box on some AOO dies silently and has to be killed with taskmanager.
Additional note, installing these extensions also result in a hanging AOO: - Oracle Report Builder - AOO PDF Import
While testing Dev-m2 (German) on macOS I experienced the same issue described in comment #1. At the first start AOO hangs after the setup screen. It has to be killed. The next start is successful, however the French dictionary is not registered correctly.
The French dictionary tries to integrate a "Dictionary Switcher" into the AOO menus via a Python script. This is where it possibly hangs.
(In reply to Matthias Seidel from comment #2) > Additional note, installing these extensions also result in a hanging AOO: > > - Oracle Report Builder > - AOO PDF Import Wiki Publisher
(In reply to Matthias Seidel from comment #4) > The French dictionary tries to integrate a "Dictionary Switcher" into the > AOO menus via a Python script. > > This is where it possibly hangs. Previously python.exe could not start due to bug 127731, so with that fixed, maybe this needs re-testing.
python.exe was used by the French dictionary. uno.exe was surely used by the failing extensions. Confirmed FIXED with latest trunk on Windows 10. Fresh install is successful and all extensions can now be installed without problem! Thank you!
(In reply to Matthias Seidel from comment #7) > python.exe was used by the French dictionary. > uno.exe was surely used by the failing extensions. > > Confirmed FIXED with latest trunk on Windows 10. > > Fresh install is successful and all extensions can now be installed without > problem! > > Thank you! That's fantastic news! Thank you for reporting and testing. Since both bugs have a common cause, shouldn't this be resolved duplicate? *** This issue has been marked as a duplicate of issue 127731 ***