ERROR: 'pacman' returned a fatal error (1):

lighttn · 2022-02-09 15:50:48

I am trying to install VSCode.

1. The Arch distribution I have is the following.

$ cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"

2. And I cloned visual-studio-code-bin as the following.

$ git clone https://aur.archlinux.org/visual-studio-code-bin.git
Cloning into 'visual-studio-code-bin'...
remote: Enumerating objects: 629, done.
remote: Counting objects: 100% (629/629), done.
remote: Compressing objects: 100% (351/351), done.
remote: Total 629 (delta 280), reused 625 (delta 278), pack-reused 0
Receiving objects: 100% (629/629), 424.98 KiB | 4.52 MiB/s, done.
Resolving deltas: 100% (280/280), done.

3. When I try to make a package, I got an error regarding the pacman.

$ makepkg -si
==> Making package: visual-studio-code-bin 1.64.1-1 (Wed 09 Feb 2022 03:19:10 PM CET)
==> Checking runtime dependencies...
/usr/bin/pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/bin/pacman)
/usr/bin/pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/libalpm.so.13)
==> ERROR: 'pacman' returned a fatal error (1):

How can I do now?

Trilby · 2022-02-09 16:04:03

It looks like you have done a partial upgrade. You have a current / recent pacman version but you do not have the current glibc installed. You'll either need to download a pacman-static binary then use that to properly upgrade your system, or you can boot into a live iso, mount your partitions, and use the live iso to update the mounted system (e.g., `pacman -r /mnt -Syu`).

Posting your complete pacman.log would help us identify when/how things went wrong to see if there will be other problems to fix.

Trilby · 2022-02-09 16:17:29

If pacman isn't working, the OP can't use pacman to run that check on glibc. The following would provide some information - but regardless of the outcome, getting a functional pacman would be step 0 in fixing things:

grep -A 1 VERSION /var/lib/pacman/local/glibc-*/desc

V1del · 2022-02-09 16:20:13

Yeah realised that now as well and wanted to self censor

lighttn · 2022-02-10 12:00:30

Hi Trilby, Here is the information.

$ grep -A 1 VERSION /var/lib/pacman/local/glibc-*/desc
%VERSION%
2.29-1

schard · 2022-02-10 12:15:27

Yeah, as Trilby already mentioned, partial upgrades are not supported.
Boot a live medium and use its pacman to fully upgrade your installed system.

lighttn · 2022-02-10 12:31:02

Here are some most rescent pacman.log file.

[2021-12-17 10:18] [PACMAN] Running 'pacman -Syu'
[2021-12-17 10:18] [PACMAN] synchronizing package lists
[2021-12-17 10:18] [PACMAN] starting full system upgrade
[2021-12-17 10:18] [PACMAN] Running 'pacman -Syu'
[2021-12-17 10:18] [PACMAN] synchronizing package lists
[2021-12-17 10:18] [PACMAN] starting full system upgrade
[2021-12-17 10:19] [PACMAN] Running 'pacman --color auto -Sy'
[2021-12-17 10:19] [PACMAN] synchronizing package lists
[2021-12-17 10:19] [PACMAN] Running 'pacman --color auto -S -u'
[2021-12-17 10:19] [PACMAN] starting full system upgrade
[2021-12-17 10:20] [PACMAN] Running 'pacman -Syu'
[2021-12-17 10:20] [PACMAN] synchronizing package lists
[2021-12-17 10:20] [PACMAN] starting full system upgrade
[2021-12-17 10:34] [PACMAN] Running 'pacman -Rdd libxfont python2-pyqt4 python2>
[2021-12-17 10:34] [ALPM] transaction started
[2021-12-17 10:34] [ALPM] removed libxfont (1.5.4-1)
[2021-12-17 10:34] [ALPM] removed python2-pyqt4 (4.12.1-1)
[2021-12-17 10:34] [ALPM] removed python2-pyqt5 (5.12.2-1)
[2021-12-17 10:34] [ALPM] transaction completed
[2021-12-17 10:34] [ALPM] running 'systemd-update.hook'...
[2021-12-17 10:34] [PACMAN] Running 'pacman -Rdd libxfont python2-pyqt4 python2>
[2021-12-17 10:34] [PACMAN] Running 'pacman -Syu'
[2021-12-17 10:34] [PACMAN] synchronizing package lists
[2021-12-17 10:34] [PACMAN] starting full system upgrade
[2021-12-17 10:42] [PACMAN] Running 'pacman -S archlinux-keyring'
[2021-12-17 10:47] [PACMAN] Running 'pacman -Sy archlinux-keyring'
[2021-12-17 10:47] [PACMAN] synchronizing package lists
[2021-12-17 10:48] [PACMAN] Running 'pacman -Syu'
[2021-12-17 10:48] [PACMAN] synchronizing package lists
[2021-12-17 10:48] [PACMAN] starting full system upgrade
[2021-12-17 11:10] [PACMAN] Running 'pacman -U'
[2021-12-17 11:11] [PACMAN] Running 'pacman -U'
[2021-12-17 11:11] [PACMAN] Running 'pacman -U pacman'
[2021-12-17 11:17] [PACMAN] Running 'pacman -S pacman'
[2021-12-17 11:17] [ALPM] transaction started
[2021-12-17 11:17] [ALPM] warning: /etc/pacman.conf installed as /etc/pacman.co>
[2021-12-17 11:17] [ALPM] upgraded pacman (5.1.3-1 -> 6.0.1-2)
[2021-12-17 11:17] [ALPM] transaction completed
[2021-12-17 11:17] [ALPM] running 'systemd-update.hook'...

