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#25852 - Pacman segfaults when trying to update the system

Attached to Project: Pacman
Opened by Alexander Yakovlev (Oreolek) - Thursday, 01 September 2011, 10:03 GMT
Last edited by Dan McGee (toofishes) - Thursday, 06 October 2011, 15:04 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Low
Reported Version 3.5.3
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Pacman segfaults when trying to update the system. Log is attached.
The system is a clean arch aug/2011.
   pacman.out (49.2 KiB)
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 06 October 2011, 15:04 GMT
Reason for closing:  Deferred
Additional comments about closing:  Likely fixed in 4.0 with switch to libcurl, please reopen if this is not true.
Comment by Jesse Frey (jessef) - Thursday, 01 September 2011, 16:34 GMT
The same thing happended to me. attached is my log. my system was installed mid July so it was not a clean install.
also I have pacman 3.5.4
   pacman.dbg (9.6 KiB)
Comment by Dave Reisner (falconindy) - Sunday, 04 September 2011, 14:31 GMT
The mirror that this crashes on is completely hosed and contains lots of 0 byte files:

ftp://mirrors.ustc.edu.cn/archlinux/core/os/x86_64
Comment by Jesse Frey (jessef) - Sunday, 04 September 2011, 16:16 GMT
I don't think that I would have used that mirror I only use the US mirrors. even still pacman should not segfault if it downloads a bad file. It works now but it is just not that great a thing to happen.
Comment by Dave Reisner (falconindy) - Sunday, 04 September 2011, 16:23 GMT
jessef: your logfile doesn't even have evidence of a crash in it. Please open a separate bug report unless you can reproduce _this_ particular crash.
Comment by Jesse Frey (jessef) - Sunday, 04 September 2011, 17:43 GMT
Sorry I now see that my log shows no crash. I can't seem to find avoidance of a crash but pacman definitely crashed and told me to please file a bug report which is when I saw this one. anyway at this point I can't file a separate report because I can't reproduce the crash and have no evidence that it actually crashed, sorry.
Comment by Dave Reisner (falconindy) - Monday, 12 September 2011, 17:39 GMT
ping?
Comment by Dave Reisner (falconindy) - Thursday, 22 September 2011, 17:39 GMT
Please retest this on pacman 4.0.0 rc2:

http://mailman.archlinux.org/pipermail/pacman-dev/2011-September/014415.html

Loading...