Recently installed 4.2.4
initial setup crashed bc. of an unrecognised line in the anaconda kickstart file (that was generated by anaconda without changes).
Manually re-ran it after removing these lines. (Something btrfs).
Appmenu icons were missing and the new menu doesn’t load. But it loads if called from Terminal.
The default VMs and stuff are there since re run.
Fixed the app Icons in a kludged invocation of the new launcher.
The old launcher is buggy as well.
And most importantly ALT+TAB does not work.
It worked before in that very same session. But it stopped working. Even across reboots.
The shortcut for window switching is set to alt tab.
Indeed, because many users have not faced these problems.
Details of the hardware may be useful.
Details of the lines removed equally useful as most users have not faced
any issue here.
Details of the options selected during install and at the post install
stage, also useful.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
It is independent of hardware. Both certified devices.
Sovereign blocked the initial setup from launching. It was related to the storage stacking.
BTRFS with Subvolumes and non-BTRFS on LVM on LUKS.
There were 2 combined problem origins.
One was in the installer.
The other was that the initial setup parses the kickstart file in /root that is written by the installer. It choked on the BTRFS lines.
I can’t provide logs rn. I think it is Reproducible.
I don’t have a testing machine right now to show it.