Next release (0.15.0.0) is scheduled for October 31, hard fork planned to take place on November 30.
Currently 0.15 is available for CLI only. GUI version still isn’t out. Many nodes already using 0.15.
Official Monero site has served possible malware for 30 minutes between Nov.18 and Nov.19.
Always verify hashes!
According to the email from the monero-announce list the malware was being served for 14 hours.
The malware will steal your coins: https://github.com/monero-project/monero/issues/6151#issuecomment-555694443.
I’ve posted a proposal at monero Community Crowdfunding System (CCS) where I suggested myself to become the maintainer of a monero GUI Debian package installable from whonix.org repository, avaiable for all users of Debian buster, Whonix and Qubes Debian buster template.
See full proposal text here:
The CCS proposal was a success. Funding as provided.
Monero GUI was packaged for Debian. It’s available in all Whonix repositories.
Not calling for testers just yet since I am still testing myself.
There’s also a non-packaging, probably non-Whonix specific 100% CPU use bug: https://github.com/monero-project/monero-gui/issues/2238#issuecomment-622497250
Looks like a new ticket was created instead of re-opening the old one:
Good to see a developer react so quickly.
Could you please test monero-gui (from Whonix repository https://github.com/Whonix/monero-gui)
sudo apt update sudo apt install monero-gui
in Whonix-Workstation KVM and see if KVM is affected by any of these bugs?
Related, perhaps you also have an idea for Test command from inside VM to detect if VirtualBox 3D acceleration is enabled or disabled?
Install mesa-utils then run
glxinfo | grep OpenGL
If 3D is being emulated in pure software because no acceleration it will say llvmpipe. At least it’s the case with KVM. This isn’t future proof and makes no sense in vulkan environments.
OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
VirtaulBox host setting VMSVGA 3D acceleration seems to be working.
- Without, 3D acceleration disabled the CPU utilization is higher as expected (100%).
- With, 3D acceleration enabled the CPU utilization is lower (30%).
The output of
glxinfo is exactly the same with and without 3D acceleration.
I can’t find any way to figure that out from inside the VM. The only way to find this out is by testing. Environment variable
QMLSCENE_DEVICE=softwarecontext is either required or not.
For VirtualBox, this will be simplified in the future in Whonix ™
220.127.116.11.4 (and above) which is coming soon.
QMLSCENE_DEVICE=softwarecontext will be globally set as environment variable if VirtualBox is detected. Script:
Seeing the exact same behavior described in bug reports. Expected because 3D acceleration is not fully ready yet for KVM on Debian stable.
any way to test if it works for kvm?