screen caught signal 11 core dumped

[Fake Name]

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 hope of someone actually noticing.

Basically, the version of screen in the 14.04 "long term support" release can occasionally segfault, taking all contained shell sessions down with it. This is extremely annoying if you use screen extensively, and having to compile screen from source on every ubuntu install I use is ridiculous.

The underlying issue was a bug in GNU screen: https://savannah.gnu.org/bugs/index.php?35757

This was fixed fully one year ago. However, the version of screen that's distributed as part of ubuntu is apparently **10** years old (Screen version 4.01.00devel (GNU) 2-May-06).

Since 14.04 is ostensibly still supported, can someone please actually support it, and upgrade the version of screen to something from the last year?

There is screen 4.2.1 in trusty/backports, but 1) this bug was not fixed until 4.3.0, and 2) this is a core shell util, I shouldn't have to go hunting for a additional repository to get a functional version of the GNU tools that's usually installed by default.

Other:

1 durr@xenbox:~⟫ lsb_release -rd
Description: Ubuntu 14.04.4 LTS
Release: 14.04
durr@xenbox:~⟫

durr@xenbox:~$ apt-cache policy screen
screen:
  Installed: 4.1.0~20120320gitdb59704-9
  Candidate: 4.1.0~20120320gitdb59704-9
  Version table:
     4.2.1-2~ubuntu14.04.1 0
        100 http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages
 *** 4.1.0~20120320gitdb59704-9 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

[Axel Beckert (xtaran)]

Hi,

Fake Name wrote:
> This is a duplicate of
> https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630
>
> However, 1333630 is incorrectly marked as fix released,

No. It is correctly marked as "fix released in Ubuntu" since this has
been fixed "in Ubuntu" since release 15.04 Vivid.

> 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
> hope of someone actually noticing.

The question is: Is this bug severe enough to get the fix backported
into Trusty's 4.1.0~20120320gitdb59704-9 version. So far nobody seems
to have cared enough to make that effort. It seems no security issue,
so the only way to get this fixed is via a "stable release update".
See
http://packaging.ubuntu.com/html/security-and-stable-release-updates.html#stable-release-updates
and https://wiki.ubuntu.com/StableReleaseUpdates for details about
which bugs can get fixed in released versions of Ubuntu and how this
should be done.

> This was fixed fully one year ago. However, the version of screen that's
> distributed as part of ubuntu

Not "ubuntu", but "Ubuntu 14.04".

> is apparently **10** years old (Screen version 4.01.00devel (GNU)
> 2-May-06).

No. That was a "devel"opment snapshot where the version hasn't been
bumped in the source code. Please the package version number which
clearly states the date of the snapshot (from 2012).

> Since 14.04 is ostensibly still supported, can someone please actually
> support it, and upgrade the version of screen to something from the last
> year?

That probably needs someone creating a patched package, getting it
reviewed and asking for inclusion into Ubuntu 14.04 LTS. (JFTR: I
won't do that.)

> There is screen 4.2.1 in trusty/backports, but 1) this bug was not fixed
> until 4.3.0,

But it has been fixed by cherry-picking the fix in the package version
4.2.1-3. It's though true that only contains the package version one
before that: 4.2.1-2~ubuntu14.04.1 -- an update there might be easier
to achieve since 15.04 Vivid already has 4.2.1-3.

