I'm not an expert, but IIUC there are many moving parts and some possible 
configurations are:

1. x.org X11 with Gnome WM and GTK talking X11, thats the traditional setup, 
and therefore the one _most likely_ to be stable until the components start to 
bitrot
2. Wayland compositor such as Gnome and GTK talking Wayland to it, thats the 
future, but still new, some have found that to be stable, but YMMV, and unknown 
if they used full screen
3. Wayland compositor such as Gnome and GTK talking X11 to Xwayland that talks 
Wayland to the compositor, waaay too many moving parts, a GTK that expects the 
old fashioned weirdness of x.org talking to a new implementation on top of 
Wayland that does not have all the features of x.org is bound to be buggy IMO.

So the first thing is to be absolutely sure what the setup is, newer distros 
like Fedora or Arch default to a wayland compositor, so its setup 2 by default, 
but setting `GDK_BACKEND=X11` when running Geany will use setup 3 IIUC.  But 
you should be able to select Gnome on x.org at the login dialog to get setup 1.

It would be great if you can test all the combinations and report which work 
fullscreen/maximised and windowed, which don't work, and which work really 
badly.

Once you have the worst combination (so its nice and repeatable) run Geany 
under GDB (see HACKING) and when its frozen type ctrl+C in the GDB window and 
get a `bt` to show where its stuck.  Probably important to repeat this to be 
sure that its the same place (the lowest level function locations may change if 
its polling but it should be down the same basic rabbit hole of calls).  Hard 
to do if fullscreen unless you have two screens though.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2658#issuecomment-780201706

Reply via email to