In my case, it was happening on a headless server so lots of keyboard
access isn't an option. I actually fixed it on my system by reversing a
change to a BIOS setting which I had initially changed to work around
the same issue on a previous occurrence.
The setting on my system related to the
This should really only be an issue early during boot, or if you require
a lot of randomness. So I guess wait, use your keyboard a lot, generate
a lot of network traffic? Or manually inject randomness? I don't really
know, and it's out of scope for the bug report to discuss this - you
might want
Any recommendation how to update if you can't update due to this bug?
"apt update" will always fail, so no matter if it's a kernel or apt
update I need, I won't get it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
This has been fixed in 18.10, not 18.04 - the breaking kernel change was
reverted in 18.04, so we decided we don't need to backport it.
This is a system wide issue if the kernel runs out of entropy and by no
means an apt one. I suggest you report a kernel bug if you still see
issues like this on
Hi, can someone with the permission please re-open?
I'm seeing this on a relatively recent system (18.04, updates have been
successfully done lately), so it's definitely not fixed since august last year.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
OK, this appears to have been fixed in a kernel update, but then broken
again, and the error is no longer intermittent - I cannot apt update,
which means I can't apt upgrade to a fixed version.
Do you have any suggestions?
--
You received this bug notification because you are a member of Ubuntu
Fixed in 1.7.0~alpha2
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1784796
Title:
apt update fails -
Ah! Awesome, thanks. So the fact that I run apt immediately after
rebooting to check if I've cleared the problem, is what is causing the
problem. That figures.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This should be a problem with not enough entropy that should have been
fixed in recent kernel versions. APT 1.7 will have a fix for that, it's
not backported to 1.6 yet, but it should be easily doable.
I'd say: make sure you are running the latest kernel and that you don't
start apt shortly after
9 matches
Mail list logo
