Completely removing libreoffice and reinstalling it

Hi, Ive joined bc i have seen some posts about the subject, having joined, cant find those posts. d’oh. In a nut shell I’ve been having some real issues with LO, calc freezing when using mouse to scroll, it generally hanging up. it refuses to copy-paste whereas another machine it’s fine.. It sort of works but nothing like a fresh install which is what I was contemplating, just reinstall Manjaro and restore my backup.

Then I googled instructions to purge LO and any associated files, forget website but its definitely gone. Then I tried reinstalling it and I get this:-

sudo pacman -S libreoffice-still
resolving dependencies...
looking for conflicting packages...

Packages (31) argon2-20190702-6  boost-libs-1.89.0-4  clucene-2.3.3.4-16  libabw-0.1.3-5  libatomic_ops-7.8.2-1  libcdr-0.1.8-3  libcmis-0.6.2-6  libe-book-0.1.3-19
              libepubgen-0.1.1-5  libetonyek-0.1.13-1  libexttextcat-3.4.7-1  libfreehand-0.1.2-5  libixion-0.20.0-4  liblangtag-0.6.8-1  libmspub-0.1.4-18
              libmwaw-0.3.22-3  libnumbertext-1.0.11-2  libodfgen-0.1.8-5  liborcus-0.21.0-3  libpagemaker-0.0.4-4  libqxp-0.0.2-14  librevenge-0.0.5-3
              libstaroffice-0.0.7-4  libvisio-0.1.10-2  libwpd-0.10.3-5  libwps-0.4.14-3  libzmf-0.0.2-19  lpsolve-5.5.2.11-3  rasqal-1:0.9.33-7  redland-1:1.0.17-9
              libreoffice-still-25.2.7-6

Total Download Size:     0.07 MiB
Total Installed Size:  537.25 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 libatomic_ops-7.8.2-1-x86_64                                              66.9 KiB   496 KiB/s 00:00 [############################################################] 100%
(31/31) checking keys in keyring                                                                      [############################################################] 100%
(31/31) checking package integrity                                                                    [############################################################] 100%
error: libatomic_ops: signature from "Anatol Pomozov (Arch Linux developer account) <anatolik@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/libatomic_ops-7.8.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

** it seems I have an issue with zst files, I’ve tried reloading keyrings and doing a refresh (sudo pacman -Sy archlinux-keyring | sudo pacman -Syu) that all works, no updates but try reinstalling LO and it fails. Can any of you wizards guide me through this please.

Mod edit: Added code formatting. Please see this quick guide:

How to post Terminal output

We normally ask for System Information. Example:

inxi -zv8

… with such output, please use the code formatting (the </> button at the top of the Reply window or the three backticks ``` on lines above and below the pasted output).

Note: This output is privacy-filtered using the above command.

You seem to have bad luck in this case choosing the worst time to reinstall..because libreoffice currently appears to have a problem with the signature. Will be investigated and fixed but may take a day or two. I guess there is a flatpak as a temporary solution until then.

p.s. try what Nachlese says, be there is another very similar topic and it seems like a packaging problem and not user system problem.

1 Like

Before you install anything, make sure your system is fully up to date.

sudo pacman-mirrors -f
sudo pacman -Syu

Then you can install stuff anew - like libreoffice in your case.

sudo pacman -Syu libreoffice-still

Don’t just use pacman -S

… (re)installing the very same thing will have the very same result … because:
why and how would or even could it be different? :wink:

1 Like

I recommend using the AppImage for LO, I have been using it for over a year and it has been rock solid.

https://appimages.libreitalia.org/portable/LibreOffice-26.2.0.3.full-x86_64.AppImage

@ndj7919 Yochanon already downgraded the keyring. Check if your mirror is synced (or use Global as country sudo pacman-mirrors -i ) and downgrade with sudo pacman -Syuu and tell us if it fixes it.

2 Likes

Hi, slightly progressed, It’s getting further into the install but still returns:-

error: libatomic_ops: signature from “Anatol Pomozov (Arch Linux developer account) anatolik@archlinux.org” is marginal trust
:: File /var/cache/pacman/pkg/libatomic_ops-7.8.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).

I’d try removing that file before making another attempt at reinstalling LibreOffice, in case you haven’t done this already. :man_shrugging:

Yeah, did that, I guess it’s created at install and it makes sense what was said earlier, that LO having issues with broken file preventing it being installed…

1 Like

There was a problem with archlinux-keyring. An updated version is on the way, but you’ll have to wait until your mirrors have synced (or refresh your mirror list) and then update with… :backhand_index_pointing_down:

sudo pacman -Syuu

That’s a double “u”, because the package must be downgraded.

1 Like

btw this is a duplicate of Unable to install LibreOffice with a fresh install also posted today

No, it’s a different poster. :wink:

Which reports the new-old keyring on stable solves it, by the way.

Aha, thanks for you help guys, the other thread/post has this:-

Repos are synced now, archlinux-keyring is at version 20260107-2.0.

Downgraded, tried to install: still the same problem. Tried to nuke the local keychain once again, and that did the trick. So to summarize, this is the current solution:

sudo pacman -Syuu
sudo rm -rf /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate archlinux manjaro
sudo pacman -Syu libreoffice-still

Thanks a lot for help!

it worked.. !!! and i’m back creating LO files!!.. I hope the other copy/paste issue I had has also done one..

once again, thankyou

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.