Programming => Widgetset => GTK => Topic started by: tkapias on September 08, 2021, 02:43:54 pm
Title: Blank window with a 60sec timeout before any Lazarus/GTK2 app starts
Post by: tkapias on September 08, 2021, 02:43:54 pm
Distribution : Debian GNU/Linux 11 (bullseye) Kernel : Linux 5.10.0-8-amd64 GPU : Intel 82G33/G31 (opengl 1.3) WM : i3wm with picom
Hello,
When I open any Lazarus/GTK2 application, I get a blank window that will timeout after 60 sec and the application will appear then. If I kill this blank window the application lauch directly and the CRITICAL output resulting from my kill is always the same :
If I wait for the timeout there is no output and everything works fine.
This issue appeared to me when I tried to use Cudatext. I opened an issue with them (https://github.com/Alexey-T/CudaText/issues/3704 (https://github.com/Alexey-T/CudaText/issues/3704)).
But I got the same issue with any other application using Lazarus and GTK2. No problem with the QT5 version of the same applications.
I tried this demo : http://uvviewsoft.com/c/gtk2_slow/ (http://uvviewsoft.com/c/gtk2_slow/) and took a capture that you can view in the Cudatext issue.
I don't know how to debug this.
Title: Re: Blank window with a 60sec timeout before any Lazarus/GTK2 app starts
Post by: zeljko on September 08, 2021, 03:16:16 pm
Try to start your application with -disableaccurateframe param and see if that helps.
Title: Re: Blank window with a 60sec timeout before any Lazarus/GTK2 app starts
Post by: tkapias on September 08, 2021, 03:44:00 pm
Is it because my i3wm configuration does not draw window frames ?
Title: Re: Blank window with a 60sec timeout before any Lazarus/GTK2 app starts
Post by: zeljko on September 08, 2021, 07:18:00 pm
Actually I've never tested i3wm in this context, so really don't know.
Title: Re: Blank window with a 60sec timeout before any Lazarus/GTK2 app starts
Post by: mosquito on January 28, 2022, 09:31:50 am
I also use i3wm, with and without Compton. I have the same problem, but:
1. -DisableAccurateFrame works. I do not know if this could be declared at compile time or calling during execution.
2. If I run <Shift + Alt + Q>, I kill "something" that is not my program, and this appears magically.This is what I usually do. If I execute the order again, obviously I kill my lazarus application. Resting container, around my program, appeared I have.
3. If I have opened in this workspace any other window, I do not have this problem.
4. If I execute my laz-app in a empty-workspace, I suffer the problem, but I'll press <Alt + Enter> or I open any other window, the program appears and works perfectly. Apparently the problem comes when the Main-Form tries to occupy all the screen space.
* Alt is for super_mod_key * When the mysterious container appears, apart from the 60 seconds, an incredible CPU consumption. * While this error occurs, My Rofi : xwm.sh does not say anything, quite mysterious.