Description of problem: tried to start virt-manager Version-Release number of selected component: virt-manager-0.9.4-3.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: python /usr/share/virt-manager/virt-manager.py kernel: 3.6.9-2.fc17.x86_64
Created attachment 717509 [details] File: executable
Created attachment 717510 [details] File: dso_list
Created attachment 717511 [details] File: environ
Created attachment 717512 [details] File: smolt_data
Created attachment 717513 [details] File: backtrace
Created attachment 717514 [details] File: core_backtrace
Strange, is this reproducible? What's rpm -q gnutls rpm -q libvirt-client
Someone mentioned this on IRC the other day. IIRC, the problem was that they had pulled in a new gnutls from Fedora updates, but had not pulled in the corresponding libtasn1 RPM update. If correct, this would be a bug in gnutls RPMs, not having a good enough dep on the required libtasn1 RPM.
V I C T O R Y comment 8 did the trick Although I had already done a full "yum update", I tried "yum update libtasn1" -- and then virt-manager started fine.
Reassigning to gnutls
*** This bug has been marked as a duplicate of bug 923999 ***