Following a reinstall of 8.2, I cannot get OpenOffice to start - the terminal window on the first start complains of a segmentation fault. I tied uninstalling it with YaST and then replacing it with the latest version (1.0.3) tarball. On running "./install --prefix=/opt" it returns to the prompt after a second or two, with no messages, and no installation has taken place. Interestingly enough, I downloaded the StarOffice 6.1 beta the other day and it won't install either.The installation window comes up for a couple of seconds, then disappears. Any suggestions? Many thanks. David -- Si Hoc Legere Scis Nimium Eruditionis Habes
On Friday May 30 2003 11:37 am, David Robertson wrote:
Following a reinstall of 8.2, I cannot get OpenOffice to start - the terminal window on the first start complains of a segmentation fault. I tied uninstalling it with YaST and then replacing it with the latest version (1.0.3) tarball. On running "./install --prefix=/opt" it returns to the prompt after a second or two, with no messages, and no installation has taken place.
Interestingly enough, I downloaded the StarOffice 6.1 beta the other day and it won't install either.The installation window comes up for a couple of seconds, then disappears.
David, this is a noted problem....NOT widespread, but is noted. From what I can determine, this happens occasionally with upgrades. The ONLY way I could fix it, was to do a fresh install, INCLUDING my /home partitian......format all and reinstall. Fred -- Powered by SuSE Linux 8.2 Pro & KMail 1.5.1 Never forget: At Microsoft, the engineering department are the Ferengi... The marketing and legal departments are the Borg!
On Fri, 2003-05-30 at 17:53, Fred A. Miller wrote:
David, this is a noted problem....NOT widespread, but is noted. From what I can determine, this happens occasionally with upgrades. The ONLY way I could fix it, was to do a fresh install, INCLUDING my /home partitian......format all and reinstall.
Fred
Thanks Fred - just what I didn't want to hear! I didn't find anything in the archives or with google, funnily enough, so I guess it's uncommon. Unfortunately, I'm off on a two month business trip on Sunday and I didn't really want to spend the Saturday getting another reinstall organised. If needs must, though........... David -- Si Hoc Legere Scis Nimium Eruditionis Habes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alle 23:38, venerdì 30 maggio 2003, David Robertson ha scritto:
On Fri, 2003-05-30 at 17:53, Fred A. Miller wrote:
David, this is a noted problem....NOT widespread, but is noted. From what I can determine, this happens occasionally with upgrades. The ONLY way I could fix it, was to do a fresh install, INCLUDING my /home partitian......format all and reinstall.
Fred
Thanks Fred - just what I didn't want to hear! I didn't find anything in the archives or with google, funnily enough, so I guess it's uncommon. Unfortunately, I'm off on a two month business trip on Sunday and I didn't really want to spend the Saturday getting another reinstall organised. If needs must, though...........
I am in the same situation as yours. I have been digging into openoffice users mailing list. At last, they have said I should go to the developer's openoffice ml to fix the problem. I have not been there yet, though. Praise -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+2PV76v3ZTabyE8kRAidTAKDip7mdxAVU2HwGdJ/FxVVnVTYoBwCfeC1x 5rFtd4Zi0vjpNFmng7mTAfA= =B+SQ -----END PGP SIGNATURE-----
On Sat, 2003-05-31 at 12:33, Praise wrote:
--BEGIN PGP SIGNED MESSAGE-- Hash: SHA1
Alle 23:38, venerdì 30 maggio 2003, David Robertson ha scritto:
On Fri, 2003-05-30 at 17:53, Fred A. Miller wrote:
David, this is a noted problem....NOT widespread, but is noted. From what I can determine, this happens occasionally with upgrades. The ONLY way I could fix it, was to do a fresh install, INCLUDING my /home partitian......format all and reinstall.
Fred
Thanks Fred - just what I didn't want to hear! I didn't find anything in the archives or with google, funnily enough, so I guess it's uncommon. Unfortunately, I'm off on a two month business trip on Sunday and I didn't really want to spend the Saturday getting another reinstall organised. If needs must, though...........
I am in the same situation as yours. I have been digging into openoffice users mailing list. At last, they have said I should go to the developer's openoffice ml to fix the problem. I have not been there yet, though.
I may have found away around this. After playing with various upgrades and other changes, it was time to do some work. So I tried to open some text files with OO and they would not open. Using konsole to try and open, found it was the infamous seg fault. Removing .sversionrc did not help. 00 1.02 that had worked earlier today would not open. Tried to install the SO beta that I had downloaded earlier. It almost started to install then stopped. Tried the SuSE StarOffice 6.0 patch cd (I was really trying to avoid a full re-install! ). Again Konsole showed a seg fault. In order to get some work completed (and really avoid starting to do the re-install) I was about to transfer the files to my wife's computer. Out of pure desparation I used Yast / System Update. Not that I needed anything updated, but simply out of desparation. Yast / System update removed a few files which I did not record and do not care because the option was looking like a re-install. After System Update I clicked on the OO icon and OO was re-installed. Hooray. That was so KEWL that I then installed SO beta 6.1, which also installed slick (except that SO would not recgonize Blackdown Java). On my computer the OO seg fault did not require a re-install once Yast / System Update had been run. I did lose spell-check in evolution but that is a fair trade-off to avoid a re-install. HTH, but YMMV -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alle 03:04, domenica 1 giugno 2003, Ralph Sanford ha scritto:
I am in the same situation as yours. I have been digging into openoffice users mailing list. At last, they have said I should go to the developer's openoffice ml to fix the problem. I have not been there yet, though.
I may have found away around this.
After playing with various upgrades and other changes, it was time to do some work. So I tried to open some text files with OO and they would not open. Using konsole to try and open, found it was the infamous seg fault. Removing .sversionrc did not help. 00 1.02 that had worked earlier today would not open.
Tried to install the SO beta that I had downloaded earlier. It almost started to install then stopped.
Tried the SuSE StarOffice 6.0 patch cd (I was really trying to avoid a full re-install! ). Again Konsole showed a seg fault.
In order to get some work completed (and really avoid starting to do the re-install) I was about to transfer the files to my wife's computer.
Out of pure desparation I used Yast / System Update. Not that I needed anything updated, but simply out of desparation. Yast / System update removed a few files which I did not record and do not care because the option was looking like a re-install. After System Update I clicked on the OO icon and OO was re-installed. Hooray. That was so KEWL that I then installed SO beta 6.1, which also installed slick (except that SO would not recgonize Blackdown Java).
On my computer the OO seg fault did not require a re-install once Yast / System Update had been run. I did lose spell-check in evolution but that is a fair trade-off to avoid a re-install.
HTH, but YMMV
Do you know what files it removed?? Yast/System update did not solve the problem for me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+20Dj6v3ZTabyE8kRAhodAJ9jrCACZX2XL0znc/YjsQWkiJmfmgCgskTz +ZI9Pd+/iJ8ilyNOpwl26a0= =F084 -----END PGP SIGNATURE-----
On Mon, 2003-06-02 at 06:19, Praise wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alle 03:04, domenica 1 giugno 2003, Ralph Sanford ha scritto:
I am in the same situation as yours. I have been digging into openoffice users mailing list. At last, they have said I should go to the developer's openoffice ml to fix the problem. I have not been there yet, though.
I may have found away around this.
snipped
Out of pure desparation I used Yast / System Update. Not that I needed anything updated, but simply out of desparation. Yast / System update removed a few files which I did not record and do not care because the option was looking like a re-install. After System Update I clicked on the OO icon and OO was re-installed. Hooray. That was so KEWL that I then installed SO beta 6.1, which also installed slick (except that SO would not recgonize Blackdown Java).
On my computer the OO seg fault did not require a re-install once Yast / System Update had been run. I did lose spell-check in evolution but that is a fair trade-off to avoid a re-install.
HTH, but YMMV
Do you know what files it removed?? Yast/System update did not solve the problem for me.
Sorry I did not particularly notice. Approximately 5-7 files were removed. Aspell was the one I noticed. I should have paid attention, but I did not care what was removed as I was about to face a fresh re-install which would have meant everything would be removed. Spell checking in evolution does not work now, even after re-installing aspell, but with OpenOffice now working I can at least do most of my work. -- Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01
participants (4)
-
David Robertson -
Fred A. Miller -
Praise -
Ralph Sanford