Apache OpenOffice (AOO) Bugzilla – Issue 110720
Aborting when "UI-language cannot be determined" since DEV300_m76
Last modified: 2017-05-20 10:22:08 UTC
Since the changes introduced by CWS native0 to DEV300_m76's desktop/source/app if there are problems with the application trying to determine the prefered language then it aborts with: "The application cannot be started. The user interface language cannot be determined." Aborting in this case is much too heavy, it should simply fall back to any of the installed UI-languages. More often than not it is exactly one, so things are simple. Since the error message is also localized (or is it hardcoded in English?) then this information should be readily available. If not then falling back to just English would be much better than aborting.
Related to Issue 110102?
Yes, issue 110102 is at least very related: When it is known that something is wrong with language detection I suggest a better handling of the situation, in the other issue the configuration entry related to language detection was wrong which it should not be in the first place. @cd: issue 110102 is probably yours as well
I confirmed Issue 110102 because I saw the mentioned error message when I tried to start m76, but I believe this one is closer to the core of my problem. I upgraded from "Ooo-Dev 3.2.1 multilingual version English UI WIN XP: [OOO300m14 (Build 9489)]" with a special detail: I unselected all modules except WRITER during custom installation. I don't know whether that detail is important. The way how and from what situation the update has been done might be the reason for the problem. I uninstalled my damaged m76 and then did a second attempt to install m76 (this time a complete installation) - now it works.
I have this problem again with m80. The previous solution (with bootstrap.ini) does not work amnymore - see issue 110102 for further comments. That one is a P1 for me.
Reproducible with "Ooo-Dev 3.3 multilingual version English UI WIN XP: [DEV300m80 (Build 9507)]. I upgraded from "Ooo-Dev 3.2.1 multilingual version English UI WIN XP: [OOO320m16 (Build 9497)]" with various steps (m78 and m79 did not work for me) and deleting user profile.
*** Issue 112103 has been marked as a duplicate of this issue. ***
cd: I would be nice if anyone can provide a step-by-step description on how to reproduce this issue. I wasn't able to reproduce it on Windows Vista/XP/2000. This would help me to fix this issue as soon as possible. cd: As this issue is severe it must be fixed for OOo 3.3 (set target and state to started/accepted).
Please excuse me, I wanted to write: NOT reproducible with "Ooo-Dev ...
I am installing OOo as always: 1. start OOo installer (dev80 in this case) 2. select Custom install 3. left all settings as is (selected only custom to check that everything is fine, as I do have some unorthodox directories) Everything progresses as expected. [Java v20 was also installed the first time I installed dev80 - it wasn't installed afterward anymore - I hope it is not related to this install.] As mentioned in another issue: App data is on the C drive, while the program is installed on the L drive. If needed, I can send you (in the evening today) various ini files per mail - please specify which ones. Reinstalling did not solve the issue. I did not check if deleting all the previous directories will solve the issue - I only noticed afterward that older directories are still lurking on my computer. I do not have a stable release installed either. Some errors may be related to the fact that I do not have a stable release installed (and therefore NOT reproducible if the stable release is still installed on the computer). I believe this was one issue for the java-errors (I received on previous installs often an error related to java - and I now believe that that error was related to uninstalling the stable release).
I could reproduce it on some Windows machines (both Windows XP). What I did : - had an old installation of OOo (e.g. OOo 3.2.1) with an old configuration (updated for a long time) - I think I had also a language pack installed (german) (but I do not know exactly) - I installed the m80 en-us => the first start results in this error - when I delete my configuration I can start m80 In the configuration files I could find only, that en-us was activated (setup.xcu). But I do not know, if this is updated by the installation of new installation. If it is needed I can send you my configuration files to reproduce this error.
cd: After some investigation there is a strong hint that the start up problem is related to a installed weblog-publisher extension. So could people who can reproduce this problem confirm this?
It's the weblog publisher. This is a duplicate of 162567 (internal oracle issue) which is fixed on jl152. There is an error in the xcu which makes the config manager struggle. I propose to close this issue.
@jl: CWS jl152 changes the weblog publisher to no longer contain invalid .xcu data, but that does not help for users updating to OOo 3.3 with an already installed, old weblog publisher. Hence, I will change the configmgr code to accept and ignore the invalid .xcu data (as did the old pre-DEV300_m74 configmgr code).
.
fixed as <http://hg.services.openoffice.org/cws/jl153/rev/73b410b4d190>
@hi: please verify
@OF: This is more your area. Please take over, Thanks.
OF: What I've done: - I've installed OOO320_m18 - I've installed blogger extension version 1.1.1 (the released on) - I've updated the installation with cws jl153 - Office refuses to start with the given error message.
of: Fix verified in cws jl153.
how was this verified? I still have that error on my m83 + the patch which went into jl153...
Just read: "OF: What I've done: - I've installed OOO320_m18 - I've installed blogger extension version 1.1.1 (the released on) - I've updated the installation with cws jl153 - Office refuses to start with the given error message."
and you really consider "- Office refuses to start with the given error message." the fix? please don't tell me this is true. If you don't, why is this VERIFIED-FIXED then?
You're right. That's rubbish. I've been able to start the office with the given test steps.
Nevermind, my error apparently was caused by our broffice.org packging (which worked in 3.2.1). Need to find out what changed in 3.3 which broke it....
(for the record: empty {UI,Setup}-brand.xcu. They don't exist anymore, and having the empty there seems to break OOo. Of course noone told about such changes).
(@rene, "Of course noone [sic] told about such changes": see <http://www.openoffice.org/servlets/ReadMsg?list=interface-announce&msgNo=1257>)
as if packagers are required to read interface-announce... I'd have expected something like that on an appropriate dev@ list... But OK.. Besides that this mail is too unverbose to know what you need to have to change. But anyways.