Description of problem: Connect a guest with virt-viewer -v,then close the console,there is no return at the end of last line. Version-Release number of selected component (if applicable): virt-viewer-0.5.2-8.el6.x86_64 How reproducible: always Steps to Reproduce: 1.Start a guest. 2.Run #virt-viewer -v rhel6.2 or # virt-viewer --verbose rhel6.2 3.Close the console Actual results: # virt-viewer --verbose rhel6.2 Opening connection to libvirt with URI <null> Guest rhel6.2 is running, determining display Guest rhel6.2 has a spice display Opening direct TCP connection to display at localhost:5901:-1 Guest rhel6.2 display has disconnected, shutting down[root@dhcp-*-* ~]# Expected results: It should have a return at the end of line of verbose info,like this: # virt-viewer --verbose rhel6.2 Opening connection to libvirt with URI <null> Guest rhel6.2 is running, determining display Guest rhel6.2 has a spice display Opening direct TCP connection to display at localhost:5901:-1 Guest rhel6.2 display has disconnected, shutting down [root@dhcp-*-* ~]# Additional info:
Should be pretty easy to fix this.
I've sent a patch for this https://www.redhat.com/archives/virt-tools-list/2012-September/msg00044.html
And it has been ACK'ed and pushed upstream, moving the bug to POST.
This bug can be reproduce by following build: virt-viewer-0.5.2-9.el6.x86_64 Verified pass on the following build: virt-viewer-0.5.2-13.el6.x86_64 Steps: 1. Run virt-viewer $guest --verbose 2. Close the window. Actual result: [root@KP-T1 ~]# virt-viewer T1 --verbose Opening connection to libvirt with URI <null> Guest T1 is running, determining display Guest T1 has a vnc display Opening direct TCP connection to display at localhost:5901:-1 Guest T1 display has disconnected, shutting down [root@KP-T1 ~]# So mark this bug as VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0361.html