On Mon, 28 Jan 2002 at 02:08, Paolo Alexis Falcone wrote: > I've been getting this problem when I reinstalled StarOffice 5.2 and/or > OpenOffice build 641 on my home PC (Athlon, kernel 2.4.17-xfs, Debian > Potato r5). Since last Friday, whenever I reboot the machine, the SO/OO > install just gets wrecked when I try to run StarOffice or OpenOffice by > the next session. Here's the error message in OpenOffice: > > The application cannot be started. > The configuration service is not available. > Do you want to start the setup application to repair your installation? > [yes][no]
I run into this same problem with OpenOffice 641C, on an Intel Pentium III 733MHz, 2.4.17-xfs, Debian/Sid. No problems with StarOffice 5.2. I haven't figured out what causes this problem, but I never really progressed past installation (ie: always runs into this when I try to run things). > In StarOffice it was kinda more descriptive (it reads the initialization > script file instead of the normal, like OpenOffice...) > > In the StarOffice 5.2 installation, the following file could not be found! > > /home/himiko/office52/user/sofficerc > > StarOffice 5.2 requires this file to be executed correctly. With the aid > of the setup program it may be restored. > > Click 'Repair' to let the setup program repair your 'StarOffice 5.2' > installation. Click 'Cancel' to terminate the installation now. > [Repair][Cancel] On a kiosk where I first realized that ext3 would have been a better pick instead of XFS, I ran into corrupted config files often because they'd turn it off during those perfect times when the old file was deleted synchronously to make way for a new file during an edit, and the new file is still in the buffer, leading to an config that was null'd out. Normally I have to delete the user's local so52 directory and re-configure. > I believe this can be a mitigating factor: Power was tripped Friday at > our place. When it did came back, my /home (XFS) developed a file hole > in .gnome-errors, which skyrocketed my harddisk consumption to 99% from > 67%. Deleted the file using the XFS tools, but df didn't report filesize > normally until I rebooted. Then this problem started appearing. Ooh, you may want to share this with the XFS list. However I'd just like to share that I hit those problems with OO 641C on a system with a UPS. So no hole. Disk usage is normal. Have you tried xfs_repair, BTW? The XFS developers normally ask this first and foremost, and then ask what it said. > Invoking OpenOffice from an Xterm mentions: > > OpenOffice.org641/soffice: //HACK: No such file or directory. Now we're talking. This is the exact same message I get with OpenOffice!!! Goodness gracious. What the hell is that //HACK file? > Tried the arduous process of fsck and XFS repairs. No avail. Even mkfs > then copy back again all the data for /home doesn't solve the problem. Oh my. BTW, have you tried changing the target directories of both system and user installations? Might work. --> Jijo -- Federico Sevilla III :: [EMAIL PROTECTED] Network Administrator :: The Leather Collection, Inc. GnuPG Key: http://jijo.leathercollection.ph/jijo.gpg _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
