Package: iotop Version: 0.3-1 Severity: important On i386 system with amd64 kernel, iotop exits without printing anything:
$ iotop -b || echo $? 1 $ Running without -b additionally corrupts the terminal. The problem is that ioprio.find_ioprio_get_syscall_number() uses uname -m to find syscall numbers, which breaks on biarch systems. On i386/amd64 in particular, iotop calls exit_group(2) instead of ioprio_get(2) as a result. Please use something like dpkg-architecture instead of uname. Better yet, use a less fragile method of dispatching syscalls, if you can think of sane one. [There is a mismatch between severity levels suggested by reportbug and http://debian.org/Bugs/Developer. I chose the lower one, please adjust if necessary.] -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.29 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iotop depends on: ii python 2.5.4-2 An interactive high-level object-o ii python-support 1.0.2 automated rebuilding support for P iotop recommends no packages. iotop suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
