virt-manager @3.2.0_2 [quartz, [+]x11] Monterey python GTK crash

[GRMrGecko (Mr. Gecko)]

Hello,

I'm trying to get virt-manager setup on my mac to manage remote hosts. I installed using the standard port install, without any modifications. Started dbus, and ran with the following command.

virt-manager --no-fork -c 'qemu+ssh://grmrgecko@10.0.0.5/system'

Upon running, it seems to crash with a GTK memory move error with a SIGTRAP. Google searching, I found ticket #63891 which looks to have a similar error occurring with another python GTK program. This means the error is likely at the python GTK level and not specifically this port. But I figured it would be worth opening a ticket to help others track this issue.

[GRMrGecko (Mr. Gecko)]

Crash report from MacOS.

[mascguy (Christopher Nielsen)]

It certainly could be related to issue:63891, but I'll need to take a closer look.

Also CCing @michaelld, for visibility and collaboration.

[michaelld (Michael Dickens)]

Yes this looks like the same error. Traceback is identical for the last ~15 calls. I strongly doubt this issue is GNU Radio or Virt specific, but rather something to do with code in PyGObject or GTK3 or glib or (more generally) Gnome.

[michaelld (Michael Dickens)]

It's actually good that that this one is with +x11 rather than +quartz ... I for years have used +quartz & thus often wonder when there is a bug whether that is the issue. Guessing not with this one, which reduces the search space for the bug .. yay!

[dm3jan (Janek)]

are you on M1 or Intel?

[michaelld (Michael Dickens)]

The crash report is for ARM64.

For folks with this issue and -not- building as +universal, can you please try the following:

Edit the glib2 Portfile. Find the entry for universal.patch and remove that line & save the file. Now build glib2 from source, uninstalling the prior version before installing this version. That takes care of this issue for me & should for you too. I think I've come to a conclusion as to how to fix the issue for glib2 2.64 ... but not yet for the current release (2.70).

[michaelld (Michael Dickens)]

In 0519ce19a5703e6dc556d87a782059c53bcb7698/macports-ports (master):

glib2: fix section of universal.patch impacting ARM64 to match glib2-devel

Ref (should close, but let's get external feedback):
#64377
#64192
#63891

[mascguy (Christopher Nielsen)]

@GRMrGecko, are you still seeing crashes, after updating all of your ports?

[mascguy (Christopher Nielsen)]

I believe this was resolved via the fixes for various ports, including @michaelld's changes for glib2.

If this is still an issue, please let us know!