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.
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.
FS#62768 - Interrupt Signal (Ctrl-C) not taken into account during host resolving
Attached to Project:
Pacman
Opened by Ma Jiehong (jiehong) - Tuesday, 28 May 2019, 17:13 GMT
Last edited by Allan McRae (Allan) - Tuesday, 12 September 2023, 03:46 GMT
Opened by Ma Jiehong (jiehong) - Tuesday, 28 May 2019, 17:13 GMT
Last edited by Allan McRae (Allan) - Tuesday, 12 September 2023, 03:46 GMT
|
DetailsSummary and Info:
When hosts resolving takes a long time (because the network has been lost for example), interrupt signals (Ctrl-C) is displayed (^C), but only taken into account at the end of the resolve time-out (10s). Steps to Reproduce: 1. Make sure you have a package to update; 2. Disable your internet connection; 3. Run `pacman -Su`; 4. After the first host has a resolve time-out, hit Ctrl-C 5. See that "^C" is displayed, but also that "Interrupt signal received" is only displayed at the end of the time-out. Something like that: ``` error: failed retrieving file 'python-pygments-2.4.2-1-any.pkg.tar.xz' from mirror.puzzle.ch : Resolving timed out after 10000 milliseconds ^C (about 10 seconds later) Interrupt signal received ``` Expected: Interrupt Signal should effectively stop pacman in the middle of the host resolution (especially if the time out has been increased). |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 12 September 2023, 03:46 GMT
Reason for closing: Works for me
Additional comments about closing: seems fixed in newer release
Tuesday, 12 September 2023, 03:46 GMT
Reason for closing: Works for me
Additional comments about closing: seems fixed in newer release