I'm on the verge of completely giving up here, I've always had a few problems with sleep but for the last few months my system has no graphics output when I resume from suspend. Its not just outputting a black screen, my monitors go back into sleep mode as there is no video output at all. I'm assuming its something to do with my Nvidia GPU but none of the steps from here help: https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

I have tried suspending from the gui, systemctl suspend and directly writing to /sys/power/state. I have tried both s2idle and deep sleep (with s2idle it wouldn't even enter sleep properly and I still ended up with a blank screen). I have the same issue on Plasma X11 and XFCE on my main Arch system and also on the Ubuntu 24.04 live iso (which I couldn't even get to boot properly without choosing safe graphics mode), but interestingly I don't have the issue on Endeavour OS which I would have expected to be closer to my sys

I’m trying to make a custom iso with archiso, currently I just have the standard profile with plasma-meta, kitty, and xorg-xinit installed. When booting the iso the shell is zsh as expected, but when I launch kde with startx it changes the shell to bash.

I’m not sure if this is because I’m using the root account rather than a normal user, or if it’s something weird to do with using startx as I usually use SDDM on an actual install, I’m not having much luck with Google as I just keep getting results telling me how to automatically run startx when logging into bash/zsh.

The shell for root is listed as /usr/bin/zsh in /etc/passed so chsh makes no difference, but echo $SHELL returns /bin/bash

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.

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)

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 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

I tried the shutdown troubleshooting steps from here: 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

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

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

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?

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.

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

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

My current setup is a NAS running on an old Acer Aspire laptop with an Intel core i5-6500u and 8GB RAM (and an Nvidia 920m but I'm pretty sure its not using that as I'm running headless Ubuntu server and haven't installed the Nvidia drivers) with a 3.5" HDD plugged in via USB.

The main things I like about this setup are that its cheap (I already own it), fairly low power, and pretty quiet. I guess the built in UPS is a bonus as well!

The main reason I want to upgrade is so I can easily add more drives, either for redundancy or just more storage. The USB can also be a bit janky, sometimes after first powering on it fails to read the drive and I have to power off the hard drive caddy for about a minute, this does seem to be an issue with the devices itself though as I've had it do it with multiple drives in multiple PC's. It would also be nice to get the laptop back even though I don't use it much.

Currently its just acting as a NAS, but I would definitely like to set up Jellyfin as w

I undervolted my CPU about a year ago and haven't had any issues with it till now. I've been dual booting Linux recently and noticed whenever I was in Linux it would crash/reboot after a couple of hours or less of using it. I noticed the behavior was similar to when I set the voltages too low when initially setting up the undervolt so I disabled it and haven't had any crashed since. Any idea why it would be stable on Windows but not Linux? I tried a couple of different distros as well. I'll probably just raise the voltage until I get it stable again but I'm interested to know what could cause this! If its relevant my CPU is a Ryzen 7 3800x

I use DisplayPort audio as my main output, and it seems there is a slight delay between the sink being started and me actually hearing anything (the audio isn't delayed I just miss the start). I've managed to mostly fix it by disabling suspend on idle, so now once I've played some audio once its fine.

However when I reboot I then miss the first bit of audio again. I have no idea what I need to do to fix this. If I try to manually enable the sink with with pacmd suspend 0 I still get the same issue. The only potential fix I can think of is to set a KDE startup command for pacmd play-file and point it to a very short silent audio file. Does anyone have any better ideas?

Edit: I forgot to mention, when suspend on idle is enabled there is an audible pop every time the audio starts and suspends. With suspend on idle disabled I still hear this pop on login (and the first time audio is played) which suggests something is happening when I log in

Edit 2: Apparently it still does it every tim

Apparently os-prober is a security risk but tbh I don't really understand the issue. I've read its something to do with mounting all partitions as root, but you have to run grub-mkconfig as root anyway so I don't see how that could be used to gain root privileges? Does it not unmount them afterwards? And could you avoid the risk by just disabling it again after you've generated your grub.cfg?

The other option seems to be manually adding a Windows entry to /etc/grub.d/40_custom so I assume thats the recommended way to dual boot?