I am also affected by the bug,
echo all > /etc/gcrypt/hwf.deny fixed it.
The sha1 and md5 sum were equals but the sha256 sums were different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890006
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libgcrypt20 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890006
Title:
I've spent a day trying to figure out why my VMs were not working until
I found this report.
TLDR: Windows Sandbox in itself does not break the virtualization for
Virtualbox, what does is the Virtual Machine Platform (on which I guess
Windows Sandbox depends on).
I'll try to gather everything I
** Package changed: apt (Ubuntu) => libgcrypt20 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890006
Title:
Hash mismatch on "apt update"
To manage notifications about this bug go to:
VT-x status in BIOS is a red herring. Turns out modern Virtualbox won't
even start VM's without VT-x.
A true cause turned out to be "Windows Sandbox" feature (although I
imagine for some other users the problem might be triggered by "Windows
Subsystem for Linux" or anti-virus software).
Here is
Here is apport stuff, and there are more news.
I confirmed that the problem was in the gcrypt. More precisely,
disabling SSSE3 fixes this issue (echo intel-ssse3 >
/etc/gcrypt/hwf.deny).
The Virtualbox (running on Windows 10) was using software virtualization
("execution engine: native API")
apport information
** Tags added: apport-collected focal
** Description changed:
This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt
2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
Don't see any reason for any apport collecting here.
This needs a clean reproducer or someone with the issue to do the work
to analyse what's wrong.
Looking at the bug report, the output from the reproducer matches that
of the commandline tools?
--
You received this bug notification because
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1890006
When reporting bugs in the future please use apport by using 'ubuntu-
