CThis might be a bit of a shitty take, but i never understood the hype with hdr - all my displays have hdr, just never really cared about it. Thought the jump would be as significant as 60hz -> 120/144hz but it was pretty underwhelming. OLED imo is a much higher jump.
ROLED is a higher jump but significantly more expensive and less accesible than HDR
His your steamdeck the oled version, if yes then it has HDR
other than that you will have to check your monitor specs
other than that you will have to check your monitor specs
RMy keyboard now works again.
RI have no clue why today from terminal it has decided to show me a pairing code and then would not accept ANY input. I reconnect it now and magically it start working again.
DI just have the regular steam deck
RI have no clue.
Dit's possible that an update fixed it
RRNope, it still won't pair from any graphical utilities
RAnd it is still the not previously working 5.70
RThese appeared when I could associate with the keyboard and had no input.
DI thought you said it got paired
RFrom bluetoothctl
RFor whatever reason.
RIt would not pair at all from KDE or SteamOS
R**Game Mode, i mean
Dit needs to be fixed
RThe HID failed to bind it, but I doubt that the issue is the HID itself.
RIt's probably still the bluetooth layer that was providing wrong data to it if you ask me.
RAnd now magically, no update, no reboot
Rhid-generic 0005:046D:B33D.0009: input,hidraw4: BLUETOOTH HID v28.03 Keyboard [Keyboard K480] on I have no clue on what is happening, but I hope that 5.71 will be merged as soon as possible.
RAt least I have one less variable to exclude.
Cout of curiosity, is there a plan on how to handle F40's dropping of x11?
Cjust going along with it or trying to keep it i your build?
Hi might remember wrong but i think i read somewhere when i first joined here that x11 would be kept around for nvidia if it was still needed at that point.
PI'm using the x11 session on bazzite, but when I open the games it shows me that I'm using Wayland
PI need x11 to play Star Citizen, because in Wayland Nvidia there is a bug in the cursor
KWe already ship wayland by default
Kthe plan is to just do it
Kif Nvidia still has issues by then I'll include the missing x11 session in nvidia builds
CYeah I know wayland is on there already and the default compositor. I mainly ask because I need to use x11 to get sunshine to work as it seems to find no encoders on wayland and I'm on amd
CI totally get not wanting to try and support a whole extra compositor though
Cso I'm not asking you to add it in just for me lol
Hi think it is going to be a while before sunshine fully supports wayland, if we are lucky we get full support next year. since atm it "technically" works on wayland but technically working is not practically working 
CYeah I don't have a ton of hope for sunshine. The dev still hasn't pushed a build to the f39 repos
Cand the flatpak works in 39, but only in x11.
RIt's nvidia, of course it will /s
Hthey arent a very big team last time i checked, but i do believe they will get it done eventually
Cthe moonlight devs are responsive at least
Cmy experience with the sunshine devs has mostly been them saying "read the docs" about issues that aren't covered by the docs
Cit's honestly kind of baffling how there's no direct xrandr equivalent on wayland
Hwould be nice, i am kinda tired of my sddm login to be sideways on my 3rd monitor 
KGitHub
Description
Add fedora 39 image, and drop fedora 37.
Screenshot
Issues Fixed or Closed
Type of Change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change whi...
Add fedora 39 image, and drop fedora 37.
Screenshot
Issues Fixed or Closed
Type of Change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change whi...
Cit's like they expect users to pump in commands directly to dbus to change the display settings if they need to do something via terminal
Kxrandr works in KDE Wayland
Kand we ship gnome-randr for GNOME Wayland
CI ame aware. Go ahead and search sunshine on the repos
Cit's not there
