Main changes from RC3 to RC4
- Fixed: “qvm-move fails, deletes origin file anyway” (#8516)
- Fixed: “
90-default.policynot upgraded after in-place upgrade from 4.1 to 4.2” (#8458)
- Fixed: “Qube Manager freezes while opening settings” (#8387)
- Fixed: “Error when attempting to update dom0 in the Qube Manager” (#8117)
- Fixed: “XScreenSaver & XScreenSaver Settings not opening window” (#8266)
- Fixed: “Setting no-strict-reset option via salt on already attached devices doesn’t work” (#8514)
- Fixed: “qvm-copy-to-vm incorrect progress report” (#1519)
- Fixed: “qubes-video-companion-receiver missing dependency on acl package” (#8426)
- Fixed: “OpenBSD 7.3 ISO doesn’t boot anymore” (#8502)
- Fixed: “Kernel compile bogs down rest of system” (#8176)
- Fixed: “rpm-oxide makes unjustified assumptions about RPM ABI” (#8522)
- Fixed: “yk-auth YubiKey PAM script incorrectly expects \0 to be appended to hash” (#8517)
- Fixed: “Qubes Application Menu isn’t updated when using salt to modify menu-items” (#8494)
- Fixed: “Different values for
default-menu-itemsare not preserved when cloning templates” (#8518)
- Fixed: “Fix handling of menu items in GUI VM” (#8528)
- Fixed: “Firefox does not start on 4.2-rc3 after upgrading template” (#8571)
- Fixed: “Qubes R4.2.0-rc2 Qubes OS Global Config tool not see qubes-u2f installed in sys-usb” (#8463)
- Fixed: “global config: policy rules for U2F incorrectly assume wildcard argument” (#8525)
- Fixed: “Pipewire on some systems causes a lot of underruns” (#8576)
- Fixed: “Listing PCI devices breaks when there is some with non-0000 PCI domain” (#6932)
- Done: “Prepare R4.1 -> R4.2 upgrade tool” (#7832)
- Done: “Phase out legacy qrexec policy files” (#8000)
- Done: “Better qrexec service configuration format” (#8153)
- Done: “QRexec services should be able to specify the user they must run as” (#6354)
- Done: “Qube Manager: Enable the ‘restart qube’ button for named disposables” (#8382)
- Done: “Utilize memory hotplug to add VM memory by qmemman” (#7956)
For an overview of major changes from Qubes 4.1 to 4.2, please see the Qubes OS 4.2.0 release notes.
When is the stable release?
That depends on the number of bugs discovered in this RC and their severity. As explained in our release schedule documentation, our usual process after issuing a new RC is to collect bug reports, triage the bugs, and fix them. This usually takes around five weeks, depending on the bugs discovered. If warranted, we then issue a new RC that includes the fixes and repeat the whole process again. We continue this iterative procedure until we’re left with an RC that’s good enough to be declared the stable release. No one can predict, at the outset, how many iterations will be required (and hence how many RCs will be needed before a stable release), but we tend to get a clearer picture of this with each successive RC, which we share in this section in each RC announcement. Here is the latest update:
At this point, we are hopeful that RC4 will be the final RC.
Testing Qubes 4.2.0-rc4
Thank you to everyone who tested the previous Qubes 4.2.0 RCs! Due to your efforts, this new RC includes fixes for several bugs that were present in the previous RCs.
Upgrading to Qubes 4.2.0-rc4
If you’re currently running any Qubes 4.2.0 RC, you can upgrade to the latest RC by updating normally. However, please note that there have been some recent template changes, which are detailed in the Qubes OS 4.2.0 release notes.
If you’re currently on Qubes 4.1 and wish to test 4.2, please see how to upgrade to Qubes 4.2, which details both clean installation and in-place upgrade options. As always, we strongly recommend making a full backup beforehand.
Reminder: new signing key for Qubes OS 4.2
As a reminder, we published the following special announcement in Qubes Canary 032 on 2022-09-14:
We plan to create a new Release Signing Key (RSK) for Qubes OS 4.2. Normally, we have only one RSK for each major release. However, for the 4.2 release, we will be using Qubes Builder version 2, which is a complete rewrite of the Qubes Builder. Out of an abundance of caution, we would like to isolate the build processes of the current stable 4.1 release and the upcoming 4.2 release from each other at the cryptographic level in order to minimize the risk of a vulnerability in one affecting the other. We are including this notice as a canary special announcement since introducing a new RSK for a minor release is an exception to our usual RSK management policy.
As with all Qubes signing keys, we also encourage you to authenticate the new Qubes OS Release 4.2 Signing Key, which is available in the Qubes Security Pack (qubes-secpack) as well as on the downloads page under the Qubes OS 4.2.0-rc4 ISO.
What is a release candidate?
A release candidate (RC) is a software build that has the potential to become a stable release, unless significant bugs are discovered in testing. RCs are intended for more advanced (or adventurous!) users who are comfortable testing early versions of software that are potentially buggier than stable releases. You can read more about Qubes OS supported releases and the version scheme in our documentation.