Public bug reported: I'm pretty sure nothing will happen by posting this, but it's not like I should just leave it ...
That error is still well alive despite the numerous reports. The package version 4.4.0-6 (GNU version 4.04.00; the current one at the time of posting this), designated for Zesty, installed just fine on 16.04 LTS through a DEB file from official repo but provided absolutely nothing related to this issue by how easy it still is to replicate: as §root§ (doing this as an user with §sudo su§ permissions not tested), §su§ into another user and try to run §screen§, doesn't matter which parameters used as long as the parameter doesn't make §screen§ just reply without executing anything. As §root§ no problems, obviously. I remember well, on either 12.04 LTS or 14.04 LTS, that I managed to get a version of §screen§ where this and the §chmod 777§ problem with §/var/run/screen/§ were fixed by no longer using §/var/run/screen/§, but some subfolder under §~/.screen/§, disregarding the fact the executing user was, usually, logged into by §root§. Don't ask me to help fix this by writing C[++], I can't even write a Hello World program, although I can often interpret what the existing line does. lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ** Affects: screen (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644636 Title: Cannot open your terminal /dev/pts/X - please check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1644636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs