-
Notifications
You must be signed in to change notification settings - Fork 37.7k
Closed
Description
Umbrella issue for 23.0 testing. Please help testing on a wide variety of supported platforms, as well as interaction with different software.
Let us know which version you tested on which operating system.
If you find an issue, please search Github for known issues first and then open a new Github issue. This meta issue should not be used to report bugs, as a single thread makes it impossible to track more than one topic.
What to test
For an idea what to test, see @stickies-v's 23.0 release candidate testing guide, or
- See Draft Release Notes for a list of changes-
- Also see testing reports for earlier releases (v0.21.0 v22.0)
Known issues (as of rc5)
Other known issues:
- MacOS: SHA256 acceleration is not enabled on MacOS 11.x due to missing reporting of sysctl
hw.optional.arm.*
. Please upgrade to MacOS 12.x if this is important to you.
Known issues fixed (as of rc5)
-
Due to a naming conflict after adding support for the new MacOS architecture, we had to rename the following dmgs manually frombitcoin-23.0rc2-osx-signed.dmg
during upload:
bitcoin-23.0rc2-arm64-apple-darwin.dmg
bitcoin-23.0rc2-x86_64-apple-darwin.dmg
This may cause issues during verification because in the SHA256SUMS.asc
they still have the old name.
-
MacOS: please postpone the Monterey 12.3.1 update until 23.0rc4 to test whether macOS Monterey deleting bitcoin core after updates (M1) #23134 has been really fixed(it's really fixed, see v23.0 testing #24501 (comment)) -
Cross-compiledbitcoind -signet
silently fails on Windows #24726 bitcoind/-qt may silently fail on Windows when using AVX2 SHA256 implementation - ~Bech32m unavailable for encrypted wallets bitcoin-core/gui#571~~
-
Windows GUI crashes while rendering bandwidth graph: 23.0rc4 crashes when trying to open the "Network Traffic" tab bitcoin-core/gui#582
slashbinslashnoname, JeremyRand, dunxen and muugkatesalazar and RandyMcMillan