gtk3-nocsd doesn't seem to work with wayland

[Luticus]

I'm using this on debian bullseye and on the wayland desktop it doesn't seem to do much of anything. Is there any chance this can support wayland?

[neon64]

What's your window manager/desktop environment? I've got it partially working inside of sway by setting the env vars before I launch sway from cmdline. However certain apps launched with wofi as an application launcher don't yet work.

Also maybe try this fork here: https://github.com/ZaWertun/gtk3-nocsd which is what is used in the Arch AUR package and seems to be more up-to-date.

[Luticus]

I'm using Debian with KDE Plasma 5.17.

I've tried this with Dino IM and remmina. It seems to work when I launch the programs using an xorg session, but once I launch in a wayland session it doesn't seemingly nothing. I'll check out the fork and see if I can mess with that.

[neon64]

Where are you putting the environment variables at the moment? .Xsession won't be read on a Wayland-only session (seeing as its just for X sessions). I have used ~/.pam_environment and it works nicely?

[Luticus]

Didn't know that was a thing. I basically just installed from Debian repos and ran with it. I'll look into the environment vars.

[Luticus]

Ok, I put them in a script in ~/.config/plasma-workspace/env and that made it work on Debian Bullseye. That's probably only good for the KDE environment though, but it suits my purposes. I think this should probably be a bit more automatic on install in a wayland environment when installed from an official distro package, but maybe that's a packaging thing. Also of note is that my method would not help someone who wanted this to work as a global solution. My fix is user specific. If there's any advice on properly globalizing this it might be nice to know. Whatever the case, it's technically fixed for me for now. Thanks for the help!

[miklcct]

Can confirm that it doesn't work OOB on Wayland but running it with the wrapper works.