First of all I would like to say that I have encountered some of these problems and will try to link you to the issue or offer a solution. I have been using Qubes OS a couple years as my only OS and over a year on L14 with a similar configuration as you. One thing you could do to rule out RAM fault is to run memtest86.
- Almost every time the fedora-34 template is modified, either by me or via system updates, this breaks my Wi-Fi configuration upon reboot. By “break”, I mean that the system won’t even attempt to connect to the network, even though the configuration is correct. My only fix for this is to delete the configuration and recreate it with all of the same data.
I have noticed that NetworkManager sometimes “loses” the password to saved Wi-Fi networks, this has happened since Fedora 32 or 33 if I remember correctly. Core of the issue seems to be around that NetworkManager stores some wireless configs in /etc/Networkmanager/system-connections/ which are not surviving reboots as sys-net is an App Qube. I might have fixed this by creating identical files to sys-net’s Template Qube under /etc/Networkmanager/system-connections/ but I’m not sure of that. Myself I have migrated to disp sys-net and use Wi-Fi rarely, so this is a non issue for me.
- I’ve encountered an issue similar to #1 after waking up from the suspend state
As @dom0 stated suspend and other sleep states have not been working properly for a lot of people. But that is almost always due to proprietary hardware and should not be the case for L14.
- The software manager in Fedora-34 appears to be useless because it appears to be under the impression that it has no internet connection ("Unable to contact “admin.fedoraproject.org”). I did see an open issue that seemed to describe this, but that was ~4 years ago.
@fsflover linked the issue above.
- The cheese app seems to be corrupted in my personal qube. I attached my webcam to the personal qube, then tested taking a photo, which worked. When I tried to record a video, it froze, and I had to shut down the qube. Now when I open the cheese app, it always says “There was an error playing video from the webcam” and everything in the app is disabled.
Recording video takes quite lot of cpu power, might be worth a while to increase the VCPU count from App Qube’s Advanced Settings.
To fix your personal Qube’s cheese app you might want to try the following:
Delete ~./config/cheese and ~./cache/cheese directories from your personal Qube.
- There are odd graphical glitches in the Qubes splash screen and with some cursors (loading spinning wheel) in the desktop environment that I didn’t see with v4.0.4, particularly around the password box and progress bar during disk decryption
This is an issue with Intel Graphics and the newer GUI on luks decryption splash screen, you can press “Esc” to get CLI or disable GUI completely on spash screen (Run these in dom0):
sudo nano /etc/default/grub
Remove rhgb from GRUB_CMDLINE_LINUX line
Rebuild grub config sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Rebuild initrd sudo dracut -f
Reboot
Fixing some of the graphical issues while loaded into desktop environment you could try to follow this: I3 not working properly video/graphic issues - #4 by bungali
- The OS froze on me during a routine restart. When I clicked restart, it kicked me out to the login screen (which it always does in v4.1.0, which I don’t understand), then went to the Qubes splash screen and froze there. Is anyone else confused by Qubes going from desktop → login screen → Qubes splash screen that makes it appear as though it’s booting up when it’s actually shutting down, or is it just me?
On Qubes OS 4.1 it seems like it log you out before it goes to “shutdown” screen. As @dom0 mentioned App Qube’s take a while to shutdown.
Other issues that you are having seem really odd and personally have not experienced those.
One thing that hasn’t been mentioned that boosts performance (fixing CPU scaling). In dom0:
sudo nano /etc/modules-load.d/xen-acpi-processor.conf
Write xen-acpi-processor and save.
Reboot.