Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

Post by rlpb » Sun, Jan 29, 2017, 6:08 PM UTC

Pxtl wrote: post #7

mrmondo wrote: post #2

It's not just a bunch of people setting cm.swappieness to 0 is it? That behaviour changed and now prevents going into swap /ever/ where it used to mean go into swap as a last resort. Changing it to 1 fixes the issue and will act like the old behaviour or only swapping as a last result. Regardless, it's things like this why we never recommend people use Ubuntu - years of poorly packaged and tested software. If you wan…

Yeah, Ubuntu still keeps running out of space in /boot by filling it w old kernels in the default partition profile. A bug that I've been hitting since about 2011. In spite of their best efforts, it is not the "grandma friendly" quality software it hoped to be.

Post by Pxtl » Sun, Jan 29, 2017, 6:17 PM UTC

nnq wrote: post #65

Pxtl wrote: post #22

Earlier quoted context omitted.

Oh, I know it's easy to fix, I just single that bug out as "I have done nothing with this box but install updates and surf the web. I am Grandma. It breaks".

If you're Grandma you don't have /boot on a separate partition, you have all / on a big 120GB at least, so if you run out of space you simply know you've run out of space. Not perfect but not a problem for 90% of people I guess...

Post by lima » Sun, Jan 29, 2017, 6:23 PM UTC

spikengineer wrote: post #106

cakeface wrote: post #84

Earlier quoted context omitted.

Ubuntu installer has separate /boot partition by default. If you don't do anything special during installation you end up with it.

No you don't. Ubuntu's default partition map is one big / and one efi(if necessary).

Post by dfc » Sun, Jan 29, 2017, 8:18 PM UTC

amluto wrote: post #11

Pxtl wrote: post #7

Earlier quoted context omitted.

Yeah, Ubuntu still keeps running out of space in /boot by filling it w old kernels in the default partition profile. A bug that I've been hitting since about 2011. In spite of their best efforts, it is not the "grandma friendly" quality software it hoped to be.

My M.O. is: # apt-get update # aptitude full-upgrade # apt-get autoremove Because as far as I can tell, apt-get sometimes fails to actually update things, whereas aptitude can't autoremove. I'm sure there's a better way. This is my major gripe with the dpkg ecosystem. There are (AFAICT) multiple different tools to build dpgks and multiple different tools for updating your system, and none of them are adequately docum…

Post by mianos » Sun, Jan 29, 2017, 9:20 PM UTC

cagey wrote: post #149

pacifika wrote: post #115

Earlier quoted context omitted.

What does it do?

I tried it on Lubuntu 16.04; it required modification: # mystery one-liner from https://news.ycombinator.com/item?id=13513171 # dpkg -l 'linux-' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]\)./\1/;/[0-9]/!d' | xargs -p sudo apt-get -y purge # my corrected/improved version: noncurrent_kernel_pkgs() { dpkg -l 'linux-*[0-9]*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.\)-\([^0-9…