Maybe you can login x11 and from there disable HDR ?
Maybe you can login x11 and from there disable HDR ?
GAlso even on X11 I get blank screens unless my monitors are in HDR mode, which is especially odd since there’s no option to even enable HDR
Ktry the command on X11?
GThat’s what I was trying but in an X11 session kscreen just days HDR is unsupported
KI'm trying to search where kscreen-doctor is in the source
KAnyone knows?
ZMmm, another option is login but not with the login manager, but from a tty
GI think that’s what I’m trying right now and I’m getting kscreen errors (maybe because no KDE initialized yet?)
ZGitHub
KDE's screen management software. Contribute to KDE/libkscreen development by creating an account on GitHub.
Gkscreen-doctor output.DP-2.hdr.disable qt.pa.xcb: could not connect to display
qt-gpa-plugin: From 6.5.0, xcb cursora or libxcb-cursorD ts needed to load the Qt xcb platform plugin. gt.qpa.plugin: Could not load the ut platform plugin "xch" in " Even thaugh it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Peven thaugh
ZOnly thing I can think it's modifying manually whatever config file plasma uses to store the HDR param
KYeah I meant that, to see where the config files are
GI’m not even 100% sure that’s what’s causing my issue
ZA lot of ppl were getting black screens with plasma, maybe something to do with config idk
ZSome reported removing certain config files fixed the issue(?) though I would do that as a last measure,
Goh thanks, that's a massive thread it might take me awhile to check out
Kcheck if you have libxcb-cursor package
Galso at this point I'm fine with leaving HDR disabled, I'd just like to get off of X11
ZStrongly inclined to this one Black screen bug with bazzite-nvidia:testing build for explicit sync
Krm ~/.config/kwinoutputconfig.jsonKeasy
Gnot sure best way to do that but rpm -qa | grep libxcb returns a few packages but no libxcb-cursor
ZYeah same behavior almost
KOh, it seems to be in ~/config/kwinoutputconfig.json
Kcheck if highDynamicRange is set to true in the corresponding output
Gbrb rebooting after doing this
Kalso turn off
KwideColorGamut
KI wouldn't do that
G
Kjust change the booleans
K
K"highDynamicRange": false,
"wideColorGamut": false
"wideColorGamut": false
Gok, rebooting after that
Kthat should turn off hdr and if it is the same bug it should work
Gwe in! thank you
Gso it sounds like HDR on nvidia gpus is just broken in KDE plasma until they fix?
Gon 555 or newer drivers
Kyep
KThe thing with this project is garbage in garbage out, as much as I'd like to fix everything, realistically we can only do as well as what we have available can do
KIE: Offer you the best experience we can with what's available today
Kwith any luck KDE fixes this up soon
Kand that is exactly why X11 is remaining available
Gno worries, appreciate the support. The fix was hidden pretty deep in that thread 
GGraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 4: explicit sync is used, but no acquire point is setGmaybe I should just try to find someone who will swap my 3080 for their 6800xt lol
BHey guys quick question. Is the zram better in performance than the 4GB Vram swap from cryo utilities
Tzram is compressed memory and imo thats better than the edge case usage of increasing the swap
KVery important note, using cryo here will likely break things in a very fundamental way
