Your message dated Thu, 2 Jan 2025 07:24:18 +1100
with message-id
<CALy8Cw5AfZ60bGS=rKcPBLrRb7+EBDOckfoXod0Ss6YVx=q...@mail.gmail.com>
and subject line Re: Bug#1091673: procps: top <space> :Refresh-Display now
seems to duplicate its action
has caused the Debian Bug report #1091673,
regarding procps: top <space> :Refresh-Display now seems to duplicate its action
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1091673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 2:4.0.2-3
Severity: normal
The version of top in bookworm seems to have changed the processing of
the <space> keybinding for :Refresh-Display, and you can see it
immediately drawing the screen *twice* while registering the current
`top` process as something taking 100% of the CPU.
The former behaviour was to just trigger the timer right now, and
calculate the resource usage and refresh. This was useful. The new
behaviour is to calculate resource usage, refresh, wait 0 seconds,
calculate resource usage (funnily enough, the only thing to take CPU
since 0 seconds ago was top itself), and refresh again. This is not
useful, because it hides the behaviour of the rest of the system,
which had only a tiny chance of being scheduled in those timeslices
where top was recalulating if they were using anything less than 100%
of a core(s).
Tested on a vanilla system just case I had done something funky in
.toprc. manpage doesn't seem to deal with reverting to previous
behaviour, and doesn't mention any change in how <Space> or
:Refresh-Display may have been changed.
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (5, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.10.11+bpo-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages procps depends on:
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u9
ii libncursesw6 6.4-4
ii libproc2-0 2:4.0.2-3
ii libtinfo6 6.4-4
Versions of packages procps recommends:
ii psmisc 23.6-1
procps suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: procps
Version 1:4.0.4-1
On Thu, 2 Jan 2025 at 06:57, Jim Warner <james.war...@comcast.net> wrote:
> That was corrected in release 4.0.4, essentially restoring the former
> 3.3.17 behavior.
>
Closing bug on version 4.0.4-1
- Craig
--- End Message ---
