*** This bug is a duplicate of bug 1333630 ***
https://bugs.launchpad.net/bugs/1333630
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 <a...@debian.org>, 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562658
Title:
screen caught signal 11 core dumped
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1562658/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
