Is that not what KDE Discover and Gnome Software Center do? Or is this a new one for Gnome?
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 30,000 people per million. Consider the fact that the .03% of people in this figure are those who report this bug to Riot.
Perhaps not inclided in the .03% are people who lost their install and:
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.
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
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?
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.
If they can get full vulkan, maybe Zink can take care of the rest
Pcie ASPM off would hurt battery life a lot wouldn’t it? What sad do you have?
I agree the joke is played out. IIRC, radios would play them because people wouldn’t typically dislike their music so much that they’d change the station or turn the radio off. A lot of music is quite polarizing so people love it or hate it and will leave the station when they dislike a song. Nickelback had a little of every rock genre under the sun, so while some people loved them, few people hated or disliked them.
But then they were overplayed and more people who were on the fence got tired of it. A bit like Mariah Carey’s Christmas song and some of Fallout Boy’s songs.
I think two great ways to manage this are
1: using permissions the user can see and grant/deny “Allow persistent background usage” or something like that with a tooltip or something that warms the user about resource usage. IIRC, this is already a thing in Android 14.
2: providing visibility into background app usage and history. They do this to some degree, but it’s not as good as it could be. Especially when I want to know what is draining my battery when my phone is in my pocket.
That sounds about right
I agree desktop is not top priority. And I know their money largely comes outside Desktop. In fact, I would be surprised if consumer products came close to their b2b products. Just saying they have more than zero incentive to care about the Linux desktop. And apparently, Nvidia agrees, because they are finally putting more effort in.
I still use and recommend AMD for Linux desktop, and I’m hoping Intel will become competitive in that space so we have more options and competition. I personally don’t like how closed off, uninvolved, and impassive Nvidia has been in general and I don’t trust them in general to collaborate much, as shown by their history.
Well they do lose some business in the Linux world to their issues and will probably take some time to recover their reputation in the Linux desktop community. I know not everyone hates them and the Linux Desktop community isn’t huge right now, but there is some incentive to show the world you care about your customers
And if Linux Desktop ever gets super popular and easy for everyone but Nvidia, that’s not a necessary risk Nvidia should take. And the catching up later on could be really slow and painful if Nvidia lets themselves get even further behind. GPUs are among the most complicated hardware components to support and develop drivers and other software for.
It wouldn’t shock me. A lot of improvements to 14 are reeling in idle usage. In fact, that’s a big focus on the last 3 or 4 Android versions, and something Android is doing to catch up to iOS.
It seems better for battery life to do batching and budgeting of background activities as much as possible, instead of continuous, unregulated usage.
I think the one thing I miss is that Android used to have idle background battery usage estimates, so that you knew which apps were killing your battery in the background. It’s not quite as easy to figure that out anymore, but maybe something new will come along to help out with that.
Sad spyware and adware noises