[qubes-users] Qubes OS 4.2.0-rc4 is available for testing

Dear Qubes Community,

We're pleased to announce that the fourth [release candidate (RC)](#what-is-a-release-candidate) for Qubes OS 4.2.0 is now available for [testing](Testing new releases and updates | Qubes OS). The ISO and associated [verification files](Verifying signatures | Qubes OS) are available on the [downloads](Download Qubes OS | Qubes OS) page.

## Main changes from RC3 to RC4

- Fixed: ["qvm-move fails, deletes origin file anyway" (#8516)](qvm-move fails, deletes origin file anyway · Issue #8516 · QubesOS/qubes-issues · GitHub)
- Fixed: ["`90-default.policy` not upgraded after in-place upgrade from 4.1 to 4.2" (#8458)](`90-default.policy` not upgraded after in-place upgrade from 4.1 to 4.2 · Issue #8458 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Qube Manager freezes while opening settings" (#8387)](Qube Manager freezes while opening settings · Issue #8387 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Error when attempting to update dom0 in the Qube Manager" (#8117)](Error when attempting to update dom0 in the Qube Manager · Issue #8117 · QubesOS/qubes-issues · GitHub)
- Fixed: ["XScreenSaver & XScreenSaver Settings not opening window" (#8266)](v4.2 - XScreenSaver & XScreenSaver Settings not opening window · Issue #8266 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Setting no-strict-reset option via salt on already attached devices doesn't work" (#8514)](Setting no-strict-reset option via salt on already attached devices doesn't work · Issue #8514 · QubesOS/qubes-issues · GitHub)
- Fixed: ["qvm-copy-to-vm incorrect progress report" (#1519)](qvm-copy-to-vm incorrect progress report · Issue #1519 · QubesOS/qubes-issues · GitHub)
- Fixed: ["qubes-video-companion-receiver missing dependency on acl package" (#8426)](qubes-video-companion-receiver missing dependency on acl package · Issue #8426 · QubesOS/qubes-issues · GitHub)
- Fixed: ["OpenBSD 7.3 ISO doesn't boot anymore" (#8502)](https://github.com/QubesOS/qubes-issues/issues/8502)
- Fixed: ["Kernel compile bogs down rest of system" (#8176)](Kernel compile bogs down rest of system · Issue #8176 · QubesOS/qubes-issues · GitHub)
- Fixed: ["rpm-oxide makes unjustified assumptions about RPM ABI" (#8522)](rpm-oxide makes unjustified assumptions about RPM ABI · Issue #8522 · QubesOS/qubes-issues · GitHub)
- Fixed: ["yk-auth YubiKey PAM script incorrectly expects \0 to be appended to hash" (#8517)](yk-auth YubiKey PAM script incorrectly expects \0 to be appended to hash · Issue #8517 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Qubes Application Menu isn't updated when using salt to modify menu-items" (#8494)](4.2-RC3: Qubes Application Menu isn't updated when using salt to modify menu-items · Issue #8494 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Different values for `menu-items` and `default-menu-items` are not preserved when cloning templates" (#8518)](Different values for `menu-items` and `default-menu-items` are not preserved when cloning templates · Issue #8518 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Fix handling of menu items in GUI VM" (#8528)](Fix handling of menu items in GUI VM · Issue #8528 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Firefox does not start on 4.2-rc3 after upgrading template" (#8571)](Firefox does not start on 4.2-rc3 after upgrading template · Issue #8571 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Qubes R4.2.0-rc2 Qubes OS Global Config tool not see qubes-u2f installed in sys-usb" (#8463)](Qubes R4.2.0-rc2 Qubes OS Global Config tool not see qubes-u2f installed in sys-usb · Issue #8463 · QubesOS/qubes-issues · GitHub)
- Fixed: ["global config: policy rules for U2F incorrectly assume wildcard argument" (#8525)](global config: policy rules for U2F incorrectly assume wildcard argument · Issue #8525 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Pipewire on some systems causes a lot of underruns" (#8576)](Pipewire on some systems causes a lot of underruns · Issue #8576 · QubesOS/qubes-issues · GitHub)
- Fixed: ["Listing PCI devices breaks when there is some with non-0000 PCI domain" (#6932)](Listing PCI devices breaks when there is some with non-0000 PCI domain · Issue #6932 · QubesOS/qubes-issues · GitHub)
- Done: ["Prepare R4.1 -> R4.2 upgrade tool" (#7832)](Prepare R4.1 -> R4.2 upgrade tool · Issue #7832 · QubesOS/qubes-issues · GitHub)
- Done: ["Phase out legacy qrexec policy files" (#8000)](Phase out legacy qrexec policy files · Issue #8000 · QubesOS/qubes-issues · GitHub)
- Done: ["Better qrexec service configuration format" (#8153)](Better qrexec service configuration format · Issue #8153 · QubesOS/qubes-issues · GitHub)
- Done: ["QRexec services should be able to specify the user they must run as" (#6354)](QRexec services should be able to specify the user they must run as · Issue #6354 · QubesOS/qubes-issues · GitHub)
- Done: ["Qube Manager: Enable the 'restart qube' button for named disposables" (#8382)](Qube Manager: Enable the "restart qube" button for named disposables · Issue #8382 · QubesOS/qubes-issues · GitHub)
- Done: ["Utilize memory hotplug to add VM memory by qmemman" (#7956)](Utilize memory hotplug to add VM memory by qmemman · Issue #7956 · QubesOS/qubes-issues · GitHub)

For an overview of major changes from Qubes 4.1 to 4.2, please see the [Qubes OS 4.2.0 release notes](Qubes OS 4.2.0 release notes | Qubes OS).

## 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](Version scheme | Qubes OS) 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.

If you're willing to [test](Testing new releases and updates | Qubes OS) this new RC, you can help us improve the eventual stable release by [reporting any bugs you encounter](Issue tracking | Qubes OS). We encourage experienced users to join the [testing team](Joining the Testing Team).

A full list of issues affecting Qubes 4.2.0 is available [here](Issues · QubesOS/qubes-issues · GitHub). We strongly recommend [updating Qubes OS](How to update | Qubes OS) immediately after installation in order to apply all available bug fixes.

## 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 [enabling the `current-testing` repo in dom0](How to install software in dom0 | Qubes OS), then [updating normally](How to update | Qubes OS). However, please note that there have been some recent template changes, which are detailed in the [Qubes OS 4.2.0 release notes](Qubes OS 4.2.0 release notes | Qubes OS).

If you're currently on Qubes 4.1 and wish to test 4.2, please see [how to upgrade to Qubes 4.2](How to upgrade to Qubes 4.2 | Qubes OS), which details both clean installation and in-place upgrade options. As always, we strongly recommend [making a full backup](How to back up, restore, and migrate | Qubes OS) beforehand.

## Reminder: new signing key for Qubes OS 4.2

As a reminder, we published the following special announcement in [Qubes Canary 032](Qubes Canary 032 | Qubes OS) 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 always, we encourage you to [authenticate](Qubes security pack (qubes-secpack) | Qubes OS) this canary by [verifying its PGP signatures](Verifying signatures | Qubes OS). Specific instructions are also included in the [canary announcement](Qubes Canary 032 | Qubes OS).

As with all Qubes signing keys, we also encourage you to [authenticate](Verifying signatures | Qubes OS) the new Qubes OS Release 4.2 Signing Key, which is available in the [Qubes Security Pack (qubes-secpack)](Qubes security pack (qubes-secpack) | Qubes OS) as well as on the [downloads](Download Qubes OS | Qubes OS) 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](Supported releases | Qubes OS) and the [version scheme](Version scheme | Qubes OS) in our documentation.

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2023/10/13/qubes-os-4-2-0-rc4-available-for-testing/

3 Likes