Created attachment 607200 [details] traceback Description of problem: virt-manager does not work with the latest gtk-vnc Version-Release number of selected component (if applicable): # rpm -qa gtk-vnc* gtk-vnc-0.5.1-1.fc17.x86_64 gtk-vnc2-0.5.0-2.fc17.x86_64 gtk-vnc-python-0.5.1-1.fc17.x86_6 How reproducible: Just start virt-manager. Additional info: Error starting Virtual Machine Manager: /lib64/libgtk-vnc-1.0.so.0: undefined symbol: vnc_connection_open_addr
Me too.
What version of the 'gvnc' RPM do you have ?
It works after yum update today. Thanks! before version # rpm -qa gtk-vnc* gtk-vnc-0.5.1-1.fc17.x86_64 gtk-vnc2-0.5.0-2.fc17.x86_64 gtk-vnc-python-0.5.1-1.fc17.x86_64 after is here # rpm -qa gtk-vnc* gtk-vnc-0.5.1-1.fc17.x86_64 gtk-vnc2-0.5.1-1.fc17.x86_64 gtk-vnc-python-0.5.1-1.fc17.x86_64
gtk-vnc-0.5.1-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gtk-vnc-0.5.1-4.fc18
gtk-vnc-0.5.1-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gtk-vnc-0.5.1-4.fc17
Package gtk-vnc-0.5.1-4.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk-vnc-0.5.1-4.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-13311/gtk-vnc-0.5.1-4.fc18 then log in and leave karma (feedback).
gtk-vnc-0.5.1-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
gtk-vnc-0.5.1-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.