+++ This bug was initially created as a clone of Bug #537489 +++
abrt detected a crash.
Comment: Trying to open a console in virt-manager of a machine on another host.
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
reason: Process was terminated by signal 6
--- Additional comment from firstname.lastname@example.org on 2009-11-13 15:35:19 EST ---
Thanks for filing this bug.
From the backtrace, it looks like an assertion failed; frame 2 of thread 1 has:
Assertion `*lock == ((ath_mutex_t) 0)' failed.
in _gcry_ath_mutex_lock, deep inside gvnc_start_tls (frame 21) within gvnc_initialize (frame 24).
So it looks like an assertion failure deep inside gvnc's TLS code, which causes the process to abort.
Reassigning component from "python" to "virt-manager" in the hope that someone with knowledge of that domain can assign it to a more appropriate component.
He or she will probably want to know which version of virt-manager, libvirt, etc you have installed.
--- Additional comment from email@example.com on 2009-11-13 15:41:49 EST ---
Here's the versions of those two:
...let me know if you need other info.
--- Additional comment from firstname.lastname@example.org on 2009-12-17 13:42:02 EST ---
Fix built in gtk-vnc-0.3.10-2.fc12
This fixes the problem as far as GTK-VNC is concerned. It'll likely still crash though because of an identical bug in libvirt https://bugzilla.redhat.com/show_bug.cgi?id=544305
Created attachment 413700 [details]
Fix gcrypt threading initialization
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Fix built in gtk-vnc-0.3.10-2.el6
Could you please retest with the latest RC?
This is quite hard to reproduce, but in my testing there were no further crashes.
Thank you for your report.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.