Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48191 - htop 2.0 crashes and totally screws running terminal
Attached to Project:
Arch Linux
Opened by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 10:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 15 February 2016, 14:00 GMT
Opened by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 10:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 15 February 2016, 14:00 GMT
|
DetailsWhen running htop in a terminal, would it be a tty or konsole (ruling out this bug to be terminal specific), it crashes and destroy the running terminal: nothing works within the terminal except writings commands, so I can’t scroll to view full output or select the output to copy it…
The output starts like this: *** Error in `htop': free(): invalid next size (fast): 0x0000000000cc8cb0 *** I’ve joined two screen captures: –htop.png is the one with the maximum font size that lets the output fit in height –htop_tiny.png is the one with the lowest available font size, so that the maximum possible of the output content is on the screen (else parts of it disappear at the right). Sorry I can’t get more of it or in an more usable way, but there is literally nothing I can do in that terminal to get more or even a text copy… |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 15 February 2016, 14:00 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#48149
Monday, 15 February 2016, 14:00 GMT
Reason for closing: Duplicate
Additional comments about closing:
update_process_names=1
Can anyone confirm this? So that I could report it upstream.