On 03/ 2/10 04:57 PM, W. Wayne Liauh wrote: >> I downloaded and installed OpenOffice 3.2 last night >> on my snv_133 x64 system, the only hiccup I saw was >> the "Next" button being grayed out on the initial >> setup screen - but clicking the "Help" button, then >> returning to the initial setup screen resulted in it >> becoming available (weird), after which it installed >> and ran fine. >> >> What error did you see? >>
For me it was a little different. I'm running the development editions. I was at m71. So I ran the upgrade script and everything went normally. Then I went to open Openoffice and it wouldn't start from the icon. Next I opened a terminal to start it from the command line to see if there were any error messages. I don't remember exactly but it said something like couldn't execute something. Then I went to open other applications and it to had the same error message. I thought, maybe a reboot will fix this. So I clicked on the Icon I had (pfexec /usr/sbin/init 5) to shutdown, I don't use reboot since fast reboot was installed it never worked. The computer wouldn't shutdown, it just hung. I held the power switch for 5 seconds and proceeded to reboot. It gets just past grub and then just hangs indefinitely. I had to boot into b132 which worked just fine. So, now here I am, afraid to install/upgrade Openoffice m72 because its an old Sys-5 package. > I ran the setup script, everything "seemed" to be OK (I did not pay attention > to the installation messages--which I should have). I was very happy until I > realized that the installation actually FAILED and I was still running the > old OOo 3.1 (installed from the IPS repository). > > So, I decided to run the update script. Again, everything seemed to be > OK--the old OOo 3.1 was removed as I was told and the script continued. This > time, I couldn't even start OOo. > > The third time around, I used IPS to remove OOo, then ran the setup script. > I probably did something else but I can't remember. This time, the system > froze, forcing me the do a cold reboot, which failed. > > I tried to do "svcadm disable /system/boot-archive" from the console to see > whether I could revive the system, but it failed. Since this was a clone, I > thought it would be much easier simply to boot into the original b133 and > destroy the clone. > > This is how the story went. Sorry I couldn't provide more detailed info. > > Also, please note that this is a virgin installation of b133. I remember at > one time (more than one year ago), after I had changed the java runtime > environment, I was actually able to install OOo from the setup script. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20100302/c6fc8929/attachment.html>
