what can i say, the best distros are also maintained by the smartest people
what can i say, the best distros are also maintained by the smartest people
Tthanks but the only known compromised distros were Debian Sid and very specific builds of Fedora Rawhide that were known as "Fedora 41"
Tthe exploit had to meet certain requirements too regarding linking to the library
Agot it
Msome arch distros as well but I believe they’ve all taken care of the issue by now
Tyeah arch patched it and is urging users to update asap
Tsupply chain attacks are terrifying
Chow do i format my ssd
Ci mean
Cthe sd
Calso why is everything in desktop mode so zoomed in
Tscaling issue you can change that in system settings
Tgaming mode > system > format sd card
Cwhat system settings
Tdisplay and monitor
Cty
SReminds me of this https://www.theregister.com/2016/03/23/npm_left_pad_chaos/
Code pulled from NPM – which everyone was using
Toh yeah i heard about this one too lol
Dthere was some guy who intentionally broke his nodejs library, node devs had to step in to restore it on npm
Cbruh
Cwere people really incapable of writing 11 lines of code
Qsolaar listener keeps dying and requires restarting the app to get it to recognize my login devices again 
Tis there a way to keep the screen from dimming while playing media via a browser?
SI was curious about bazzite's vulnerability to that xz cve a few days ago but I pushed it to the back of my mind since I knew an update was going to be pushed if it was affected. Checking deeper relieved me further aha, though I'm sure bazzite users weren't really the main target of the bad actors unless they were trying to build a botnet lmao
Tit's a supply chain attack, but it was found quick enough before making it beyond the testing channels/rolling release distros
Tit affected fedora rawhide's 41 builds
Tbazzite is still using fedora 39 builds
SMhm I had noticed! Thanks for the quick info haha
SAlso
SThat issue I had? Found the solution. You have to enabled developer settings in the System tab in game mode.
S
SAbout to update the github issue and the help channel ticket
TSwitching my congestion algorithm to cubic has solved my network lag spike issues while streaming my PS5 to my Go. Might be my home network or might be something with the Go.
KTysm as always 
Are there any special settings, that I need to take care of?
And I assume, if I use GNOME as my DE, I should go for the bazzite-arch-gnome image, right?
Are there any special settings, that I need to take care of?
And I assume, if I use GNOME as my DE, I should go for the bazzite-arch-gnome image, right?
Hyes, gnome image for gnome DE
Kty
VI get a lot of audio crackling when watching videos or things like that, as if the CPU or RAM were being severely taxed. I have an AMD 5600x and 32 GB of RAM, not to mention an RTX 2080 for hardware acceleration. Yet anytime I'm especially screensharing, I get all these issues like the videos not wanting to buffer and audio crackling.
Is this also related to XWayland issues?
Is this also related to XWayland issues?
VIt's not all the time but it's enough to be annoying
SI get them every few minutes on the ally using chiaki. How'd you do that ?
KIs it a bad idea to rebase to the :latest image instead of :stable?
Tit's the same thing
KOh okay
T:latest:stable:latest:testingthen it goes
:unstableKSo if I wanted to try the hhd 2.4.0 update, I would either have to wait for the new version to be reflected in stable or try testing?
Toh idk if the new verisons is in testing
KHey I noticed fedora silverblue is much faster when it comes to upgrading the system vs bazzite. At first I thought it's because of my slow internetspeed. But that can't be, because I tested it on both systems.
Then I thought it might be, because of the number of layered packages, but even silverblue with many layered packages like virtualization, waydroid etc ... is still miles faster.
Is that something, that's going to get better over time?
and can you maby simplify, why it's slower in general?
Then I thought it might be, because of the number of layered packages, but even silverblue with many layered packages like virtualization, waydroid etc ... is still miles faster.
Is that something, that's going to get better over time?
and can you maby simplify, why it's slower in general?
GThanks for mentioning this. Helped me today.
Tyeah it's slower because we have more packages in the image and it's pulling nearly 3GB from the GHCR. upstream plans fix this later with diffd updates
