Error: GPGME error: No data after fresh install

Hello @francois072 :wink:

Looks like this could be a solution for you:

I already tried that, but I’ll try it again.

It’s great if I can update stuff, but when are the signatures going to be fixed?

Myself I had never that issue and cannot see how this could happen right now, (I use always pamac to update manjaro), but…

As you see, the problem was solved. Maybe there some sort of problem with pacman here… :man_shrugging:

1 Like

I cannot say why so many users are having similar issues - but I do know why the error is thrown.

When pacman requests a file from a mirror - it uses the method setup in pacman.conf.

This defaults to curl. curl writes the request file’s content to the requested location.

When pacman verifies the content - the content is not as expected - usually because it is a html document - most likely a 404 response.

To mitigate it - change your primary mirror to a verifiable mirrror like

https://mirror.moson.org/manjaro

I suspect this has something to do with the CDN mirrors - but I really don’t have a clue.

How can I add only verifiable mirrors without doing it manually?

You cannot.

You may get an idea on why it happens by reading my mirror troubleshooting from many moons ago.

What counts as a verifiable mirror?

What about - a mirror that works?

I mean how do I know which mirrors I should choose?

https://repo.manjaro.org

My personal criteria is mirrors which are has synced unstable branch within the past 30 minutes. easyname, kyberorg, moson and alpix mirrors are very good mirrors.

But then again I run my own mirror - so I am kind of biased.

It seemed to work for a while, but now I get the same error again listed in the title.

Could you please post the content of your /etc/pacman.d/mirrorlist?

I suspect the pamac-mirrorlist.timer is in play - it runs the command pacman-mirrors -f8 on a weekly base.

This is just a thought - I wonder if you have the manjaro.re mirror as the first mirror. The mirror is using cloudflare and I suspect the cloudflare cache service is messing with the mirrors pool of packages.

##
## Manjaro Linux default mirrorlist
## Generated on 2021-09-29 00:46
##
## Please use 'pacman-mirrors -f [NUMBER] [NUMBER]' to modify mirrorlist
## (Use 0 for all mirrors)
##

## Country : Ukraine
Server = https://fastmirror.pp.ua/manjaro/stable/$repo/$arch

## Country : Bulgaria
Server = https://mirror.telepoint.bg/manjaro/stable/$repo/$arch

## Country : Indonesia
Server = https://mirror.deace.id/manjaro/stable/$repo/$arch

## Country : Switzerland
Server = https://mirror.init7.net/manjaro/stable/$repo/$arch

## Country : Germany
Server = https://manjaro.moson.eu/stable/$repo/$arch

## Country : Finland
Server = https://manjaro.kyberorg.fi/stable/$repo/$arch

## Country : Global
Server = https://mirrors.manjaro.org/repo/stable/$repo/$arch

## Country : United_Kingdom
Server = http://manjaro.mirrors.uk2.net/stable/$repo/$arch

## Country : Netherlands
Server = https://mirror.erickochen.nl/manjaro/stable/$repo/$arch

## Country : Hungary
Server = https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch

## Country : United_States
Server = https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch

## Country : Germany
Server = https://mirror.moson.org/manjaro/stable/$repo/$arch

## Country : South_Africa
Server = http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch

## Country : Netherlands
Server = https://manjaro.mirrors.lavatech.top/stable/$repo/$arch

## Country : United_Kingdom
Server = https://mirror.cyberhost.uk/sites/manjaro/stable/$repo/$arch

## Country : Poland
Server = https://repo.skni.umcs.pl/manjaro/stable/$repo/$arch

## Country : United_Kingdom
Server = https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch

## Country : Germany
Server = https://mirror.alpix.eu/manjaro/stable/$repo/$arch

## Country : Netherlands
Server = https://mirror.koddos.net/manjaro/stable/$repo/$arch

## Country : Germany
Server = https://mirror.23m.com/manjaro/stable/$repo/$arch

## Country : Germany
Server = https://mirror.netcologne.de/manjaro/stable/$repo/$arch

## Country : Bulgaria
Server = https://manjaro.ipacct.com/manjaro/stable/$repo/$arch

## Country : Canada
Server = https://osmirror.org/manjaro/stable/$repo/$arch

## Country : Bulgaria
Server = http://manjaro.telecoms.bg/stable/$repo/$arch

## Country : United_States
Server = https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch

## Country : Canada
Server = https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch

## Country : Sweden
Server = https://mirror.zetup.net/manjaro/stable/$repo/$arch

## Country : New_Zealand
Server = http://manjaro.mirrors.theom.nz/stable/$repo/$arch

## Country : Germany
Server = https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch

## Country : Costa_Rica
Server = https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch

## Country : Netherlands
Server = https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch

I have again followed the Manjaro wiki to clear the keys and all that, but keep on getting errors even when refreshing the keys.

We have some user in the Spanish Telegram group with the same problem. Mirrors are Ok (checked and rechecked). Keys database regeneration doesn’t help. But disabling signature checking (SigLevel = Never) updates and new installs work as expected.

My guess is that it is in the GPG part, but I can’t still say where.

1 Like

That worked. I don’t get the GPGME error when updating. Why does the default pacman.conf work for other users, but not me?

I don’t know - the configuration will work - as can be deducted from the Arch bugtracker.

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