Install Updates Graphical Glitch

[Şerban S.]

https://askubuntu.com/questions/844323/e...mapped-wit

"It seems that the Gtk devs decided to add this warning which affects a number of packages. We just have to wait for the Zenity dev to catch up and fix Zenity "

Probably still relevant.

TC

Unfortunately, the same error message appears in Gambas 3.14.3 when running some apps.
I've been working on an app I need for myself and I got tons of messges identical with this quoted in the article.
It seems that the message is included somewhere in a GTK superclass and for whatever reason it is triggered in some situations. As I see things, the parent window should be provided as a default option in all error cases, based on a filter internally contained in the class that triggers the message. So, might be a conditional missing or somewhat.
It's an abnormal exiting situation that was supposed to be caught by the Error system and at least throw an exception or whatever that could be further analysed.
However, the message is the same allover the place.
Now, I see it pops out in the installer/updater code so the bug is deeply hidden somewhere.
Might be a ton of reasons so for now, I guess all we can do is wait to see how this goes on in the devs team.
Maybe there is a bug report on that and it awaits the availability of a dev to solve it.
Unfortunately, both my knowledge and interest in digging for those kind of things is close to none.
I assume if there is a bug report on that, people ignored it since I belive in GTK 3.x (latest looks is 3.24.x) the bug will be elliminated.
In my program, there was something related to an "Event Loop call", which I never understood what was supposed to mean.
I never wrote code to call any event NESTED. Procedures, yes, but never called events (event handlers) recursively so it goes beyond my understanding what the message was supposed to mean.
Subsequently, it triggered this GTK warning, repeatedly.

Bad thing is that we can only see this happening but for what can we do, as I see, nothing is clear.
When I first looked at the screenshots, I recognised the behaviour from my own experience. In my case, it was a glitch due to GPU driver overlapping. I solved it removing the Intel driver that caused the glitch.
Now it looks that here is a different thing though.

Hope that will go away in the LL 5.0 updates.

Best regards!