General Error at open or save using Manjaro Linux

[Hagar Delest]

And try to run AOO as root to see f the problem occurs also.

[keme]

A shot in the dark about the save problem:
Do you have a trailing space in the file name when saving? Generally, file systems do not allow leading/trailing spaces in file names.

This should apply equally to saving as doc, though, so not a likely cause, and does not explain the issues around opening existing files. Just a thought.

[bcripps]

Yes, Rory. I have a ThinkPad with Windows but I had to fire it up to find out what word processing software is installed. I only have the laptop so I can run PaintNet which I use to add text to photos manipulated in Gimp. OpenOffice 4.1.14 is installed and it works perfectly, handling .odt files without issue.
I recently switched from Zorin to Manjaro because OO is in the AUR package manager. I could never get OO to install properly in Zorin (either?).
Not sure how to run OO as root. I can't find OO executable (soffice) in my Directories. “find soffice” brings up “no such file or directory” in the terminal. Further instructions, please.
And thank you keme for joining the fray. Saving with a trailing space brings up an Error Window which I don't see unless purposely adding a trailing space. Thank you everyone.
Bry

[floris v]

Run software as root means: run it as administrator, not as ordinary user. If AOO was installed correctly, it's available for all user accounts, including the one with administrator permissions.

[RoryOF]

On way out, so in haste. In terminal Sudo OpenOffice4 should give you root.

OpenOffice worked for me on a trial Manjaro install.

[RPG]

I use OpenSUSE 15.6 what is the current version. I did always install ApacheOffice for 64 bits without problems but since this version it does no longer work. I did understand that openSUSE did remove some old parts maybe that is the reason of the problem for not running ApacheOffice.

On way out, so in haste. In terminal Sudo OpenOffice4 should give you root.

I can run ApacheOffice as root but not with sudo. I must first start with su and then I can run Apache Office. I did this also with a fresh installation on an older 64 bits computer.

Running ApacheOffice as root was only for testing I do now work with LibreOffice.

[RoryOF]

Running sudo openoffice4 on Xubuntu 24.04.5 ran it OK for me (just now tested).

It did require me to log in to OpenOffice as a newly registered User.

[bcripps]

Opening OO as root (sudo openoffice4), I wrote a test .odt document. When I clicked on save I got the “Error Saving the Document.” When I closed the terminal opened with “Segmentation fault dumped. See attachment.
Bry

[RPG]

You get the same error as get. Maybe the number for the segementation fault is not the same. When I start first with "su" then I can run ApacheOffice as root. But it is not good to run a program as root for a long time.

I have accept that ApacheOffice does not work more and as more people I did prefer ApacheOffice for some reason but I have to change now to LibreOffice.

[floris v]

A segmentation fault means that the program tries to access a memory location that it shouldn't be able to access. This is normally caused by a programming error of a kind that shouldn't occur in OpenOffice, so your installation may be corrupted.
This is taking you a lot of time. I suggest that you try your luck with LibreOffice.

[RoryOF]

When running linux, a useful fault-finding trick for OpenOffice is to use a terminal and enter openoffice4 - the trailing 4 is important.

This will give any errors when OpenOffice runs.

[bcripps]

Okay. I give up. I don't like LibraOffice so I guess I'll be working in .doc for the time being. Thanks everyone for your patience, suggestions and support.
Until the next problem...
Bry

[RoryOF]

Occasionally OpenOffice throws a fault after exiting a file (which has been safely saved - running on Xubuntu). The files, of any size, including very large (several thousand pages in Writer or several hundred slides in Impress) have always been Saved correctly, so I never bothered to investigate in depth - it seems to be a graphics problem.

LibreOffice working in .odt would be a much preferable choice to Word (for working in .doc)

I should mention that I had OpenOffice 4.1.15 running OK on a trial Manjaro installation, which I scrapped because of problems with printer installation and pressure of time for a large printing project - quicker to install the printer and print the project on an existing Xubuntu install.

I think Manjaro of more recent versions has improved printer installation, so I might try it again when I have time.

[RoryOF]

Today I installed Manjaro 24.2.1-241216-linux612.iso, using the XFCE desktop, fully updated after the install. I then installed OpenOffice 4.1.15 from the AUR repository and ran OpenOffice.

When I Saved a small Writer file I got a General error writing the file; the file was nevertheless written correctly. On reopening the file, before it displayed, a General error popped up, but the file reopened. The little diagnostics I had time to do indicated a segmentation fault.

[Later] Reopening a Saved file gave the General error, but the file then opened correctly. After an edit, the file closed without any error message.

[Hagar Delest]

Seems to be an issue with the packaging then. Likely for Manjaro team (or Arch).

[RoryOF]

I think it might be with the creation or opening of the file at system level. Haven't time to investigate further today.

[bcripps]

Still watching and listening...
Bry

[Hagar Delest]

My conclusion is that there is a problem in the Arch or Manjaro package. Either coming from a problem with AOO running on Manjaro or from the packaging of AOO.
Since it works well for other distros, I would say that the issue is with the packaging of the application.
Then, it's your call. Since it seems to save anyway, either live with that or switch to LibreOffice or keep AOO but with another distro.
You can report it to the Manjaro devs also. Since there is no AOO dev here and definitively not enough dev manpower to investigate such issue, very few chances asking them