Hi Tim, I can confirm that the gtk3 version bump fixes the issue. Thanks for the update, and for the recommendation to try a new gtk theme. With responsibility for maintaining thousands of CRUX ports, it's understandable that you prefer not to waste time on patching the ports that haven't kept up with the system libraries. In this case a fix was quickly posted to the system library itself, but some libraries might not be so accommodating. For those cases, dropping the old software in favor of a modern alternative is a simple resolution to the breakage that would otherwise persist in the port tree. But by not taking the opportunity to provide feedback to upstream developers, we leave them completely unaware that their user base extends into the CRUX community. To quote the Japanese proverb, "the protruding nail gets hammered." The upstream github sites might be filled with bug reports from users on Mac OS X or Windows, with hardly a peep from the CRUX users who silently moved on to an alternative at the first sign of outdated code. Due to our silence (and to their remoteness from the development of the system library they depend on), the upstream project has no idea that the GUI they wrote prior to gtk 3.10 is in need of a rewrite, and they focus their attention on the internals of the app rather than its GUI. I'm not advocating holding sentimentals for old software, but instead doing our part to improve the software we once saw fit to include in our repositories. Dropping a port at the first sign of trouble is too drastic a response, if the upstream github site is active and responsive to constructive feedback from users on other platforms. -- John