Unable to install LibreOffice with a fresh install

After a successful install of Manjaro (manjaro-kde-26.0-260104-linux618.iso), I can’t install Libreoffice (both still and fresh variants). It is possible to install LibreOffice with the original installer (which just copies stuff from the ISO). When attempting to install with

sudo pacman -S libreoffice-still

I will get the following error:

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 changed the mirror, nuked the keychain and ran

sudo pacman-key --init
sudo pacman-key --populate archlinux manjaro

Didn’t help. What next?

On a fresh install you must first install the updated keyring packages… :backhand_index_pointing_down:

sudo pacman-mirrors -f && sudo pacman -Fyy && sudo pacman -S archlinux-keyring manjaro-keyring
sudo pacman -Syu libreoffice-fresh
1 Like

…and unless you have just updated and synced, it is considered a best practice to make the habit of installing with -Syu (or running it just before installing with -S).

2 Likes

That doesn’t change anything. I did a full system update right before anything else. Tried your solution - I’m still stuck.

I did update right beforehand. -S has the advantage of not including other packages in the process, that could be included otherwise. Of course it is generally a better practice, but normally I’m working from a private repo and I tend to check whether that is synced correctly first (and that one gets synced at preset times). In this particular case, I’m using remote repos, in case something is wrong with our server. This error popped up yesterday, I did another fresh install today. This is an old notebook and I do not need it right now, so I’m keeping it as is for now. I need to figure out what’s wrong before I start to install Manjaro onto other machines.

What is the content of your /etc/pacman.conf?

Here you are:

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg      = pacman glibc manjaro-system
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

#IgnorePkg   =
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#NoProgressBar
# We cannot check disk space from within a chroot environment
CheckSpace
#VerbosePkgLists
ParallelDownloads = 4

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Manjaro Linux
# packagers with `pacman-key --populate archlinux manjaro`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs


Hmm… I don’t see anything peculiar in there… :thinking:

I wonder if this is an edge case where the latest archlinux-keyring isn’t quite consistent with the package versions in Manjaro Stable.

A key was removed from the Arch keyring, which resulted in several other keys (such as anatolik) dropping to marginal trust. libatomic_ops has been rebuilt with updated signing, and is available in Manjaro Unstable and Testing, but hasn’t made it to Stable yet.

3 Likes

Very likely, similar case as Cannot install cockpit-docker

4 Likes

Seems like a viable theory. Maybe @philm and @Yochanan can follow how this goes.

Keyring is downgraded. @djaeris can you check if your mirror is synced and if it is sudo pacman -Syuu and see if it helps (the older arch keyring)?

3 Likes

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!

2 Likes

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