Your message dated Sat, 16 May 2026 22:57:10 +0200
with message-id <[email protected]>
and subject line Closing: not found in 5.0.1
has caused the Debian Bug report #645202,
regarding how to freeze screen in four simple steps
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 [email protected]
immediately.)


-- 
645202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645202
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: screen
Version: 4.0.3-14
Severity: normal

Hi,

1. start screen: screen
2. spawn another window: Ctrl-a c
3. go to the window list: Ctrl-a "
4. kill a window: Ctrl-a : at 0 kill

Now screen is unresponsive with "Window 0 (bash) killed." message in the
status line.  I think this is a bug.

Thanks,
Feri.

-- System Information:
Debian Release: 6.0.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.38-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages screen depends on:
ii  dpkg                      1.15.8.11      Debian package management system
ii  install-info              4.13a.dfsg.1-6 Manage installed documentation in 
ii  libc6                     2.11.2-10      Embedded GNU C Library: Shared lib
ii  libncursesw5              5.7+20100313-5 shared libraries for terminal hand
ii  libpam0g                  1.1.1-6.1      Pluggable Authentication Modules l

screen recommends no packages.

screen suggests no packages.

-- debconf information:
  screen/old_upgrade_prompt: false



--- End Message ---
--- Begin Message ---
notfound 645202 5.0.1-1
thanks

Hi,

This bug was likely fixed a long time ago, and is unable to be reproduced on the latest unstable.

Cheers,
Peter Dey

--- End Message ---

Reply via email to