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#2950 - pacman progress meter broken when resized
Attached to Project:
Pacman
Opened by Mark McCoy (mcking) - Monday, 11 July 2005, 22:32 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 16 November 2006, 01:18 GMT
Opened by Mark McCoy (mcking) - Monday, 11 July 2005, 22:32 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 16 November 2006, 01:18 GMT
|
DetailsI use putty to access an arch server through ssh. I regularly use screen to manage several virtual terminals through the ssh connection. Whenever I use the pacman-screen-putty combo to update or install a package, the progressbar during downloads does not work. On an update, instead of the progress meter moving to the next position, a newline is appended to the current line and the entire progress line is reprinted to the screen like this:
%<-------- begin screendump ~ # sudo pacman -S zope Targets: zope-2.7.4-1 Total Package Size: 4.8 MB Proceed with upgrade? [Y/n] :: Retrieving packages from extra... zope-2.7.4-1 [#### ] 29% 1472K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 30% 1483K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 30% 1494K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 30% 1506K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 30% 1516K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 30% 1528K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 31% 1539K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 31% 1550K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 31% 1562K 0.0K/s 00:00: zope-2.7.4-1 [#### ] 31% 1573K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 32% 1584K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 32% 1595K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 32% 1607K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 32% 1618K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 32% 1628K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 33% 1640K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 33% 1651K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 33% 1662K 0.0K/s 00:00: zope-2.7.4-1 [##### ] 33% 1674K 0.0K/s 00:00:00 %< -----------end screen dump I have tried various combinations: * turning on/off ILoveCandy * running through screen on the desktop directly * running through putty w/o screen the only combo that reproduces this is the one in the title: pacman->screen->putty. I will look through the pacman progressbar code in my rare^H^H^H^Hspare time. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Wednesday, 22 November 2006, 04:54 GMT
Reason for closing: Implemented
Additional comments about closing: Fixed in pacman3 - progress meter resizes with the terminal (plus a little artifacting that can't be helped).
Wednesday, 22 November 2006, 04:54 GMT
Reason for closing: Implemented
Additional comments about closing: Fixed in pacman3 - progress meter resizes with the terminal (plus a little artifacting that can't be helped).
Comment by Judd Vinet (judd) -
Wednesday, 24 August 2005, 22:17 GMT
what is your $TERM set to when you run pacman?
Comment by Roman Kyrylych (Romashka) -
Wednesday, 16 August 2006, 10:20 GMT
Pacman works OK in PuTTY. You just should not resize PuTTY window after starting pacman.
Comment by Roman Kyrylych (Romashka) -
Wednesday, 16 August 2006, 10:21 GMT
The same is true for any other terminal window. Resizing it breaks progress meter.