It works with Sully. You can close this ticket at your discretion.

I switched to Ubuntu because of that. I don't have the bug there. I miss Manjaro. Dear developers, it would be nice if you could advise with test instructions. I don't mind building Geany from source and putting in some debug prints here and there if you let me know where to start. I use Geany like crazy every day, totally love it in fact, so I can't have it freezing on me.

I'll give it try.

BTW, you should look into Manjaro. I really recommend it. It is as user-friendly as Ubuntu, configures everything automatically and whatnot, but has some nice additional features. Most notably 'pacman', the package manager of Arch Linux, which can handle tricky installations much better than apt. This is interesting especially for developers as it can handle multiple installations of the same package with different versions very well e.g. GTK2 and GTK3 or a 32-bit and 64-bit version of the same package. Manjaro comes with the zsh which you will absolutely love. I have even started using it on Ubuntu. And finally, Manjaro comes with a beautiful Gnome desktop, so it is definitely worth checking out. You can run a full-fledged desktop from a live-CD...

Ok, thanks for the help! And also thanks for the work you put into Geany. I'm a power user! Can't use it enough, thanks for that!

@jansalleine : Got your message, thank you! I'll give it a try. Switched from Majaro to Ubuntu because of this bug. Looking forward to some Manjaro time :-)

_I don't know if this comment will be displayed on a closed issue, but I had the same problem on Arch Linux, Gnome 3, X11 Session. In this case my workaround was to edit /usr/share/applications/geany.desktop and change the "Exec" line to: Exec=env GDK_BACKEND=x11 geany %F_

@jansalleine full screen issues have been reported before #1532 and #1787 for eg. But it still comes back to my comment [above](https://github.com/geany/geany/issues/2658#issuecomment-745023264) which I also said on a number of the previous issues as well. Until the problem happens to/for somebody who can (capable and has time) debug it nothing will happen unfortunately.

AFAICT it doesn't happen to any of the regular contributors, but may happen as more systems upgrade to newer and still flakey components like Wayland compositors (Gnome, Sway, etc) and very flakey XWayland. But until somebody debugs the problem its not fixable. IIRC suggestions for debugging were made on previous issues but (perhaps understandably) people just found a workaround and didn't contribute further.

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.

PPS note that fullscreen `view->fullscreen` is different to maximised (using the window decorations) and may behave differently.

@jansalleine is probably not necessary to build Geany, its clear that Geany is waiting for communication, its stopped in the `poll()` system function ([see](https://man7.org/linux/man-pages/man2/poll.2.html)) which is usually waiting for communication from something and there is no Geany code in the backtrace beyond the startup that calls `gtk_main()`, so Geany has not asked for a screen update, or opened a file or anything else, its just patiently waiting for a keypress to be communicated.

It confirms the theory that some keypress communication from the server is going missing, maybe something in the compositor (Wayland) or WM (X11) is interecpting the keypress and holding it, and the main part of both those is of course Gnome, but that doesn't really help us do anything about it I'm afraid.

After hours of aggresive googling and messing up, I found this which works wonderfully to fix this: https://extensions.gnome.org/extension/4028/wandering-pixel/

You're welcome! Glad to know that it worked for you too. It's funny, if we search hard enough, the number of different threads that exist across several websites that talk about the same issue manifesting in different forms, and only a single discussion out of them mention this extension. I was too lazy to go back and post this solution on the other pages, but this was among the first links that popped up when I googled about Geany :)