You are not logged in.

#1 2021-12-14 22:48:02

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Failed to start Authorization Manager

I recently attempted a Pacman -Syu after some months without update.  It failed to complete.  Following that, when I tried the same update I would get the error "version 'GLIBC_2.33' not found (required by sudo)"

Now the system won't boot.  I get the startup messages and they stop shortly after the "Failed to start Authorization Manager" message.  Ctrl-C does not allow it to continue.

I am able to Ctrl-Alt-F3 into a new terminal at this point.

Offline

#2 2021-12-15 09:10:09

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,971

Re: Failed to start Authorization Manager

The glibc bump is almost a year old. Broken glibc means you pretty much need a live system or pacman-static, from a live system mount all your partitions under /mnt like they should be including mnt/boot or so if applicable and run a

pacman --sysroot /mnt -Syu

Offline

#3 2021-12-17 18:55:17

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Re: Failed to start Authorization Manager

I booted from a USB drive with Arch install medium and from Archiso mounted the partitions from the original arch drive to /mnt and /mnt/boot respectively.  I then ran your command and received the errors:

error: could not open file: /etc/mtab: No such file or directory
error: could not determine filesystem mount points

Is this not referred to as a live system?  If not then what do you mean?

Offline

#4 2021-12-17 21:01:07

seth
Member
Registered: 2012-09-03
Posts: 26,217

Re: Failed to start Authorization Manager

mounted the partitions from the original arch drive to /mnt and /mnt/boot respectively

error: could not open file: /etc/mtab: No such file or directory

Did you by any chance chroot into the installed system?

Offline

#5 2021-12-19 17:40:18

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Re: Failed to start Authorization Manager

If I chroot into the system and run the update I get the glibc error again

Offline

#6 2021-12-19 21:18:11

seth
Member
Registered: 2012-09-03
Posts: 26,217

Re: Failed to start Authorization Manager

I didn't mean to say "you should chroot" but "if you had chrooted, that could explain the error"
/etc/mtab is a symlink to ../proc/self/mounts and if you just chrooted (not arch-chrooted), you probably don't have /proc in place

What's "lsblk -f; stat /proc"  when you try to run that pacman command?

Offline

#7 2022-01-07 22:47:12

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Re: Failed to start Authorization Manager

Ok I got the proc thing sorted out by following your advice and this guide:
https://wiki.archlinux.org/title/pacman … an_upgrade

The files are updating now, however it will update 20-30 or so before returning 404s (failed to retrieve some files).  I have about 650 updates to go.  I can keep manually restarting the update until it is finished, but if there is a way to prevent it from stopping midway that would be appreciated.

Offline

#8 2022-01-07 23:18:20

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,151

Re: Failed to start Authorization Manager

See https://wiki.archlinux.org/title/Mirror … irror_list for a way to generate a fresh, ranked mirrorlist for your country. Install the pacman-contrib package to get the rankmirrors command.

Online

#9 2022-01-07 23:21:27

Slithery
Forum Moderator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 4,851

Re: Failed to start Authorization Manager

Choose a different mirror that is actually up to date.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#10 2022-01-14 22:41:41

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Re: Failed to start Authorization Manager

I ranked the top 20 mirrors following your advice and the wiki, and still had issues updating packages - getting through none or up to 50 before having to restart.  Could be my ISP Spectrum which I've had issues with.

Finally, after many retries I worked down to the last few packaged (out of 900+), and I got a long string of the error:

"error: GPGME error:  invalid crypto engine"

after that long string of errors, I got this error for each package:

"File var/cache/pacman/pkg/package-name is corrupted (invalid or corrupted package  (PGP signature))."
Prompting me to delete it for every one.

After trying to reupdate it starts all over at 900+ packages...

Offline

#11 Yesterday 08:14:55

seth
Member
Registered: 2012-09-03
Posts: 26,217

Re: Failed to start Authorization Manager

The packages are first downloaded, then checked. Since you probably deleted all of them for the gpgme error, you now have to re-download them.

Boot the install iso.
Mount the root partition of the installed system to /mnt
Do NOT chroot into the installed system.
Try to run

pacman --sysroot /mnt -Sy archlinux-keyring

If that runs w/o error

pacman --sysroot /mnt -Su

otherwise post the exact error you got from the archlinux-keyring installation.

Offline

#12 Today 02:18:22

Robert_Adolph
Member
Registered: 2021-01-18
Posts: 7

Re: Failed to start Authorization Manager

The error I get from the keyring install:

"
Checking keys in keyring
error: GPGME error: Invalid crypto engine
Checking package integrity
error: GPGME error: Invalid crypto engine
error: archlinux-keyrin: missing required signature

/var/cache/pacman/pkg/arch-linux-keyring.pkg.tar.vst is corrupted (invalid or corrupted package (PGP signature))
Do you want to delete it?
"

Last edited by Robert_Adolph (Today 02:22:06)

Offline

#13 Today 10:23:40

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,151

Online

Board footer

Powered by FluxBB