rotopenguin

99% of the time, that means SteamOS is getting sleeby and needs a reboot. (Some component of wine or something is not very good at cleaning up itself. You could try to chase it down, but trust me just rebooting is easier. Welcome to Linux.)

I'm so old, I remember when instead of "crypto" it was "Amway".

ProtonTricks may be the app for your problem. It can run Winetricks specifically targeting the prefixes that Steam sets up for each individual game. Soo, (I do not have BG3) run Protontricks, pick the game, wait, find that Winetricks starts off at a really awkward point in its UI, pick add an application, cancel, find yourself at a better menu, choose "Install a Windows DLL or component", and check off the appropriate dot net version.

I think that the Deck's touchscreen and keyboard code is just not a priority at all. It has to be barely good enough to type in your wifi password. From there, you scan a QR code to sign in to Steam (which was absolutely an amazing development), and maybe type in four letters to search for a game you want to install.

Direct manipulation of the keyboard is awkward because you aren't holding the screen very closely like on a phone. Doing that is more like "gorilla-grip one side, and poke keys with your other index finger quickly, before you drop the damn thing". In addition to that, the keys don't register very well, possibly because it doesn't have a phone's clever DWIM heuristics. And even when you're trackpad typing, the keyboard laaags, because we only have eight 3.4 ghz logical cores 🤪.

As far as I'm concerned, valve has the right priorities. Keep their noses to the Proton and Vulkan and Gamescope grindstones. Make it so that nobody ever feels the need to wipe and reinstall their system to fix some unfathomable bug. The keyboard can keep right on sucking, so long as "make games just friggin work" moves forward.

*laughs to the tune of "I bet this mf has never even heard of a devicetree" *

Go easy on Apple, they can't afford the extra TWO BUCKS of the cheapest most commodity silicon on Earth.

I don't like how soft the tap to click is on the trackpads. I bump the click threshold up to about 9000.

On Desktop mode, I made a controller config that binds the shoulder triggers to just be shoulder triggers. Use the right trackpad as mouse, click as LMB. Left trackpad as scroll wheel (vertical), click as RMB. It would be nice if there was a real 2d scrolly-polly mode that I could bind to the left trackpad, instead of having it emit mousewheel button events.

When it comes to typing on the deck, I cry. It's terrible. Carry around a folding keyboard if things come to that.

I just spent two weeks trying to convince a new intel Zenbook laptop to have decent battery life. It would eat the battery both awake and asleep. Went through the Arch wiki on suspend issues. Discovered that the bios has a broken vestigial S3 suspend (which more and more vendors are shipping); the modern suspend mode is now S0ix (s2idle). Found that my system was only getting into C2 and C3 out of C10 levels of S0ix power-saving-state nirvana.

Somehow, I lucked upon finding that the Intel Rapid Storage/VMD setting in bios was what kept the processor from ever going to lower power states. Once I disabled that, nearly everything else fell into place. The cpu ran cooler at normal use, battery lasted longer, and power burn during sleep went from 4% an hour to negligible.

This was fun. Not one tool successfully pointed me at the real problem. It took one random dell support post to set me on the right path. https://bugzilla.kernel.org/show_bug.cgi?id=211879. I spent two weeks chasing the same problem that somebody else had in 2021. Linux doesn't have a [WARNING] for detecting a damned VMD, and it doesn't have a means to tell the VMD to fuck off? The stupid hardware doesn't have the sense to not fuck up the processor if it isn't attached to its Windows-only driver? I don't understand how anybody has been able to use an intel for the last couple of generations if this is how they work.

In conclusion - battery life is actually pretty great now. But it was a bloody nightmare to get here.

The fun part is that tab completion insists on putting the slash there.

One major failure mode of SSDs is that they can corrupt their FTL map. That kills all of the data instantly.

(Now, a major reliability advantage of SSDs is that by being faster, you can also make a backup of them faster. And if backups goes faster, you're more likely to actually do them. Right? Right!?)

Musk offers to pay l̶e̶g̶a̶l̶ bills o̶f̶-p̶e̶o̶p̶l̶e̶-u̶n̶f̶a̶i̶r̶l̶y̶-t̶r̶e̶a̶t̶e̶d̶-f̶o̶r̶-p̶o̶s̶t̶i̶n̶g̶-o̶n̶-p̶l̶a̶t̶f̶o̶r̶m̶

There, does that sound any more believable?

Lunar Lobster has 0.26.5, which is from November. Coulda gone with something a little fresher, but it isn't that severely out of date.