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#22156 - Pacman segfaults on system upgrade

Attached to Project: Pacman
Opened by Roger John Robertson Jr. (rjrjr) - Monday, 20 December 2010, 18:54 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 12 January 2011, 05:20 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version 3.4.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Pacman Segmentation Fault

Additional info:
* package version(s)
* config and/or log files etc.
pacman 3.4.1 x86_64

Steps to reproduce:
run pacman -Syu
   debug.txt (10.9 KiB)
   pacman.log (201 KiB)
   pacman.conf (2.5 KiB)
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 12 January 2011, 05:20 GMT
Reason for closing:  Works for me
Additional comments about closing:  Reopen if it is reproducible.
Comment by Ionut Biru (wonder) - Monday, 20 December 2010, 19:49 GMT
related to  FS#22102  ?
Comment by Roger John Robertson Jr. (rjrjr) - Monday, 20 December 2010, 20:18 GMT
Could be. I found that if I run pacman -Syy and then pacman -Syu the issue resolves. Not sure if that's a fix or not.
Comment by Allan McRae (Allan) - Tuesday, 21 December 2010, 04:00 GMT
Looks like something in you sync database was broken, but given you have run -Syy those files are now gone so there is not much more we can do here but assume it was the issues that has already been fixed in git.

Looking at all the recent segfault bug reports, the downloaded database tarballs seem fine (same file size as that on the server), so the error appears limited to the extracted files. I wonder why we are seeing so many of these lately?
Comment by Xavier (shining) - Wednesday, 22 December 2010, 19:32 GMT
This is quite curious indeed.
One way would be to examine all the different corrupted db, and then look for a common pattern between the different setup/usage that led to it.

So any user who encountered the issue is welcome to provide the tarball of /var/lib/pacman/sync/ as well as any relevant details (usage of pac cage or similar, all info about filesystem : type, option, eventual errors, and any problem like recent crash/lockup, etc).
Comment by Roger John Robertson Jr. (rjrjr) - Wednesday, 22 December 2010, 20:38 GMT
Yeah, unfortunately I guess my "fix" of pacman -Syy erased the source of the problem. If it happens again I'll definitely post the files you requested.
Comment by Quentin Peten (lpc) - Monday, 27 December 2010, 10:08 GMT
I had the same problem.
Mine was due to the some empty file in /var/lib/pacman/sync/*/HERE.

But I haven't been able to reproduce the bug by empying the file myself, pacman detecting it. ("L'archive * est corrompue; Voulez-vous l'effacer ?")
Unfortunately I also fixed it with pacman -Syy before going here...

Hoping it helps...

Loading...