Qubes 4.3 is being tested by the testing team

Yes, old QWT should work on R4.3 too, as long as you have GUI in dom0. But old QWT is not compatible with GUI domain, new one should be (at least in theory).

3 Likes

OK, thank you guys. I hope Win qube would survive migration to R4.3 as it did for migration to R4.2.

The list of regressions or intentional breaking changes should be provided if possible anyway, imho. Because the updates are not only bringing joy to users, but quite often break things.

2 Likes

Well, there shouldn’t really be any intentional breaking changes in a minor release (4.2 → 4.3). The whole point of distinguishing between major releases (e.g., 4.x → 5.x) and minor releases (e.g., x.2 → x.3) is that major releases are allowed to have backward-incompatible changes, while minor releases are supposed to include only backward-compatible changes.

In general, patch releases are for backward-compatible bug fixes, minor releases are for backward-compatible enhancements and new features, and major release are for any backward-incompatible changes. This means that, in general, one should not try to introduce features or enhancements in patch releases or any backward-incompatible changes in patch or minor releases. (Templates are a notable exception, as upstream OSes almost always have their own release schedules.) Bug fixes are allowed in all releases, and backward-compatible changes are allowed in all major and minor releases.

This is an excerpt from:

3 Likes

Understood Andrew. @balko do you agree based on testing?

For certain though I understand this is ALPHA/BETA software. Soon intend to test https://qubes.notset.fr/iso-testing/Qubes-4.3.202505202200-x86_64 .iso and

Guess I find out soon, Thank you “qubes team”! Eager to confirm

but sad to read

Can some kind person point me to “new one”? If matters my use is no networked Win7 qubes.
Thank you al!l

If I recall, the new QWT does not support Win7

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

:frowning_face:
Thanks for the info @unman

Appreciate you and all you do!

Testing salt to a new Fedora template in 4.3 fails with the following error:

t-fed-42:
      ----------
      _error:
          Failed to return clean data
      retcode:
          1
      stderr:
          /var/tmp/.root_dd8a91_salt/pyall/salt/ext/tornado/util.py:246: SyntaxWarning: invalid escape sequence '\d'
            """Unescape a string escaped by `re.escape`.
          Traceback (most recent call last):
            File "/var/tmp/.root_dd8a91_salt/salt-call", line 27, in <module>
              salt_call()
              ~~~~~~~~~^^
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/scripts.py", line 438, in salt_call
              import salt.cli.call
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/call.py", line 3, in <module>
              import salt.cli.caller
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/caller.py", line 12, in <module>
              import salt.channel.client
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/channel/client.py", line 12, in <module>
              import salt.crypt
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/crypt.py", line 29, in <module>
              import salt.utils.event
            File "/var/tmp/.root_dd8a91_salt/pyall/salt/utils/event.py", line 67, in <module>
              import salt.ext.tornado.iostream

System is completely up to date as of this morning.

Did you get any more messages above this one? Maybe not enough memory to start f-fed-42?

No only a couple of deprecation warnings from the Python version. Also attempted the same process on 4.2.4 using the same SLS scripts and that has worked without error.

Any advance on this? I am still getting salt failures on 4.3 with scripts that work on 4.2. I am using fully updated templates and switched the disp VM base templates in case that is the problem. Same error as above.

Is there a github issue about this?

Sorry not on GitHub.

Further investigation of salt on 4.3 (has this always been a hot mess or what…?)
Salt version 3007.5
Python 3.13.5

4.3 generates multiple Python deprecation warnings and update script interpretation crashes completely with “SyntaxWarning…” errors and “Failed to return clean data…” errors.

I’m not even convinced the saltstack code supports this version of Python. Seems like an upgrade from version 3.11 is still a tech debt task in GitHub…

On Qubes 4.2.4 in which all clone and update SLS scripts are working as expected:
Salt version 3007.1
Python version 3.11.6
(this seems to still be a fully supported version of Python)

If you are talking about datetime.utcnow and split deprecation warnings, there has been open issues and some PRs upstream to fix them. Some of them even from Qubes OS team. And Salt team did not take the appropriate action (sadly). See for yourself:

2 Likes

I can live with the deprecation warnings. It’s the apparent lack of support for a higher version of Python that is the problem when the salt scripts are crashing immediately.

I have installed and used Windows 11 and it works fine.

Are there any approx dates for the release? I prefer to install 4.3 with Plasma 6 rather the current one.

Are there any plans for fixing the keyboard layout or is it just too problematic for the 4.3 release?
AFAIK Qubes uses x11 session currently, so is it the transition to Wayland problematic and the x11 session will work fine or is it x11 will be disabled completly in 4.3?

take a look:

I note the versioning info for my test 4.3 install is now at RC1, so congratulations to all the devs and testers out there. Also thankyou to the devs for all the recent saltstack fixes… all my issues are now solved, cheers!

6 Likes