How is PulseAudio still there? I mean, sure the protocol is still there, but it’s handled by pipewire-pulse on most systems nowadays (KDE specifically requires PipeWire).

Also, PulseAudio was never designed to replace ALSA, it’s sitting on top of ALSA to abstract some complexity from the programs, that would arise if they were to use ALSA directly.

Did you try all of these solutions already? https://wiki.archlinux.org/title/Lm_sensors#Gigabyte_B250/Z370/B450M/B560M/B660M/Z690_motherboards

TBF they only switched to building from git after they were notified of the backdoor yesterday. Prior to that, the source tarball was used.

Swap is only required if you want to hibernate your system, it’s the linux equivalent of hiberfil.sys on windows. When hibernating, the kernel freezes all processes and writes the contents of the RAM to swap (usually a separate partition on the disk), where it can be restored from on the next boot. Since you have issues with sleep/suspend, adding swap won’t help you here, and I also assume PopOS configures swap automatically during the install process anyway. (Also, swap is used as additional memoty in case the RAM is full, so it also functions as the pagefile.sys equivalent.)

Anyway, suspend/sleep may fail due to various reasons. It doesn’t work on my desktop (same symptoms you also have), but works fine on my laptop. The command you executed (sudo kernelstub …) adds a kernel parameter to your bootloader, that advises your kernel to use S3 sleep instead of modern standby (S2Idle), see this wiki article for the differences: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate

Since the kernel is only loaded when you start the PC, my question is: Did you restart your PC after running the command? Check via cat /proc/cmdline, whether the parameter is present. You can also configure this while the system is running via echo deep > /sys/power/mem_sleep (needs to be run as root, i.e. login as root via sudo -i before running it). See also: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate#Changing_suspend_method

If you use a desktop PC I would honestly just disable automatic suspend via the PopOS system settings. If you use a laptop on the other hand, I can understand why you would want sleep to work. You can try reading the Arch Wiki article I linked, it contains a lot of information regarding sleep, but keep in mind that the instructions there are for Arch Linux, not for PopOS, so if the Arch Wiki advises you to change something, you’d have to look up the PopOS way of doing that. Unfortunately I don’t have any further hints I could give you, but I hope this information at least helped you to understand some of the terminology. Best of luck!

Haven’t tried it, but might be worth looking into: https://github.com/vosen/ZLUDA

I assume you already tried disabling WiFi power saving in the steam deck developer settings, right? Just asking because you mentioned this in neither of your two posts and because I also fixed my 5GHz connectivity issues this way.

EDIT: Nvm, overlooked it in your first post.

It doesn’t run GIMP because it’s an OS for mobile phones…

Maybe to be more inclusive towards macOS or BSD users.

Automatic Semicolon Insertion (ASI) has (sadly) been a part of JavaScript longer than 2016. I’m not sure exactly when it was introduced, but this document from 2009 already contains it: https://web.archive.org/web/20120418215856/https://ecma262-5.com/ELS5_Section_7.htm#Section_7.9

IMO it’s bad practice to rely on ASI since the semicolons may not get inserted where you expected them to. The following snippet

const x = 0
const y = x
[1, 2, 3].forEach(console.log) 

is interpreted as

const x = 0;
const y = x[1, 2, 3].forEach(console.log);

which raises a TypeError.

There are more examples of ASI not doing the right thing on the web, so I don’t agree with “Javascript doesn’t need semicolon”.

Sometimes it does take a few seconds for me as well, but not even close to a full minute. That must’ve been on an HDD, right?

The explanation is most likely incorrect though. A more obvious cause of this error is that the current working is the root directory (/) and that they’re logged in as a non-root user, thus trying to create the file /woman without sufficient permissions.

nginx 0.7 😵