inari@piefed.zip to linuxmemes@lemmy.worldEnglish · edit-219 hours agoLinux tipsmedia.piefed.zipimagemessage-square189fedilinkarrow-up11.08Karrow-down113
arrow-up11.06Karrow-down1imageLinux tipsmedia.piefed.zipinari@piefed.zip to linuxmemes@lemmy.worldEnglish · edit-219 hours agomessage-square189fedilink
minus-squareTurret3857@infosec.publinkfedilinkEnglisharrow-up4·9 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-squareErr(()).unwrap()@lemmy.worldMlinkfedilinkarrow-up1arrow-down2·edit-24 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.