-----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-----