[Bug 867507] Re: [needs-packaging] pypy

2018-01-01 Thread Fake Name
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.

[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

2017-04-14 Thread Fake Name
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

[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

2017-04-14 Thread Fake Name
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

[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI

2016-11-28 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2016-06-01 Thread Fake Name
@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

[Bug 1562658] Re: screen caught signal 11 core dumped

2016-04-12 Thread Fake Name
*** 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

[Bug 1562658] Re: screen caught signal 11 core dumped

2016-04-12 Thread Fake Name
*** 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

[Bug 1562658] Re: screen caught signal 11 core dumped

2016-04-12 Thread Fake Name
*** 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 re

[Bug 1562658] [NEW] screen caught signal 11 core dumped

2016-03-27 Thread Fake Name
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

[Bug 1562658] [NEW] screen caught signal 11 core dumped

2016-03-27 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-10-23 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-10-23 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-08-10 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-08-10 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-29 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-29 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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 -

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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 -

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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

[Bug 1333630] Re: screen caught signal 11 core dumped

2015-03-28 Thread Fake Name
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

[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)

2013-12-07 Thread Fake Name
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

[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)

2013-12-07 Thread Fake Name
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.

[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

2010-05-21 Thread Fake Name
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