Athanks to @Emi (legend)
SHey @wolfyreload It seems that xorg fixed my issue but I'm still sad about F40 breaking Wayland.
KThe gaslighting ends today
KWhat do we got?
Ait turns out the resizing issues happens SPECIFICALLY when you have "scale-monitor-framebuffer" ON and "xwayland-native-scaling" OFF
Dat least for us
KI have awful news
KI have both on
KAnd I can prove that from my terminal logs
Di was wondering that
Dhmm
Di'm kinda out of ideas then
Ajust for the shits sake of it
Ajust run a gsettings
KGive me a few
KJust left to get dinner
Dno rush
Agsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer', 'variable-refresh-rate', 'xwayland-native-scaling']"Yeah that is actually letter for letter what's in my terminal history
KI will instead get you a dump of what's actively in there
KBetter proof
Di believe you
Aright
Awell that's the only way we've been able to figure out how to replicate it on our end
Aat least reliably
VBazzite w/ LUKS2 encryption successfully unlocked keybord-less with Yubikey on the Deck. WOOOOOOOOOOOOOOO. Thank you so much for including all the nessessary modules/etc. in the image. :CatDance:
DMulti-monitor didn't make a difference in my testing
KYou can also TPM unlock and skip the key
VI love you guys for this
A(and tbh I don't think there's any reason to not have both those turned on at the same time)
KYeah, and we would ship a dconf to do that on your behalf anyway
Vi like that that's an option, but i'd rather have the security of key or password needed
Vfor a portable system
KOh sure, I just like pointing the stuff out because I feel like if I don't people don't even know they're there
Vmakes perfect sense for a desktop though
KAll the documentation in the world and sometimes it's just totally missed
AIndeed
S
Kthat was me replying to the wrong person
AWell we've at least found some way to replicate it
AWhich is I guess something
KYep, means we're not crazy and we can document it in the MR to get fixed
KAll great news
KSooner that's fixed the sooner I can ship this by default
Aexactly
Dwas this/should this be reported to the patch maintainer?
Aturns out none of us were truly crazy
Ait should probably be reported to the mutter git itself
Abecause that's where the patches are pulled from
Doh it's official?
