Closed jim-moe closed 3 years ago
Also... lswm seems to have a similar issue with gnome terminal windows.
Thank you very much for reporting. I am pretty busy atm with other stuff, but I would merge any PR fixing this. Best way to approach this is to check via xprop
what changed for firefox in the most recent version and then to adjust the default settings of lwsm.
How do I use xprop
? I tried xprop -name firefox
with no success.
xprop
+ click on the firefox window should work.
Nope
xprop + click
does work, just not on FF or gnome terminal.
Are you using wayland? lwsm does not work with wayland...
opensuse/gnome is using "wayland," a newer GUI. Could that be an issue?
yes! :)
There is no easy fix then?
You absolutely don't need to use wayland, this would be the easy fix :).
Apart from that: As wayland is very much still under development they have yet to provide the functionality to make something like lwsm work.
Just google for "Disable wayland" or something like that. Should be pretty straight forward I assume.
Okay. Thanks.
You're welcome!
lswm v4.0.2 firefox v82.0 gnome 3.36.7
The Window Session Manager no longer recognizes what Firefox is. FF recently updated to v82.0; lswm starts the app, and hangs waiting for some indication that FF has started. If I reset lswm (to clear the hang) and start FF again while an instance of FF is already running, a new instance of FF is started, and lswm hangs waiting for the new one.