Is that not what KDE Discover and Gnome Software Center do? Or is this a new one for Gnome?

You’re right. I missed 2 zeroes.

When you have millions of players, .03% is 300 people per million. Consider the fact that the .03% of people in this figure are those who report this bug to Riot.

Perhaps not included in the .03% are people who lost their install and:

• are not tech savvy enough to even file a report or recover their computer
• gave up or quit trying
• haven’t yet recovered their PC to file a report the usual way
• stuck to reporting issues and seeking help elsewhere, such as on Reddit, perhaps even PC subreddits
• quit when they realized how insane the Vanguard saga is

Riot is has a colorful history and a future of misuing and abusing statistics across the board. It’s practically their modus operandi.

I’ve had a lot of experience with Linux and I use Nobara currently. My only catch with Bazzite is that I didn’t know the first thing to do. It somehow felt as if most of my experience in Linux was just useless.

Not saying it’s a bad thing, I just decided I’d stick to Nobara for now and try learning Bazzite in the future to give it a fair shake.

I’m also a tweaker. I like to play with ZRam and add other things to the OS, like a custom kernel with BCacheFS-Git to support my gaming darastores. I suspect some of my creature comforts may be harder to get.

Yeah, but what if I want:

• pre-2010 graphics
• a free rootkit
• a single ugly stagnant map with no skins
• a single and unchangeable and uninspired drone of an announcer
• a game whose bug-ridden, laggy client leaks memory and processes
• a game whose client prevents you from spectating pro games, past and present
• a pro scene rampant with match fixing and ads injected into the horrendous casting

If not League of Legends, where else am I gonna get all of that from?

Using swap isn’t always a sign you need more RAM. Typically, if you use a computer for a while or have a lot of IO operations going on, Linux will decide to swap some things to make more room for cache.

Sometimes Linux just finds that you have a bunch of inactive app memory and it can swap that out to cache way more stuff. That’s just good memory management, but it’s not worth buying more RAM over

What is a cache file?

I wouldn’t put swap on an SD card, no. Even if it had an NVME, it seems like putting up at least a double-digit percent would be more effective than 1%.

Also, since 6.1, swap has been a lot better, with MGLRU. ChromeOS gets away with paltry amounts of RAM due to swapping. So classic overcommitting seems fine as long as you don’t run into situations where more RAM is active at once than is available by hardware.

I think the question is: if a person is going to make such a tiny swap, why even use swap?

Such a small swap is unlikely to save a system from memory problems and it’s does not seem likely to make a noticeable difference in performance when it’s only able to swap out small amounts of memory.

Why wouldn’t one just put in larger ZRAM or a larger Swap with a reduced swapiness?

If I have a raspberry pi with 1 GB ram, I don’t think a 2 MB swap is worth bothering with.

If they go from the resolution they used to native 4k, they waste a lot of battery life. If they go the other way, you have low res. I think they happened to pick within a golden DPI range. Not too high or low.

On KDE Wayland, I really don’t really see any blurriness issues. I’m not even on KDE 6 yet.

Technology never ceases to amaze me. It’s crazy to think about what ancient people must’ve had to do to get pants on

I don’t think I have this on the latest 6.8 RC. I have one of the RDNA 3 dedicated cards as well. Hope they get it resolved either way.

If helps in the meantime, I think you can often TTY switch in order to restart the display signal. Ctrl + Alt + F3/F4 should get you a new console. Then switch back to your desktop with Ctrl + Alt + F1/F2 (the right one may depend on your distro).

This gets my display fixed when it gets any kind of funky 99% of the time. Sometimes it takes a few tries

This is super cute, haha

I don’t see this behavior on android. Is it impossible that there is some kind of phone battery or memory usage process that’s causing the sessions to be discarded?

And this incident has been reported. As have all your activities, searches, sites, and keystrokes

I really don’t know.

If I had to guess possible reasons off the top of my head:

1: the aux cable and port are a very common for factor for electronics of all sorts, especially computers. So you could probably transfer that data to non-Gameboy devices and not have to manufacturer more proprietary GB ports which you may also have to write drivers for on your non-GB hardware. And your customers would also go through the hustle, if you require them to use your proprietary debugging hardware and drivers, when they inevitably test and debug their own games for your console.

2: in the event of a crash, the kernel might better be able to handle the aux than the proprietary port. Pure speculation by me.

Regardless of any possible reasons or strangeness, it just seems much more probable to me that the behavior of dumping the rom over the audio port is a design choice rather than a coincidence.

It might also be a debugging behavior built into the device

WWJD?

You aired my frustrations really well. He spent a lot more time making claims and discussing his own background than demonstrating Wayland’s alleged issues and showing that they’re egregious. It’s an entertaining rant at best, but that doesn’t make his points valid nor does it make anything actionable.

I agree 4k at higher fps is way better most often he time. Just one use case people may not be aware of for 8k is video editing. You need really high resolution for editing videos else you’re at risk that you introduce artifacts and blurriness when editing. Especially if you decide to zoom or crop.

This applies even if your final video is 4k.

Again, I’m on the 4k120 boat. Just wanted to share one common reason 8k is desired by some people.