3 ms·
I had it a few times. This used to happen when kernels fill up boot partition, and apt gets into broken state because of that.
by lostmsu 6y ago
I had it a few times. This used to happen when kernels fill up boot partition, and apt gets into broken state because of that.
- beagle3 6y agoyes, apt can get temporarily broken if your boot partition fills up - but it does not make a system unbootable when this happens (Which GP says he encountered). a few apt-get removes and apt-get installs -f, and it's all back to normal - but it's only ever "apt" that stops working, and only until you fix it. (I've seen got in the habbit of doing "apt-get autoremove --purge && apt-get autoclean" regularly on all machines I manage. The only borked Ubuntu kernel upgrade I've ever seen did not render anything unbootable, but a bad OOM Killer patch caused programs to get spontaneously killed in some cases - and I'm runnig, and automatically updating, tens of Ubuntu machines automatically all the time.