Trilby · 2022-02-10 12:52:19

Portions of logs aren't so helpful. I requested the complete pacman log which should be posted to a file sharing site and linked to here if you want help identifying where you went wrong. But I'd also be curious about all the previous error messages from pacman that you have not told us about. Even just from that excerpt, there are indications of failed / interrupted attempts at upgrading as well as an odd -Rdd command which was most likely your attempt at working around some problem or error message.

But in any case, that's all just for identifying the original cause of the problem so that you can learn not to do it again. None of that is actually directly relevant to the solution which you've already been provided with. You should really prioritize fixing your system first - at least to a point of basic functionality of pacman. Then if you still want to, we can investigate the origin of the problems and ensure there aren't other lingering issues.

Last edited by Trilby (2022-02-10 12:58:30)

Scimmia · 2022-02-10 13:01:54

What mirror is at the top of your mirrorlist? It looks to me like you're syncing to an extremely out of date mirror, but manually installed pacman from a up to date one.

lighttn · 2022-02-10 14:28:27

Hi Trilby, Please find the pacman log file at the following link.

https://drive.switch.ch/index.php/s/RHdspnD7UnO3bdf

Scimmia · 2022-02-10 18:15:06

So you haven't actually updated this system in almost 3 years. Then, when the update attempts failed, you manually updated pacman, which broke it. Do I have that right?

Anyway, it was already explained that you need to update your system with an external pacman now. When you get errors, seek help for them, don't ignore them or do partial updates on your own.

lighttn · 2022-02-11 13:59:57

Hi Fellow, Thank you for your comments. Sorry, I just didn't get your question about mirror, since I am a beginner. What do you mean mirror or mirrorlist? Regarding the system update, I will try it.

Arch Linux

#1 2022-02-09 15:50:48

ERROR: 'pacman' returned a fatal error (1):

#2 2022-02-09 16:04:03

Re: ERROR: 'pacman' returned a fatal error (1):

#3 2022-02-09 16:17:29

Re: ERROR: 'pacman' returned a fatal error (1):

#4 2022-02-09 16:20:13

Re: ERROR: 'pacman' returned a fatal error (1):

#5 2022-02-10 12:00:30

Re: ERROR: 'pacman' returned a fatal error (1):

#6 2022-02-10 12:15:27

Re: ERROR: 'pacman' returned a fatal error (1):

#7 2022-02-10 12:31:02

Re: ERROR: 'pacman' returned a fatal error (1):

#8 2022-02-10 12:52:19

Re: ERROR: 'pacman' returned a fatal error (1):

#9 2022-02-10 13:01:54

Re: ERROR: 'pacman' returned a fatal error (1):

#10 2022-02-10 14:28:27

Re: ERROR: 'pacman' returned a fatal error (1):

#11 2022-02-10 18:15:06

Re: ERROR: 'pacman' returned a fatal error (1):

#12 2022-02-11 13:59:57

Re: ERROR: 'pacman' returned a fatal error (1):

Board footer