*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630
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 <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