Your message dated Wed, 29 Jan 2025 18:27:57 +0100
with message-id <[email protected]>
and subject line Bug #133807: screen user must own pty (breaks with 'su')
has caused the Debian Bug report #133807,
regarding cannot start screen from a su session
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.)


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


Hi,

here is the problem:

# su - bonnaud
Username         Port     From             Latest
bonnaud          pts/104  193.55.51.165    Wed Jun 30 11:00:29 +0200 2004

$ screen
Cannot open your terminal '/dev/pts/8' - please check.

Here is the PTS file:

crw-------    1 root     tty      136,   8 2004-07-05 11:23 /dev/pts/8


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.6-1-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro

Versions of packages screen depends on:
ii  base-passwd                 3.5.7        Debian base system master password
ii  debconf                     1.4.29       Debian configuration management sy
ii  libc6                       2.3.2.ds1-13 GNU C Library: Shared libraries an
ii  libncursesw5                5.4-4        Shared libraries for terminal hand
ii  libpam0g                    0.76-22      Pluggable Authentication Modules l
ii  passwd                      1:4.0.3-29   Change and administer password and

-- debconf information:
  screen/old_upgrade_prompt: false


--- End Message ---
--- Begin Message ---
Source: screen
Source-Version: 4.6.1-1

Upstream claims this was fixed in 4.6.1, per 
https://savannah.gnu.org/bugs/?25214

Best,
Chris

--- End Message ---

Reply via email to