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#26118 - [pacman] 4.0.0rc2 segfault while fetching pgp key

Attached to Project: Pacman
Opened by Geert Hendrickx (ghen) - Monday, 26 September 2011, 07:14 GMT
Last edited by Dan McGee (toofishes) - Thursday, 06 October 2011, 04:39 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version git
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Pacman 4.0.0rc2 reproducible segfault when upgrading libreoffice (-Syu).

SigLevel = Optional TrustAll

Earlier pkg updates (with signature verification) have been succesful though.

[09:02:39] debug: found cached pkg: /var/cache/pacman/pkg/libreoffice-writer-3.4.3-2-x86_64.pkg.tar.xz
[09:02:39] debug: sig data: iQEcBAABAgAGBQJOfzV2AAoJEJRlerIPKgkrOywH/1IiyiOKngYvD0KiBLmuIO3ynkpcUweXaYmvKXMCW0HB/FbS8DIuoCelSNz/OISoSjzHt1aA1qgcFK4xd/jtBorDwoa+wrG647OZC6Yu2iYg/GEVoMyf7kh3PW4MbFjA0grb/UYlQ1mGXYALZb5IKg9TPHg97X5wZ+TjtioGnTOsZTN6SbMoKTRe1T+PZZTAguUe2xAbL5DGdxDFVlbRb+2kRrBHC2FZoewe0YxypJS6Jm/SVQD8BbwTAWCmwSlgVxHfa7RBXCcT0PniuLKWj0BzbOhXPXameQ8V2JyzW8cjHQoCWqMzZrC4KjPIKxuYoNHbYekl6CqPJHOGEvHnJrI=
[09:02:39] debug: checking signatures for /var/cache/pacman/pkg/libreoffice-writer-3.4.3-2-x86_64.pkg.tar.xz
[09:02:39] debug: checking signature for /var/cache/pacman/pkg/libreoffice-writer-3.4.3-2-x86_64.pkg.tar.xz
[09:02:39] debug: 1 signatures returned
[09:02:39] debug: fingerprint: 94657AB20F2A092B
[09:02:39] debug: summary: key missing
[09:02:39] debug: status: No public key
[09:02:39] debug: timestamp: 1316959606
[09:02:39] debug: exp_timestamp: 0
[09:02:39] debug: validity: unknown; reason: Success
[09:02:39] debug: key lookup failed, unknown key
[09:02:39] debug: signature is not valid
[09:02:39] debug: looking up key 94657AB20F2A092B locally
[09:02:39] debug: key lookup failed, unknown key
[09:02:39] error: libreoffice-en-US: key "94657AB20F2A092B" is unknown
[09:02:39] debug: looking up key 94657AB20F2A092B remotely
[09:03:06] debug: key lookup failed, unknown key
error: segmentation fault
Internal pacman error: Segmentation fault.
Please submit a full bug report with --debug if appropriate.

This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 06 October 2011, 04:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in git
Comment by Karol Błażewicz (karol) - Monday, 26 September 2011, 07:47 GMT
I've installed 32-bit libreoffice w/o a problem.
Comment by Geert Hendrickx (ghen) - Monday, 26 September 2011, 07:53 GMT
The upgrade succeeded after a few retries (without changing anything on my part).
So the segfault was probably triggered by some intermittent network issue?
Comment by Karol Błażewicz (karol) - Monday, 26 September 2011, 07:59 GMT
The package has been updated yesterday, so maybe there was some mirror sync issue?

[09:02:39] debug: found cached pkg: /var/cache/pacman/pkg/libreoffice-writer-3.4.3-2-x86_64.pkg.tar.xz

I think it means the package is already downloaded. Did you try removing it and downloading again?
Comment by Geert Hendrickx (ghen) - Monday, 26 September 2011, 08:16 GMT
The package was in cache from a previous attempt, I did not remove/re-download it when it succeeded.

There is a 27 second delay at "debug: looking up key 94657AB20F2A092B remotely", after which it segfaults immediatly. So I imagine some PGP keyserver could not be reached (timeout), and pacman cannot handle that scenario?
Comment by Allan McRae (Allan) - Monday, 26 September 2011, 08:35 GMT
Sounds like the issue fixed by this commit:
http://projects.archlinux.org/pacman.git/commit/?id=907e8af5
Comment by Geert Hendrickx (ghen) - Monday, 26 September 2011, 09:06 GMT
Look like it, yes.

Can't reproduce it now anymore, anyway, so this can probably be closed (until I re-encounter it).

Loading...