KDE intermittent desktop flickering after monitors wake up from suspend - Lemmy.World

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.

What eternity feels like - Lemmy.World

Is it worth upgrading from a Ryzen 7 3800X to a Ryzen 7 5700X3d? - Lemmy.World

I was planning on picking up Cyberpunk a while ago but noticed I no longer reach the recommended system requirements since the last update. Is it worth upgrading from a Ryzen 7 3800X to a Ryzen 7 5700X3d? The 5700X3d seems like the best choice as it seems like a pretty decent jump in gaming performance without having to buy a new motherboard. And although the 5800X3d would be even better it’s ~£300 compared to ~£200 for the 5700X3d so doesn’t seem worth the price difference. My gpu is an RTX2080 super so that would probably become the bottleneck, but I’m planning on upgrading that a bit later on if I upgrade the cpu first (not sure what to go with for that either yet, I’m still debating between Nvidia and AMD)

HD video playback from streaming services - Lemmy.World

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.

Laptop won't shut down on any kernel version above 6.7 - Lemmy.World

I’ve been trying to install Arch on an old laptop for the past few days but for some reason it will not shut down if I’m using any kernel above version 6.7. It goes all the way through and gets to Reached target: System Power Off but then just sits there and never actually powers down. I waited 30 minutes in case it did something and it never did. I don’t believe there is anything useful in the journalctl output as there’s nothing after Reached target System Power Off but I’ll paste it here in case: https://text.is/4KNL [https://text.is/4KNL] I tried the shutdown troubleshooting steps from here: https://freedesktop.org/wiki/Software/systemd/Debugging/ [https://freedesktop.org/wiki/Software/systemd/Debugging/] The debug shell is no help as I can’t access it once it hangs, and since it never finishes shutting down the logging script won’t help. reboot -f and poweroff -f both work which made me think it wasn’t a kernel issue, however it works fine using the linux-lts kernel. Because of this I tried manually downgrading to a few standard kernel versions from 6.6, 6.7 and 6.8 and only the ones above 6.7 had this issue. Specifically the latest lts version (6.6.23 at the time I tested) worked fine, 6.7.arch1-1 and above didn’t. Weirdly I don’t have any issues with the installation media (currently using the ones from 29th March and 1st April). I also tried Opensuse Tumbleweed which I believe is on the same kernel version and had no issues so it seems to be Arch specific. I also tried linux-zen in case that had any difference but it didn’t help. I have tried several re-installs with both legacy and UEFI boot, mostly minimal installs (base, linux, linux-firmware, linux-headers and nano). Since the live iso works I also tried installing all the packages from that but it still didn’t work. I’m completely out of ideas at this point. I can’t see anything obvious in the kernel 6.7 changelog, but then I don’t really know enough to know what to look for there. I know for now I can keep using the lts kernel but presumably at some point that will be upgraded to a version above 6.7 so that doesn’t seem like a good long term solution, I’d also really like to know the root cause behind this as its been bugging me for days! The laptop is an Acer aspire E15 with an Intel 6500U (I have tried with the Intel-ucode package installed) and an Nvidia Geforce 920M.

WiFi card pci errors - Lemmy.World

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?

mkinitcpio failing on Btrfs - Lemmy.World

I’m trying to install Arch on Btrfs but every time mkinitcpio runs it fails as shown in the attached screenshot. I’ve tried on the actual laptop which I’m trying to set up, and also on a couple of Hyper-V VMs set up as I usually do and I’ve never had this issue before. This happens when its run automatically after installing linux via pacstrap, and if I run it again while chrooted into the new system. If I format as ext4 instead I don’t have any problems. I have a single subvolume called root mounted at / and a fat32 volume mounted at /boot, and I’m using the latest arch install iso (2024.03.29). Any idea why this is happening? The Btrfs volume is on a single device so as far as I’m aware I don’t need to add the btrfs module to mkinitcpio.conf

Yay orphaned packages - Lemmy.World

The past few times I’ve run yay I’ve got these warnings about packages that are orphaned/not in the AUR. Based on the names I’m assuming these are leftover from the upgrade from kde plasma 5 to 6, are these safe to remove now? And secondly how would I find orphaned packages like that if I wasn’t using yay since I never installed these from the AUR?

vSphere+Debian+KDE Plasma=Crash? - Lemmy.World

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? I do have the journalctl output from the last boots of the 2 Debian VM’s but I’m not sure the best way to post them on here, pastebin won’t let me create an account and I’d like to delete it afterwards

AI Articrule - Lemmy.World

This is the page if anyone wants to check if its real: https://scalacube.com/blog/terraria/how-to-stop-corruption-in-terraria [https://scalacube.com/blog/terraria/how-to-stop-corruption-in-terraria]