Aleksei Bavshin

Nothing else sets or uses `wayland->cursor.theme_name`, so IMO the patch could be simplified to ```c wayland->cursor.theme_name = (char *)g_getenv("XCURSOR_THEME"); ``` somewhere in the `wayland_display_setup`

I stopped looking into that direction when I found that none of the launchers I'm aware of can provide `app_id`. I.e. if you take `rofi -show drun`, `wofi`, `fuzzel`, `nwg-`anything,...

The static assignment needed for LANG/MOZ_ENABLE_WAYLAND/QT_QPA_PLATFORM/etc... seems to be already solved with [`environment.d(5)`](https://www.freedesktop.org/software/systemd/man/latest/environment.d.html), right? What do you want to achieve by parsing environment.d files with another tool and sending the...

Something like this should be more accurate ```cpp // g++ $(pkg-config --cflags --libs wayland-client) wl-compositor-exit.cpp #include #include #include int main(int, char **) { auto *display = wl_display_connect(nullptr); if (display ==...

> > Ah, I understand. It should look like this?: > > session_cleanup () { > ... > } > trap session_cleanup INT TERM > > # Set the default...

I'm afraid that is a correct behavior. Wayland does not offer info about the currently focused output, partly because it is considered a sensitive information, partly because it doesn't make...

> I was thinking of using cairo device scaling but I have yet to code anything. Would reworking the draw code to use it remove the need to know the...

> Having this, too. But I think restarting by `SIGUSR2` is not a workaround, it's actually triggering the duplication. That's a good catch. I'm finally able to reproduce the issue...

Thanks! The patch works for me both locally and in the package build environment.

That is fine, I'll just skip the testcase in the RBTools package spec and reenable it when we get a fix. No other packages were affected so we can wait.