Description of problem: We have a CentOS 6.5 VM with xfig-3.2.5-23.a.el6.x86_64 installed. We have found that if you create a text area in a figure, typing a space character causes the user interface to freeze. The VM still running. You can log in with ssh and shut it down. The cursor can be moved around but it remains an "I-bar" instead of an arrow. None of the GNOME 2 panel functions can be used and Ctrl-Alt doesn't work. Sending Ctrl-Alt-F2 from virt-viewer doesn't seem to do anything. I could not find any other character besides space which causes this problem. Version-Release number of selected component (if applicable): spice-server-0.12.5-2.fc20.x86_64 qemu-kvm-1.6.2-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3.6-1.fc20.x86_64 virt-manager-1.0.1-4.fc20.noarch How reproducible: Happens every time. Steps to Reproduce: 1. Create a VM, install CentOS 6.5, run updates, install xfig, and login. 2. Run xfig. 3. Click on the Xfig toolbar button for Text entry. 4. Click on the diagram to place a text field 5. Press the space bar Actual results: The cursor in the text field disappears. The mouse cursor remains an "I-bar" and you can't do anything else. Expected results: The space should be entered in the text field and the UI should continue operating normally. Additional info: The same problem happens in RHEV 3 when connecting from remote-viewer and spice-html5. We are using the virtual desktops to run electronics design software and Xfig is the IEEE standard for figures.
Should be fixed when https://lists.nongnu.org/archive/html/qemu-devel/2014-10/msg01207.html reaches the QEMU you are using, and when the guest QXL driver gets http://lists.freedesktop.org/archives/spice-devel/2014-October/017598.html
qxl patches are in f22 plus, as are qemu patches Let's use this bug to track backporting the qemu fix to f21: commit 9e5a25f1c209ff51e4b65124a3b76dd3f1b0fb49 Author: Marc-André Lureau <marcandre.lureau> Date: Fri Oct 10 19:05:11 2014 +0200 qxl: keep going if reaching guest bug on empty area
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
qemu-2.1.3-8.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/qemu-2.1.3-8.fc21
Package qemu-2.1.3-8.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing qemu-2.1.3-8.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9599/qemu-2.1.3-8.fc21 then log in and leave karma (feedback).
qemu-2.1.3-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.