I'll now mark this as duplicate of
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630 and
hence as "fixed in Ubuntu" (which is not the same as "fixed in the
current LTS release").

If you really want to get this fixed in Ubuntu 14.04 LTS, please
follow the instructions in the guides listed above instead of opening
new duplicates for already existing bug reports. Thanks!

  Regards, Axel
--
 ,''`. | Axel Beckert <email address hidden>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
  `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE

[Fake Name (lemuix)]

> Hi,

> Fake Name wrote:
> > This is a duplicate of
> > https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630
> >
> > However, 1333630 is incorrectly marked as fix released,

> No. It is correctly marked as "fix released in Ubuntu" since this has
> been fixed "in Ubuntu" since release 15.04 Vivid.

So the "Supported" LTS is not "Ubuntu"?

> > 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
> > hope of someone actually noticing.

> The question is: Is this bug severe enough to get the fix backported
> into Trusty's 4.1.0~20120320gitdb59704-9 version. So far nobody seems
> to have cared enough to make that effort. It seems no security issue,
> so the only way to get this fixed is via a "stable release update".
> See
> http://packaging.ubuntu.com/html/security-and-stable-release-updates.html#stable-release-updates
> and https://wiki.ubuntu.com/StableReleaseUpdates for details about
> which bugs can get fixed in released versions of Ubuntu and how this
> should be done.

> > This was fixed fully one year ago. However, the version of screen that's
> > distributed as part of ubuntu

> Not "ubuntu", but "Ubuntu 14.04".

Still Ubuntu. Also, still "Supported"

> > is apparently **10** years old (Screen version 4.01.00devel (GNU)
> > 2-May-06).

> No. That was a "devel"opment snapshot where the version hasn't been
> bumped in the source code. Please the package version number which
> clearly states the date of the snapshot (from 2012).

> > Since 14.04 is ostensibly still supported, can someone please actually
> > support it, and upgrade the version of screen to something from the last
> > year?

> That probably needs someone creating a patched package, getting it
> reviewed and asking for inclusion into Ubuntu 14.04 LTS. (JFTR: I
> won't do that.)

> > There is screen 4.2.1 in trusty/backports, but 1) this bug was not fixed
> > until 4.3.0,

> But it has been fixed by cherry-picking the fix in the package version
> 4.2.1-3. It's though true that only contains the package version one
> before that: 4.2.1-2~ubuntu14.04.1 -- an update there might be easier
> to achieve since 15.04 Vivid already has 4.2.1-3.

Whatever has been claimed to have occurred, it didn't actually fix the crash, and I still periodically encounter it and have it eat my screen session on a new VM until i remember I have to build screen from source.

> I'll now mark this as duplicate of
> https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630 and
> hence as "fixed in Ubuntu" (which is not the same as "fixed in the
> current LTS release").

> If you really want to get this fixed in Ubuntu 14.04 LTS, please
> follow the instructions in the guides listed above instead of opening
> new duplicates for already existing bug reports. Thanks!

I want it fixed in Ubuntu, not "just that one version of ubuntu". From what you're saying the only version of "Ubuntu" that is *actually* ubuntu is whatever the latest version is, the rest are just ignored? What part of that actually has support?

[Fake Name (lemuix)]

If you want to mark this as a duplicate, that's fine, but at least re-open the old bug. Until that's done, this is *not* a duplicate, the reporting issue has not been solved (hey look, that's for 14.04 too!).

[Axel Beckert (xtaran)]

Hi again,

Fake Name wrote:
> > > This is a duplicate of
> > > https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630
> > >
> > > However, 1333630 is incorrectly marked as fix released,
>
> > No. It is correctly marked as "fix released in Ubuntu" since this has
> > been fixed "in Ubuntu" since release 15.04 Vivid.
>
> So the "Supported" LTS is not "Ubuntu"?

No. On Launchpad, just "fix released in Ubuntu" without explicit
version means "There is one or more (not necessarily released) Ubuntu
versions where a fix is included". That could be the current
development version, i.e. currently 16.04 which is not yet released.

> > > There is screen 4.2.1 in trusty/backports, but 1) this bug was not fixed
> > > until 4.3.0,
>
> > But it has been fixed by cherry-picking the fix in the package version
> > 4.2.1-3. It's though true that only contains the package version one
> > before that: 4.2.1-2~ubuntu14.04.1 -- an update there might be easier
> > to achieve since 15.04 Vivid already has 4.2.1-3.
>
> Whatever has been claimed to have occurred, it didn't actually fix the
> crash,

It did. Just not in Ubuntu 14.04.

> > I'll now mark this as duplicate of
> > https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1333630 and
> > hence as "fixed in Ubuntu" (which is not the same as "fixed in the
> > current LTS release").
>
> > If you really want to get this fixed in Ubuntu 14.04 LTS, please
> > follow the instructions in the guides listed above instead of opening
> > new duplicates for already existing bug reports. Thanks!
>
> I want it fixed in Ubuntu,

Again: It is fixed in Ubuntu, since Ubuntu 15.04.

> not "just that one version of ubuntu".

But that's what "fixed in Ubuntu" means on Launchpad.

> From what you're saying the only version of "Ubuntu" that is
> *actually* ubuntu is whatever the latest version is, the rest are
> just ignored?

No, that's not what I'm saying. Please read the links I posted in my
previous comment to see how to get bugs fixed in _released_ versions
of Ubuntu.

Fake Name wrote:
> If you want to mark this as a duplicate, that's fine, but at least re-
> open the old bug.

No. Someone with the proper permissions (neither you nor I have them)
needs to explicitly mark the bug report as affecting 14.04 LTS and
open it for that release only. I won't poke those people, so it's up
to you to contact them. See the links I posted in my previous comment
for how to do that.

> Until that's done, this is *not* a duplicate,

It is.

> the reporting issue has not been solved

It has. Just not in 14.04.

> (hey look, that's for 14.04 too!).

Once again: Please read the links I posted in my previous comment to
see how to get bugs fixed in _released_ versions of Ubuntu. Opening
duplicates of existing bug reports is _neither_ the way to do that nor
is just whinging around in closed bug reports.

  Regards, Axel
--
 ,''`. | Axel Beckert <email address hidden>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
  `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE

[Fake Name (lemuix)]

The original bug report was "The version of screen in X has a (serious) issue".

The "response" was "Ok, we fixed it in Y".

The version in X, where the problem was originally encountered is still broken and unfixed. Despite this fact, the bug report was closed.

I don't know how you can consider that fixed.

If Launchpad defines "Ubuntu" to be "only the latest version of ubuntu and not any of the LTS versions", well... ok? I don't think that definition is going to be too widely agreed on anywhere else, where "ubuntu" means all the OS releases.

> No. Someone with the proper permissions (neither you nor I have them)
> needs to explicitly mark the bug report as affecting 14.04 LTS and
> open it for that release only. I won't poke those people, so it's up
> to you to contact them. See the links I posted in my previous comment
> for how to do that.

Is that not the EXPLICIT purpose of this ENTIRE bug tracker? To let the appropriate people know that there is, I dunno, a bug? There is an *specific* category for *just* this *one* piece of software.

WTF is the "Screen on Ubuntu" bug tracker for if NOT telling the people involved in managing the screen package on Ubuntu that there is a problem?

Furthermore, the *original* bug was explicitly described as occurring on 14.04, so there has never been, as far as I'm aware, the contention that it affected any *other* platform.

---

As an aside, from the "7.2. Stable Release Updates" subheading on that page:

> We also allow updates to releases where a package has a high impact bug such as
> a severe regression from a previous release or a bug which could cause data loss.
> Due to the potential for such updates to themselves introduce bugs we only allow
> this where the change can be easily understood and verified.

I have *personally* had data loss from this bug, due to screen eating all my processes when doing interactive
data processing and having screen segfault.

[Axel Beckert (xtaran)]

Fake Name wrote:
> The original bug report was "The version of screen in X has a (serious)
> issue".
>
> The "response" was "Ok, we fixed it in Y".
>
> The version in X, where the problem was originally encountered is still
> broken and unfixed. Despite this fact, the bug report was closed.

Which is the normal procedere.

> I don't know how you can consider that fixed.

Then I can't help any further.

> If Launchpad defines "Ubuntu" to be "only the latest version of ubuntu

As explained in my previous comment, it's broader than that.

> and not any of the LTS versions", well... ok? I don't think that
> definition is going to be too widely agreed on anywhere else, where
> "ubuntu" means all the OS releases.

Face it. (It's the same in Debian, too, btw.)

> > No. Someone with the proper permissions (neither you nor I have them)
> > needs to explicitly mark the bug report as affecting 14.04 LTS and
> > open it for that release only. I won't poke those people, so it's up
> > to you to contact them. See the links I posted in my previous comment
> > for how to do that.
>
> Is that not the EXPLICIT purpose of this ENTIRE bug tracker? To let the
> appropriate people know that there is, I dunno, a bug?

Yes, and most of those bugs only get fixed in a _future_ release of
Ubuntu.

> Furthermore, the *original* bug was explicitly described as occurring on
> 14.04, so there has never been, as far as I'm aware, the contention that
> it affected any *other* platform.

It is assumed that, if the bug is reported in one version, it is also
in all future versions until the version where it has been fixed, i.e.
all future versions if there's no fix yet.

> As an aside, from the "7.2. Stable Release Updates" subheading on that
> page:
>
> > We also allow updates to releases where a package has a high impact bug such as
> > a severe regression from a previous release or a bug which could cause data loss.
> > Due to the potential for such updates to themselves introduce bugs we only allow
> > this where the change can be easily understood and verified.
>
> I have *personally* had data loss from this bug, due to screen
> eating all my processes when doing interactive data processing and
> having screen segfault.

Please read "3. Procedure".

Also note that the very first requirement for an bugfix update in a
released version in Ubuntu is that the bug report _is_ marked as
"Fix released", at least in the current development version:

  3. Procedure

    1. Check that the bug is fixed in the current development release,
    and that its bug task is "Fix Released".

Now please go and follow that procedure, preferably in
https://bugs.launchpad.net/bugs/1333630 and not here in
https://bugs.launchpad.net/bugs/1562658

  Regards, Axel
--
 ,''`. | Axel Beckert <email address hidden>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
  `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE