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 component: python executable: /usr/bin/python kernel: 2.6.31.5-127.fc12.x86_64 package: python-2.6.2-2.fc12 rating: 3 reason: Process was terminated by signal 6
Created attachment 369479 [details] File: backtrace
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.
Here's the versions of those two: virt-manager-0.8.0-7.fc12.noarch libvirt-0.7.1-15.fc12.x86_64 ...let me know if you need other info.
Sounds like this is gtk-vnc code, reassigning there.
*** Bug 538074 has been marked as a duplicate of this bug. ***
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
gtk-vnc-0.3.10-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gtk-vnc-0.3.10-2.fc12
gtk-vnc-0.3.10-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gtk-vnc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-13469
gtk-vnc-0.3.10-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.