Apache OpenOffice (AOO) Bugzilla – Issue 66389
Tools/Customize (Draw/Impress) has .uno... strings
Last modified: 2013-08-07 15:31:14 UTC
Automated test: framework\level1\f_lvl1.tools.bas::tToolsCustomizeKeyboardFunction Windows 2003 Terminal Server / User installation on so-win For draw and Impress many entries on the Tools/Customize/Keyboard tabpage do not have their correct names but those of the underlying UNO slot/function. E.g. Key = F1, Category = Application, Function = .uno:PackAndGo There is a grand total of 824 incorrect entries that are OK im SRC680m170
set OS -> Windows
There is something funny to this - in some cases the installation appears to go quite well, in others it fails. Maybe this is related to the names of the directories where the office is installed. Using "StarOffice8_warnings01" fails whereas "warnings01" appears to be ok. Will investigate further
It is not related to the underscore, maybe it's just the length of the directory. To sb.
Reference m170 shows the same behavior. (even worse) OOo 2.0.3 is affected as well, going for OOo 2.0.2...
OOo 2.0.2 is affected as well. Now testing whether this is Terminal Server only ...
Windows normal intallation comes up with a warning message in both OOo 2.0.2 and 2.0.3, so there is a problem as well.
Created attachment 37110 [details] Warning about corrupted config data in 2.0.2
Created attachment 37111 [details] Warning about corrupted configuration in 2.0.3
@jsk: This issue confuses me: A On CWS warnings01, there is a problem that certain UI strings are wrong. On CWS warnings01, there is no problem with a message box about corrupted configuration files, right? B On plain 2.0.2/2.0.3, when installed in a specific way, there is a problem with a message box about corrupted configuration files. In those scenarios, is there also the problem that certain UI strings are wrong? C Is target milestone 2.0.4 justified, or is this 2.X?
@sb: I'm sort of confused as well. What it boils down to is: If we install the office to a directory with a long filename we end up with a corrupted configuration. This happens to 2.0.2, 2.0.3, SRC680m170 and CWS Warnings01. This is Windows only so far. On Terminal Server installations we have this plainly visible: In Draw/Impress toolbars are displayed at random and have lots of icons missing, the menus are incomplete (84 entries blank) and Tools/Customize/Keyboard has the slotnames instead of the names of the items (384 occurrences). Installations on Windows (normal Windows, Userland installation) the warning appears but the office claims to work ok. We did not go into detail here. Regarding the target: This is currently discussed, if this is going to be 2.0.4 - or what would be far worse 2.0.3 - or 2.x i don't know yet.
So, the message box about corrupted configuration also appears when doing the automated test described in this issues initial description? [Removed "CWS Warnings01" from the summary.]
No, you found the strange part of the issue. ;-) This message only appears on "normal" Windows.
.
. *** This issue has been marked as a duplicate of 50885 ***