Krip
BRip indeed
BSo I'm stuck at windows basically
EAfter setting up rEFInd to manage the dualboot between Windows and Bazzite I updated Windows and now rEFInd does not work anymore. Does anybody know how to fix this? If I go to the boot menu in the BIOS I can only pick between Bazzite and Windows, but there isn't the rEFInd option anymore
Aneed to re-setup refind, windows updates will occasionally bork it.
Egot it thanks, just had to run again "sudo refind-install" and even the custom theme is still there
SAnyone know how to set custom boot parameters
Hrpm-ostree kargs --helpSThanks, disabled the amd_pstate kernel fallback to acpi_freq and everything is back to normal. 49c :p
Mrunning ujust update
Mpray for no black screen 
Mpraise be
Mit didn't break this time
Ahow do i reorder controllers in steam input
Anow i ask the noobie questions lmao
Hfrom what i remember it can only be done in gamemode and you do it on the right side menu and it should be an option somewhere there
RYeah, fair enough.
RI preferred to leave it more verbose for readability, but it's fine even like that XD
RThanks for repinging this 
RYeah, it was Valve's code that was assuming only LCD in the latter case.
R(LCD Display I mean)
RThey fixed it afterwards using an external enum but balika never updated patches for whatever reason.
RAnd I got annoyed enough to rebase it on latest master, it wasn't much code anyway.
R(More time on reading monitor basic terminology though, like the good old front porch and back porch /s)
ROh, but you have additional displays in.
RYeah, that might break stuff in your fork.
RValve should handle display matching using another system TBH.
Kyeah, that's why I changed it
Kworks the same way the LGO & Loki work now
RYeah, saw that.
RThe additional basic setup for undocking and no HDR might be worth even for the other displays.
R(Like my enum added below)
ᕲlol no problem. someone alerted me it wasn't working so I looked into it and discovered ur version of the patches
R(Just add them to the enum and add them in an or in that if).
RHaven't seen any other place in gamescope that applies specific display patches at least.
TPeeps - when do you think we be a good time to switch to 40. I am assuming it is something like normal Fedora "wait a couple of weeks"
Related question - is getting on the 40 train as simple as allowing the updates from the Discover app use the 40 version of the fedora platform
Related question - is getting on the 40 train as simple as allowing the updates from the Discover app use the 40 version of the fedora platform
TI didn't pin to 39 but I am holding off allowing that update to go through
TI rolled back to 39
KI did same-day we launched, no issues here
KIf you're on :39 you will have to manually rebase in the terminal
KThere's no way to do that from a GUI
Jdid kde discover get oci support yet?
KWhat you're looking at is flatpaks, totally separate
JI remember it's on the roadmap but no idea if it got implemented
TOK so allowing that update to go through won't move me to 40?
TI had a bunch of display issues with 40 and the related changes in window managers
KRight, just the flatpak platform
TWait was that flatpak comment to me?
TBecause I never did a CLI update - only through the Discover platform
Rzap looks fire @Kyle Gospo XD
