virt-manager crashed when opening a VM on remote host

[kraynovm]

I've successfully installed virt-manger by the following fix #170 (comment) on BigSur. But when I'm trying to open console or properties window to a VM virt-manager just crashed.

[ср, 21 июл 2021 21:06:32 virt-manager 12983] DEBUG (serialcon:17) Using VTE API 2.91
[ср, 21 июл 2021 21:06:32 virt-manager 12983] DEBUG (xmleditor:12) Using GtkSource 4
[ср, 21 июл 2021 21:06:33 virt-manager 12983] DEBUG (guest:320) Setting Guest osinfo name <_OsVariant name=generic>
[ср, 21 июл 2021 21:06:33 virt-manager 12983] DEBUG (vmwindow:184) Showing VM details: <vmmDomain name=contrail-upgrade-m1 id=0x10ef3ab00>
[ср, 21 июл 2021 21:06:33 virt-manager 12983] DEBUG (engine:316) window counter incremented to 2
[ср, 21 июл 2021 21:06:33 virt-manager 12983] DEBUG (console:721) Starting connect process for proto=vnc trans=ssh connhost=<hostname> connuser=<user_acc> connport= gaddr=0.0.0.0 gport=5902 gtlsport=None gsocket=None
[ср, 21 июл 2021 21:06:33 virt-manager 12983] DEBUG (viewers:433) VNC connecting to host=<hostname> port=5902
/usr/local/opt/pygobject3/lib/python3.9/site-packages/gi/overrides/Gio.py:42: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  return Gio.Application.run(self, *args, **kwargs)
Python(12983,0x104861e00) malloc: *** error for object 0x111d24740: pointer being freed was not allocated
Python(12983,0x104861e00) malloc: *** set a breakpoint in malloc_error_break to debug
[1]    12983 abort      virt-manager --debug -c  --no-fork```

[dmasiero]

Same scenario for me except I'm on Catalina 10.15.7. Any update on resolution?

[louisza]

Same scenario for me. On Big Sur.

[irtec]

same case in Catalina, is there any solution

[obazda20]

same on macOS Big Sur Version 11.4

[tinsjourney]

did anyone find a solution for this ?
still having the issue even if I'm using repo from @Krish-sysadmin, as mentioned #184 (comment)

[xcenai]

Issue still persists. Mojave 12.0.1

[DirkDuesentrieb]

In my case virt-manager crashed only if a VM with SPICE and VNC graphics was running. If this is the same for you, please test, if this workaround helps:

• stop the VM
• edit the VM settings with virt-manager
• remove the VNC display
• add it again (Listen type: address, only localhost)
• start the VM

The different order of adaptors fixed it for me.

[Gelob]

In my case virt-manager crashed only if a VM with SPICE and VNC graphics was running. If this is the same for you, please test, if this workaround helps:

• stop the VM
• edit the VM settings with virt-manager
• remove the VNC display
• add it again (Listen type: address, only localhost)
• start the VM

The different order of adaptors fixed it for me.

This worked for me also

[nicolasjulian]

In my case virt-manager crashed only if a VM with SPICE and VNC graphics was running. If this is the same for you, please test, if this workaround helps:

• stop the VM
• edit the VM settings with virt-manager
• remove the VNC display
• add it again (Listen type: address, only localhost)
• start the VM

The different order of adaptors fixed it for me.

This has worked very well for me. Thank you!

[andrioli]

I'm facing the same issue. Actually I'm using the core brew (https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/v/virt-manager.rb) but the issue is the same. Interestingly, on my old old machine (Intel running Monterey) the issue is happening. On the other hand, on my new machine (M series running Sonoma) the issue didn't show up.

No lucky, The steps above didn't help me 😢