abrt 1.0.0 detected a crash.
How to reproduce
1. connect to remote host via TLS
2. try to open vnc console (also nested in TLS)
3. wait for a while (it not deterministic, so you may be lucky enought not to experience a crash)
remote vnc sessions doesn't work. what is worse, a crash of virt-manager can lead to a crash of virtual machine on a remote host you are trying connect to. host is using qemu-kvm from git tree (head at d0be25...f72848)
using vinagre i have never noticed such problems.
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py --no-fork
reason: Process was terminated by signal 6
Created attachment 376096 [details]
Thank you for reporting this bug.
How reproducable is this problem? If you run the program from a terminal, is an error message printed?
What version of virt-manager do you have installed?
Looking at the backtrace, it looks like an assertion failed inside frame 2 of thread #1 inside _gcry_ath_mutex_lock.
Reassigning component from "python" to "virt-manager"
(In reply to comment #2)
> How reproducable is this problem?
i would say the probability is around 0.95 whenever i try to open a graphical console and stick around for a couple of seconds.
> If you run the program from a terminal, is
> an error message printed?
yes it is. but there is nothing that cannot be found in the backtrace:
$ virt-manager --no-fork
/usr/share/virt-manager/virtManager/manager.py:150: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
self.window = gtk.glade.XML(config.get_glade_dir() + "/vmm-manager.glade", "vmm-manager", domain="virt-manager")
python: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
Aborted (core dumped)
> What version of virt-manager do you have installed?
0.8.0-7 and 0.8.0-8. both produce the same results.
Needs this libvirt fix
But also requires a similar patch to gtk-vnc
To me, this would seem to seriously affect usability, and there appears to be a fix. Any estimates as to when a new package will be available on the libvirt side?
*** Bug 591503 has been marked as a duplicate of this bug. ***
Sorry about the delay on this bug, I'll build a libvirt update this week.
libvirt-0.7.1-16.fc12 has been submitted as an update for Fedora 12.
libvirt-0.7.1-16.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 libvirt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libvirt-0.7.1-16.fc12
The -16 patch definitely solved this problem for me. I could reproduce it consistently and I cannot any longer.
libvirt-0.7.1-16.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.