[Bug 867507] Re: [needs-packaging] pypy
Is there any chance you can add a PyPy3 version to this PPA? Right now, there's no nice way to get system-wide installs of PyPy3 on Ubuntu that I can find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867507 Title: [needs-packaging] pypy To manage notifications about this bug go to: https://bugs.launchpad.net/pypy/+bug/867507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present
Manually adding tmpfs /tmp tmpfs defaults 0 0 to fstab does seem to be a functional workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091792 Title: The disk drive for /tmp is not ready yet or not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present
I'm pretty sure I'm still seeing the on a up-to-date trusty install as well. This is in a rented dedicated server too, so it's extra spectacularly annoying, because I have to wait for someone to go press a key on the keyboard to fix it. mountall -v says "mountall 2.49" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091792 Title: The disk drive for /tmp is not ready yet or not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
What part of this is "fixed"? Anyways, xen can apparently support efi-booting as a efi executable directly, but for some reason ubuntu doesn't ship the "xen.efi" (see https://wiki.xenproject.org/wiki/Xen_EFI)? While I understand that fixing this is kind of out of the scope of the ubuntu packager people, at least mark it "wontfix" or something. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
@martin.von.wittich - Get used to pulling screen sources and compiling it yourself. No one at ubuntu has any interest in actually supporting their "supported" OS. It's fortunately pretty easy to build a non-fucked version of screen: - `apt-get install build-essential ncurses-dev` to get the dependencies. - Grab the latest from http://ftp.gnu.org/gnu/screen/ (currently screen-4.3.1.tar.gz) - `tar -xvf screen-4.3.1.tar.gz && cd screen-4.3.1 && ./configure && make -j4 && sudo make install` will make and install a version of screen without 2 year old game breaking bugs. Then, you just have to make sure you don't accidentally let the "SUPPORTED" broken version get installed, because it can clobber the manual version that actually doesn't periodically kill all your processes, because fuck bothering to actually fix things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562658] Re: screen caught signal 11 core dumped
*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630 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. -- 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
[Bug 1562658] Re: screen caught signal 11 core dumped
*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630 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!). -- 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
[Bug 1562658] Re: screen caught signal 11 core dumped
*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630 > 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? -- 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
[Bug 1562658] [NEW] screen caught signal 11 core dumped
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 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 ** Affects: screen (Ubuntu) Importance: Undecided Status: New -- 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
[Bug 1562658] [NEW] screen caught signal 11 core dumped
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 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 ** Affects: screen (Ubuntu) Importance: Undecided Status: New -- 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/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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 if it weren't so annoying. ** Description changed: same bug as http://savannah.gnu.org/bugs/?35757 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: screen 4.1.0~20120320gitdb59704-9 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Tue Jun 24 04:40:21 2014 InstallationDate: Installed on 2014-01-30 (144 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha i386 (20140129) ProcEnviron: - LC_TIME=en_DK.UTF-8 - TERM=screen - LC_COLLATE=en_DK.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash + LC_TIME=en_DK.UTF-8 + TERM=screen + LC_COLLATE=en_DK.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash SourcePackage: screen UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 if it weren't so annoying. ** Description changed: same bug as http://savannah.gnu.org/bugs/?35757 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: screen 4.1.0~20120320gitdb59704-9 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Tue Jun 24 04:40:21 2014 InstallationDate: Installed on 2014-01-30 (144 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha i386 (20140129) ProcEnviron: - LC_TIME=en_DK.UTF-8 - TERM=screen - LC_COLLATE=en_DK.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash + LC_TIME=en_DK.UTF-8 + TERM=screen + LC_COLLATE=en_DK.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash SourcePackage: screen UpgradeStatus: No upgrade log present (probably fresh install) -- 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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 dealbreaker when if it is triggered, particularly if you have long-running tasks in a screen session (which is what I use it for). It occasionally triggers on exiting htop, and basically ruins my entire day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 dealbreaker when if it is triggered, particularly if you have long-running tasks in a screen session (which is what I use it for). It occasionally triggers on exiting htop, and basically ruins my entire day. -- 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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 your entire session with it is just unacceptable. 4.2.1-3 needs to be released as a normal patch for all the LTS platforms. -- 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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 your entire session with it is just unacceptable. 4.2.1-3 needs to be released as a normal patch for all the LTS platforms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 - make the current region bigger with ^A :resize 83% (same with +number or while decreasing the other size) or remove it entirely with ^A X - close Vim and screen crashes with [screen caught signal 11. (core dumped)] The screen package I have is screen (4.2.1-2~ubuntu14.04.1), this is on ubuntu 14.04.1 LTS. I spent a little while trying to compile screen from source, but didn't get anywhere. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681572 seems to indicate that this is actually fixed in 4.2.1-*3*, which is /not/ in the backports. Is there any way to get the actually fixed version backported? ** Bug watch added: Debian Bug tracker #681572 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681572 -- 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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 - make the current region bigger with ^A :resize 83% (same with +number or while decreasing the other size) or remove it entirely with ^A X - close Vim and screen crashes with [screen caught signal 11. (core dumped)] The screen package I have is screen (4.2.1-2~ubuntu14.04.1), this is on ubuntu 14.04.1 LTS. I spent a little while trying to compile screen from source, but didn't get anywhere. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681572 seems to indicate that this is actually fixed in 4.2.1-*3*, which is /not/ in the backports. Is there any way to get the actually fixed version backported? ** Bug watch added: Debian Bug tracker #681572 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681572 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
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 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 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)
I can also confirm this issue. I'm running vanilla Ubuntu Server 12.03 LTS in a Hyper-V VM. durr@monsrv:~$ uname -a Linux monsrv 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux durr@monsrv:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.3 LTS durr@monsrv:~$ ps -AF | grep dpk root 12934 12912 0 12295 30440 0 04:04 pts/100:00:04 /usr/bin/dpkg --status-fd 57 --unpack --auto-deconfigure /var/cache/apt/archives/linux-headers-3.2.0-57_3.2.0-57.87_all.deb /var/cache/apt/archives/python-lazr.restfulclient_0.12.0-1ubuntu1.1_all.deb /var/cache/apt/archives/wpasupplicant_0.7.3-6ubuntu2.2_amd64.deb durr 13213 13078 0 2347 944 0 04:18 pts/200:00:00 grep --color=auto dpk It's been running for at least 15 minutes so far with no end in sight. It's worth noting that I have no idea what the hold-up is. `iotop` isn't showing any meaningful disk-activity, and the CPU isn't loaded at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947664 Title: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1) To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/947664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)
Forgot to mention. I'm using a plain-old ext4 partition. Hyper-V instrumentation is showing a pretty static ~25-35 KB/sec read *and* write from the vhd disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947664 Title: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1) To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/947664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580819] Re: package clamav-base 0.96 dfsg-2ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Having some way to stop a broken install without having to close the software center would be a big plus. I was able to install all these packages manually with apt-get after getting this error. The command suggested by Chuck above returned no output perhaps because I successfully installed the software. -- package clamav-base 0.96 dfsg-2ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/580819 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
