inari@piefed.zip to linuxmemes@lemmy.worldEnglish · edit-21 day agoLinux tipsmedia.piefed.zipimagemessage-square194linkfedilinkarrow-up11.14Karrow-down115
arrow-up11.13Karrow-down1imageLinux tipsmedia.piefed.zipinari@piefed.zip to linuxmemes@lemmy.worldEnglish · edit-21 day agomessage-square194linkfedilink
minus-squareTurret3857@infosec.publinkfedilinkEnglisharrow-up4·18 hours agoWhat WM/DE are you using? (i have no idea if I can help you but this is probably a helpful question for someone who can)
minus-squareGrail@multiverse.soulism.netlinkfedilinkEnglisharrow-up4·18 hours agoKDE Plasma with Kwin
minus-squareErr(()).unwrap()@lemmy.worldMlinkfedilinkarrow-up2arrow-down2·edit-214 hours agoDidn’t KDE just start accepting vibecode? Try running the applications inside Gamescope. It uses a separate toplevel window that shouldn’t be affected by whatever Proton is doing. You could also try either enabling or disabling Wayland in Proton: https://wiki.archlinux.org/title/Wine#Wayland It could also be a quirk of whatever Proton version you’re using. Try GE-Proton, Proton-EM, or an older version.
What WM/DE are you using?
(i have no idea if I can help you but this is probably a helpful question for someone who can)
KDE Plasma with Kwin
Didn’t KDE just start accepting vibecode?Try running the applications inside Gamescope. It uses a separate toplevel window that shouldn’t be affected by whatever Proton is doing.
You could also try either enabling or disabling Wayland in Proton: https://wiki.archlinux.org/title/Wine#Wayland
It could also be a quirk of whatever Proton version you’re using. Try GE-Proton, Proton-EM, or an older version.