Public bug reported:
This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630
However, 1333630 is incorrectly marked as fix released, and after a year
of occationally attempting to get someone to notice that 1333630 is not
fixed, I'm giving up and opening a new bug in
I'm YET AGAIN having to build screen from source for a "SUPPORTED"
distro.
HEOO
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
https://bugs.launchpad.net/bugs/1333630
Title:
screen caught signal
I just ran into this issue AGAIN on a different box.
How the hell is this in ANY way LONG TERM **SUPPORT**? A very broadly
used component of the OS CRASHES AND KILLS ALL CONTAINED PROCESS
RANDOMLY.
Me having to compile screen myself for EVERY SUPPORTED instance of
Ubuntu I have would be farcical
So. it's not getting fixed?
I use LTS releases be cause I assumed they were actually supported
(that's what the S in LTS means, or so I thought). Why on earth would
this not be released for all the currently supported variants.
Admittedly, it's rather hard to trigger, but it's a complete
Ok, got screen to compile from source I checked out from git, and it
appears the issue is indeed fixed in 4.2.1-3.
This really, /really/ shouldn't even be in backports, this really needs
to be just a straight-out normal release for all platforms.
Having screen occationally shit the bed and take
I should add, following this recipe here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=681572 still reproduces the issue exactly.
Here is a copy of the repro:
- enable the alternate screen: ^A :altscreen on
- be sure to have at least two windows opened, then split with ^A S
- open Vim
-
This issue is not fixed.
I'm running screen Screen version 4.02.01 (GNU) 28-Apr-14, installed
from screen/trusty-backports, and the issue /still/ periodically
reoccurs (generally when I'm doing a whole bunch of stuff, and is the
most inconvenient.
--
You received this bug notification because
