Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The option "zypper install openoffice with appropriate rpm data" was used and didn't function [among many other time wasting trials].
And we're all VERY sorry to have wasted your time trying to help you. It certainly won't happen again.
Quote:
I notice you have still not stated that you tried to so install openoffice [NOT libreoffice] and succeeded. Would, again, be delighted to see that you succeeded and list what you actually did.
"sudo zypper install <openoffice rpm file name>". That's it, as said several times. AGAIN, if it doesn't work for you, then there is something fundamentally wrong with your system. And the command you typed in above isn't anything that could be used, so if that's what you ran, I can see why it didn't work.
Quote:
Numerous other users of openoffice have posted that libreoffice did not function for them properly on old openoffice material. This is not some whim.
What obviously IS a whim is whatever data you have, isn't moving forward, and you're trying to install something that's not currently getting support from the various distros, due to licensing issues/disagreements. From their own forum: https://forum.openoffice.org/en/foru...hp?f=9&t=82248
**BOTH** of them save into open document format. OPENING old files isn't a problem at all...so your old data comes right into the updated schemas. And when you SAVE them, it saves an updated document so you can use it going forward. Libreoffice is more heavily developed, and based on the IDENTICAL code base to openoffice. Use whatever you want, but don't complain when folks are trying to help you. Or perhaps we are part of the "they" that are part of this concerted effort to break openoffice too?
Something is probably mis-configured: you could grep for java in any and all config files from the software you're using. Is 'java' in the PATH? Is JAVA_HOME set correctly to point to where java is? Sometimes running your app with 'strace app' can show you where it's looking for stuff. It can work; you just have to have patience.
Thanks jayjwa for your input, but among the many hours that I've devoted to this have tried that and many more options. Since I can now get openoffice using wine on the windows version, I just can't keep spending time on it. Once the wine option worked, I kept trying just to see if there was really something that I overlooked, since I've used suse since it just about first came out [with 10.1] and wanted to believe the "coincidences" of blocked openoffice, were just that [slack easily downloads and installs and opens openoffice almost instantly to have choice alongside caligra, and similar results with other OSes, but while suse still readily fully installed and operated openoffice even after it made libreoffice official choice, with later releases it first became necessary to break it into many separate files before installing, and then with Leap even that has stopped working (it "installs", but something blocks its functioning)].I'll still use the 13.2 32-bit and even Leap occasionally, but am becoming disenchanted. I suppose if I tried some script writing and other terminal inputs, I'd eventually get it up, but enough is enough.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.