To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113708
                 Issue #|113708
                 Summary|can't update from Hebrew 3.1 to English 3.2.1
               Component|Installation
                 Version|current
                Platform|Opteron/x86_64
                     URL|
              OS/Version|Windows XP
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|of
             Reported by|ilantal





------- Additional comments from [email protected] Fri Aug  6 13:59:42 
+0000 2010 -------
A friend of mine reported to me problems he was having with English 3.2.1. I was
running Hebrew 3.1 and I told him I would look at it on my XP system. From the
Control Panel I uninstalled 3.1 and proceeded to install 3.2.1.
The computer went into an endless loop using 100% CPU with unopkg.bin. I had to
kill the process. Then I did a Remove, which worked. I tried again and it got
stuck again. Again I killed the process and did another Remove, which again 
worked.
Since OO is very important to me, and 3.2.1 isn't terribly important, I returned
to Hebrew 3.1. That is up and running.
It seems to me that this is reproducible. The Hebrew 3.1 seems to have put
something in the registry which is killing the update.
Thanks,
Ilan

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to