Control: found 1.2.1-4 On 2026-02-10 04:27:13 -0500, Thomas Dickey wrote: > On Wed, Feb 04, 2026 at 07:44:07PM -0500, Thomas Dickey wrote: > > On Wed, Feb 04, 2026 at 10:53:32AM +0100, Chris Hofstaedtler wrote: > > > I object to this statement. I filed bugs in the past so each piece > > > of software can evaluate if it needs/wants changes. If a change is > > > wanted/warranted/useful at all is in the hands of the software > > > authors. > > > > Which bug report did you file against xterm, proposing to remove utmp? > > silence tells me that there was none.
At least, not in Debian. > Now... xterm's used libutempter since January 2000. If the package > for libutempter0 is updated to ensure that /run/utmp exists, the > "who" program can report the information that libutempter would write > to it: > > who /run/utmp But note that this would not solve the issue with loginctl (for "wall" and "shutdown", which do not use /run/utmp, AFAIK). > apt-cache says there are a few other programs using libutempter: > > libutempter0 > Reverse Depends: > libutempter-dev > xwrited > xterm > xfce4-terminal > mosh > guake > > screen apparently does not, but since its upstream terminfo file is long > out of date, I see that is due to neglect rather than deliberate design. The use of utempter in screen was removed last year because /run/utmp was no longer existing, so that an error was output, and this was corrupting the main screen. screen (4.9.1-2) unstable; urgency=medium * Team upload (debian/ namespace). * 63-add-utempter-switch: fix variable name * Stop building with utempter * Disable utmp writing (Closes: #1104514) * Update ptymode to 0600 in line with rest of the system -- Chris Hofstaedtler <[email protected]> Sat, 10 May 2025 22:28:23 +0200 -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
