Bug#904208: itop crashes when option -n is used

Package: itop Version: 0.1-4+b2 running as "itop -n 1" same as "itop -n 5" etc crashes it. Also it leaves the terminal in a really fucked up state, when even "reset" command does not restore normal terminal behavior. as root: itop -a -n 1 shows once the output then crashes: INT

Bug#904207: itop output names are nonsense

Package: itop Version: 0.1-4+b2 on amd64 (smp) The 3rd bug in itop I'm seeing now, on the computer where itop shows any interrupts at all, the output is messed up, as if the lines are wrongly parsed. INT NAME RATE MAX 0 [ 0 0 ] 0 Ints/s (max: 0) 1 [ 0 0 ] 0 Ints/s (max: 0) 5 [ 0 0 ] 0

Bug#904206: itop shows 0 interrupts, on amd64 SMP

Package: itop Version: 0.1-4+b2 running as "itop -a" it shows only 0, after running for even a minute INTNAME RATE MAX 0 [0 0 ] 0 Ints/s (max: 0) on CPU model name : AMD FX(tm)-6300 Six-Core Processor $ uname -a Linux xxx