Comment 14 for bug 1669578

So aside from the Ubuntu package being outdated (The codebase has indeed changed massively.) the patch we need to get screen working properly is way more intrusive then originally thought and there might even be the case that we have to do some additional lower-level plumbing in the kernel or glibc to get this working. In short, screen tries to perform various operations on the corresponding /dev/pts/<n> paths that the symbolic links under /proc/self/fd/<n> point to and it is not clear whether we can support all of that by just using the symlinks themselves.