Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Registry keys are not removed | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Installation | Reporter: | mhatheoo <mh.hh> | ||||||
Component: | ui | Assignee: | Olaf Felka <olaf-openoffice> | ||||||
Status: | CLOSED FIXED | QA Contact: | issues@installation <issues> | ||||||
Severity: | Trivial | ||||||||
Priority: | P2 | CC: | issues, khirano, nesshof, rainerbielefeld_ooo_qa | ||||||
Version: | OOO300m3 | ||||||||
Target Milestone: | OOo 3.0 | ||||||||
Hardware: | Unknown | ||||||||
OS: | Windows 2000 | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Issue Depends on: | |||||||||
Issue Blocks: | 88888 | ||||||||
Attachments: |
|
Description
mhatheoo
2008-08-20 23:20:20 UTC
Not an l10n issue, but installation. @is,mh: sounds pretty much like a show stopper to me.. isn't ooo-dev for OOO300 wrong anyway? Currently I can not confirm any problems. I uninstalled "Ooo-dev 3.0.0 Beta Multilingual version English UI WIN XP: [OOO300m2 (Build9343)]" with it's German and French language packs without deleting the remainint program and profile folders. Then I installed "Ooo-dev 3.0.0 Beta Multilingual version English UI WIN XP: [OOO300m3 (Build9344)]" and additionally German language to the default directories: <C:\Programme\OOo-dev 3\program\soffice.exe> I am used to have an addditional <C:\Programme\OOo-dev\Basis 3.0> Installed language packs DE and FR work fine. So currently I can not confirm those problem, but Issue 92977 seems to confirm problems. @mhatheoo: What WIN versions did you test? Did you install to default directories? What earlier OOo3 version did you have on your PC? Did you uninstall that old ersion? Please contribute a step by step instruction containing all observations (error messages ...), every key press and every mouse click how to reproduce the problem, and explain why you believe that your results are unexpected. is -> of: can you please try to reproduce this? OS is W2K earlier version (BEB m2) had been uninstalled prior to OOO300m3 Bytheway -- regarding the language-pack itself it is a P1 - in regard to the OOO itself, it is a P3 - of course -- just copying the content from wrong to right destination makes menu-layout/help-files work as expected - but the setting (disable wordbooks etc) partly does not work Martin @mhatheoo Still some of my questions are without answer. Please contribute details concerning uninstallation of BEB m2: What language pachs have been installed / uninstalled, order of uninstallation, did you also delete folders manually, ... Can you reproduce the problem with FR language Pack? ==> rainerbielefeld I do not understand your questions May be you should give back the info if you have a win-system availabe for retesting this issue. But here are the answers. Installed prior dev-version had uninstalled by the windows-build-in uninstall-tools /system-folder/software/uninstall) Folders can not be deleted because of the broken setup-concept of the 3.0-dev-versions, which is touching/installing to the working/stable OpenOffice the installation from the langpack can easiely be verified by the file-attributes. as the setup of the 3.0-version can not be changed from the default destination-pathes for other unforeseeable results (this is another issue) I just let it run on default settings, and the lang-pack-setup did not find its destination. thats all. Well, sorry, I really do not mind to test the FR-langpack-setup aswell rgds Martin Win XP and Win 2000: I've installed the Office to 'c:\program files\OOo3_dev_m3'. The language pack installer has detected this installation, installs to this directory and works when starting the office. What confuses me is "Folders can not be deleted because of the broken setup-concept of the 3.0-dev-versions, which is touching/installing to the working/stable OpenOffice ". In which way the developer snapshots touches a stable Office? OOo2.x uses a different install targets as the snapshots of OOo3 did. ==> hm, funstuff ooo3_dev_m3 is not the default dir for install that version, and wonder why you installed a german langpack to an english system in here stable versions are always installed to Programme/openoffice the m3 installs to programm/ooo-dev 3 the langpack to programm/ooo-dev but the language-settings of the en-us-version go to programm/openoffice/ in the dir ooo-dev/(with basis ... and so on) I am interested in this, so I will uninstall everything and reinstall as above (stable to "openoffice" and ooo-dev to defaults) I am in the mood to bet, but we'll see Martin ==>of hours later - what good it's for absolutly same behavior found, that the reg-entries of prior installations are not use, killed about 100 ooo-related reg-entries anyway, reinstalled 2.4.1(stable) and dev300m3, well, have a look at the screenshot Martin Created attachment 55964 [details]
paths: result of default inst of dev3m3 and langpack DE
*** Issue 93220 has been marked as a duplicate of this issue. *** see also issue 93220. @ is: Will this be a potential stopper? Or is this just related to dev snapshots? Can it be that some old registry entries cause these behavior? please look for HKLM(HKCU)\software\openoffice.org\. I can't reproduce on my XP machine. ==> of nope - this can not be - all star/open-office-related entries had been deleted prior to installation. Well - no polemics is always good politics, but ... the solution you may find in this confusing setup-concept: http://blogs.sun.com/GullFOSS/entry/handling_the_dynamic_links_in Martin At least it seems that we need the download urls of the lang-packs and the office. We need a valid way to reproduce. I've never been able to do so, not on WinXP nor on Win2000. Te language folder of 'help' are all in \programme(program files)\OOo-dev\Basis 3.0\help\ As Rainer has written this is not a common problem. On Windows 2000, OOo-Dev_OOO300_m3_Win32Intel_install_en-US.exe installs "OOo-dev 3" and "OpenOffice.org", and OOo-Dev_OOO300_m3_Win32Intel_langpack_ja.exe installs "OOo-dev". See the directory structure under "Program Files" I will attach to this issue. Created attachment 56094 [details]
The directory structure under "Program Files"
@ khirano: Can you please provide the download urls for the language pack? Have you tried to search and clean the registry? @ of: 1. download urls for the language pack: ftp://ftp.jaist.ac.jp/pub/openoffice/extended/developer/OOO300_m3/ 2. search and clean the registry: Sorry but I am not good at searching and cleaning them :) How do you do that? @ khirano: Look in HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.org or HKEY_CURRENT_USER\SOFTWARE\OpenOffice.org. There you have three subfolder: HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.org\Layer HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.org\OOo-devLanguagePack HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.org\UNO If you have uninstalled all you OOo 3 stuff these entries can be deleted. Then please retry to install again. @ khirano: I've tried with the installation files from ftp://ftp.jaist.ac.jp/pub/openoffice/extended/developer/OOO300_m3/: Sorry, but I can't reproduce. All ja files ended up in e.g. C:\Program Files\OOo-dev\Basis 3.0\help\. @ of: I've just learned how to use regedit on Windows :) I uninsalled all OOo and deleted all OOo folders and files. Then I deleted "HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.org" and "HKEY_CURRENT_USER\SOFTWARE\OpenOffice.org". I tried OOo installation on Windows 2000 SP4 again and got good results :) OOo-Dev_OOO300_m3_Win32Intel_install_en-US.exe installs "OOo-dev" and "OOo-dev 3". OOo-Dev_OOO300_m3_Win32Intel_langpack_ja.exe installs "OOo-dev". Now I can select Japanese for language of UI and use OOo with Japanese UI. But .... Are we going to ask our good old users to use regedit to fix this issue? @ khirano: "But .... Are we going to ask our good old users to use regedit to fix this issue?" We have to find out whether the OOO300_m4 leaves it's entries in the registry. I don't think it's the common behavior that OOo leaves it's keys in the registry. I would assume that some misbehavior of the Microsoft Installer might have caused this. And: The good old user don't un/install zillions of OOo snapshots. I would have expected more OOo QA feedback if this problem is a common one. @ Martin: Have checked the registry for this OOo keys? Apologies for my suggestions. It *is* OOoO300_m4 that leaves it's registry keys after uninstall and reuses the partly for a new installation. - install OOO300_m4 and the language pack to e.g. the default location - uninstall all OOo3 stuff - install OOO300_m4 to say ..\program files\OOO300_m4 - the shared layer will be installed to ..\program files\OOo-dev - install the language pack: '..\program files\OOO300_m4' will be detected - the lang pack files will be installed to ..\program files\OOO300_m4\OOo-dev\Basis 3.0 Adjusted summary: 'Registry keys are not removed' Fixed by: - Adding CustomAction for installation check to InstallWelcome instead of LicenseAgreement (OOo has no longer a LicenseAgreement). - Changing Component GUID for the component, that contains language pack entries for the Windows Registry. Using the same GUID led to problems during uninstallation of OOo or OOo language pack (not all entries in Windows Registry were removed). - Removing layer information from OOo language pack. A language pack does not create new layers, so it must not write layer information into the Windows registry. - Some additional minor changes. So this works fine in cws native193 -> Fixed. is -> of: please verify. OF: cws native193: Now all registry keys are remove by uninstalling OOo-dev300 and OOo-dev300_language packs. Hallo a short review as I reported this "in most" the setup already worked with 000300-m4 and is going to, where it was expected: -- installation goes to the expected directories:: programme\ooo-dev 3 and programme\ooo-dev -- partly install goes to dir: Programme\stabversion\ooo-dev (12 files *.res in dir stableversion\ooo-dev\basis 3.0\program\resouce) (it is wrong there!) -- disable that dir (delete it) does not crash OOO300_m4 -- lang-package goes to the right place I do not know, what for all these res-files are used, but I guess this needs to be fixed. however, at actual setup is working. But I guess the new title is not really reflecting the problem: Setup does not make use of registry-entries, they are used for the program when runing. However it is a good idea to delete them prior to non-update-installations for stopping OOo pointing to wrong places. Martin OF: Looks good for me in OOO300_m9. |