Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
virt-manager core dump at the first launch via ssh(w/ X forwarding)
Version-Release number of selected component (if applicable):
libvirt-daemon-1.1.1-29.el7.x86_64
libvirt-daemon-driver-secret-1.1.1-29.el7.x86_64
libvirt-daemon-driver-nwfilter-1.1.1-29.el7.x86_64
libvirt-python-1.1.1-29.el7.x86_64
libvirt-daemon-driver-lxc-1.1.1-29.el7.x86_64
libvirt-daemon-driver-nodedev-1.1.1-29.el7.x86_64
libvirt-daemon-driver-storage-1.1.1-29.el7.x86_64
libvirt-debuginfo-1.1.1-29.el7.x86_64
libvirt-docs-1.1.1-29.el7.x86_64
libvirt-client-1.1.1-29.el7.x86_64
libvirt-glib-0.1.7-3.el7.x86_64
libvirt-daemon-config-network-1.1.1-29.el7.x86_64
libvirt-daemon-config-nwfilter-1.1.1-29.el7.x86_64
libvirt-glib-debuginfo-0.1.7-3.el7.x86_64
libvirt-daemon-driver-interface-1.1.1-29.el7.x86_64
libvirt-daemon-driver-network-1.1.1-29.el7.x86_64
libvirt-daemon-driver-qemu-1.1.1-29.el7.x86_64
virt-manager-0.10.0-20.el7.noarch
openssl-1.0.1e-33.el7.x86_64
python-2.6.6-53.el6.x86_64
ssh client side:
openssl-1.0.1e-17.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.install and bring up libvirt and it's relative services
2. ssh connect to virtualization server
ssh -Xlroot IP
3.virt-manager
Actual results:
virt-manager core dump
Expected results:
program works well
Additional info:
working fine when exec 3. the 2nd time.
Comment 2Giuseppe Scrivano
2014-04-02 14:23:44 UTC
I couldn't reproduce it, I tried to connect both from Fedora 20 and from RHEL-7.
Why do you have python-2.6.6-53.el6.x86_64 installed on your system? Could you try to upgrade Python?
Comment 5Giuseppe Scrivano
2014-04-03 09:09:43 UTC
still I couldn't reproduce it but from your codedump it seems like this problem was already reported. I am going to close it as a duplicate, please re-open if I am wrong.
*** This bug has been marked as a duplicate of bug 986768 ***