Package: nm.debian.org Severity: minor I was recently talking with jmw, and told him I was surprised to get an NM assigned as I had set myself as inactive, although I didn't lower my number of available slots. He asked me to file a bug, because from the FD view, he does not even see the "active" column.
I am marking the bug as minor as it _might_ be right; turns out, my "active" bit was still marked as present. There might be a usability issue somewhere, but I cannot pin-point it. But I do believe this brings unnecessary redundancy - Why do we have both selectors? Isn't "available=false" equivalent to "slots=0"? Thanks. -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
