geany-0.18 Integrated compile feature hangs

[marspeoplester@…]

I'm using MacOSX 10.6.2 and updated packages.

When I run the integrated "Build > Compile" of Geany for any source file of several languages (I tried C++, Pascal, Python) it does the compiling, showing the messages if any, but afterwards the Geany IDE becomes totally unresponsive: I can't open menus, edit text, etc. Then I have to kill the process.

[jmroot (Joshua Root)]

Please remember to cc the maintainer and don't set the Milestone field.

[nox@…]

Could you try again now that I've updated geany to 0.18.1?

[marspeoplester@…]

Replying to nox@…:

Could you try again now that I've updated geany to 0.18.1?

The problem persists in 0.18.1

[diogratia@…]

Cc Me!

[diogratia@…]

Cc Me!

[diogratia@…]

Cc Me!

[diogratia@…]

The problem shows up for me in geany 0.18.1 and older versions under a fresh port 1.8.2, running Mac OS X 10.5.7. Same thing in a geany-0.25.1 compile outside of macports (depending on macport /opt/local/lib libraries for gtk, etc.).

Some menu pull downs are blank and if you can guess where a button are you can get an action. Sometimes the menus are totally unresponsive.

It appears the windows comprising geany aren't getting updated, or the wrong ones are being displayed on update (erroneous double buffering issue?) The impression is that the problem is either in gtk or gdk. Works under kubuntu 9.04 with geany-0.18.1. (I'm trying to do something cross platform). Doing a 'Make Custom Target' and doing anything that will complete gives visible effect. When the make exits the problem occurs. Same for any other make.

From my limited experience when users (and we qualify) see these things and developers don't, it relates to execution environment that modifies behavior differently. I tend to see lots of gnome and KDE things. One example that comes to mind is gtkwave, which would crash until you threw out your configuration tree, then when the tree is reintroduce magically work right thereafter. Blowing off your ~/.kde stuff does wonders to fixing first time run problems.

If I had to hazard a guess this relates to how gtk is built and a missing constraint somewhere. The fault could be in geany, the gtkwidget operations seem sparse there. I found this ticket when looking for inspiration on fixing the problem.

[diogratia@…]

Replying to diogratia@…:

"Same thing in a geany-0.25.1 compile outside of macports ..."

Sorry crossed wires, long night. Just 0.18.1, but both in and out of macports.

[marspeoplester@…]

Replying to marspeoplester@…:

I'm using MacOSX 10.6.2 and updated packages.

When I run the integrated "Build > Compile" of Geany for any source file of several languages (I tried C++, Pascal, Python) it does the compiling, showing the messages if any, but afterwards the Geany IDE becomes totally unresponsive: I can't open menus, edit text, etc. Then I have to kill the process.

I've just built the newly released geany 0.19 directly from source and noticed that this bug does not happens anymore in my tests. Hopefully, it will be solved when geany is upgraded to 0.19 in Macports.

However, I see now that the "Execute" command always generate a "segmentation fault" here, but that is a smaller problem to me.

[jmroot (Joshua Root)]

Seems fine with version 0.20 (r77045).