Infernal_pizza

I’m having an issue with my desktop flickering after my monitors wake up on KDE. When I first turn on my PC it’s fine, but if I walk away and let the monitors turn off when I then come back the desktop starts flickering. It’s only the desktop that flickers, if I have an app open full screen it’s fine but as soon as I minimise it the flickering comes back. It doesn’t seem to be an issue if I leave it long enough for my actual PC to go to sleep, only the monitor. This happens on both Wayland and X11.

Does anyone have any ideas on how to fix this, and if not is it worth submitting a bug report on kde? Or is it probably just something dodgy in my setup? This is with an Nvidia GPU which I suspect has something to do with it (I’ve tried with both the nvidia and nvidia-open drivers). I’ve already had to change the settings so that the screen locks before the monitors sleep otherwise it was causing kwin to crash and I’d get stuck at the login screen for a minute after resuming.

Apart from the obvious nautical themed solutions, are there any ways around streaming services not allowing HD video playback on Linux? Prime video is the one I’ve noticed it with the most, I haven’t tried Disney plus yet but I’m expecting it to be similar. I’ve been dual booting for a while now and this is the main thing keeping me on Windows at the moment.

I’ve just installed Arch on my laptop and I’ve noticed the WiFi card seems to be generating a load of errors. I’m also dual booting Ubuntu server and it looks like that’s been generating similar logs although I’ve only ever used Ethernet on there:

Under Arch it has these 2 errors over and over again in journalctl:

Mar 31 00:38:58 Laptop kernel: ath10k_pci 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)

Mar 31 01:13:08 Laptop kernel: pcieport 0000:00:1c.5: AER: Correctable error message received from 0000:03:00.0

And under Ubuntu it has this instead:

Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: [ 0] RxErr

Lspci detects the card as this:

03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30) Subsystem: Foxconn International, Inc. QCA9377 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci

But the chip itself is labelled as a Qualcomm Atheros QCNFA435 (which matches what the laptop specs are listed as online)

As far as I can tell the WiFi is working properly, is there anything I should do to fix these errors in either distro or should I just add the pci=noaer parameter to suppress the messages?

I needed a test VM at work the other day so I just went with Debian because why not, during the install I chose KDE plasma as the DE. I did nothing else with it after installing it and after leaving it alone for a while (somewhere between 20-60 minutes) the CPU useage shot up to the point vSphere sent out an alert and the VM was unresponsive (the web console just showed a blank console which I couldn't type in) It did this every time I booted the VM.

It seems to be the combination of vSphere Debian and KDE that causes this as I installed GNOME on the same VM and it was fine. I also created another Debian VM this time choosing GNOME during the install and that was also fine, until I installed KDE on that and then it started doing the same thing. I also created an Arch VM with KDE and that didn't have any issues.

Any idea why this combination causes issues? Journalctl output of the last boot from both Debian VMs below:

Original VM: https://text.is/032Z Secondary test VM: https://text.is/JR45

I had to enable proton compatibillity to even get the game to detect the controller however even after doing that the analog stick won't go up. I tried enabling steam input but that didn't work either