Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#61174 - pacman - segmentation fault

Attached to Project: Pacman
Opened by vignesh (vignesh) - Wednesday, 26 December 2018, 03:56 GMT
Last edited by Andrew Gregory (andrewgregory) - Monday, 21 January 2019, 17:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Whenever I try to install a package, for example
pacman -S pandoc
I got this error.
error: segmentation fault

Additional info:
* package version(s) pacman v5.1.1 - libalpm v11.0.1
* config and/or log files etc.


Steps to reproduce:
Try to install any package
pacman -S pandoc
   pacman-debug (1.8 KiB)
This task depends upon

Closed by  Andrew Gregory (andrewgregory)
Monday, 21 January 2019, 17:02 GMT
Reason for closing:  Works for me
Comment by Eli Schwartz (eschwartz) - Wednesday, 26 December 2018, 04:10 GMT
Works for me. Debug logs indicate the issue seems to happen while it is downloading keys from a keyserver.

Could you post the coredumpctl stack trace?
Comment by AK (Andreaskem) - Wednesday, 26 December 2018, 12:21 GMT
The key EEEEE2EEEE2EEEEE seems really odd. Might there be a problem even before pacman actually crashes?

edit: Nevermind, this one is valid. I guess somebody generated a "nice" key on purpose.

If you want to try to fix your problem, you might be able to temporarily set SigLevel = Never in pacman.conf and reinstall the keyring?
Comment by Doug Newgard (Scimmia) - Tuesday, 01 January 2019, 17:39 GMT
If you don't already have that key, something is SERIOUSLY wrong with your system.
Comment by Andrew Gregory (andrewgregory) - Sunday, 20 January 2019, 09:22 GMT
vignesh, can you still reproduce this segfault? Without a stack trace or reproducible case, there is no way to move forward on this.
Comment by vignesh (vignesh) - Monday, 21 January 2019, 16:02 GMT
Immediately after posting this bug on Wednesday, 26 December 2018, 08:56 GMT+5, I reinstalled archlinux. The newly installed archlinux does not have this problem. So I can not reproduce this segfault.

Loading...