http://bugzilla.novell.com/show_bug.cgi?id=617480
http://bugzilla.novell.com/show_bug.cgi?id=617480#c27
--- Comment #27 from Chunyan Liu 2010-07-09 02:58:25 UTC ---
About the console problem when using virt-manager, from virt-manager.log and
virt-manager & vminstall source code, did not find problem in virt-manager or
vminstall code. From log, the last two lines:
------------------------------------------------
[Mon, 05 Jul 2010 19:05:16 virt-manager 26343] DEBUG (console:654) Starting
connect process for vnc://localhost:5900: localhost 5900
[Mon, 05 Jul 2010 19:05:16 virt-manager 26343] DEBUG (console:492) VNC
initialized
------------------------------------------------
virt-manager's open connect to vnc console is successful. "Starting connect
process for vnc://localhost:5900: localhost 5900" printed just before
open_host, and when logging "vnc initialized", vnc console is already
connected. Until now, most of work has been done. After that, only
set_current_page to console-pages left.
And from log, there is no "disconnect" signal (otherwise, there will be log
like "vnc disconnceted") or window close trigger (otherwise, there will be log
like "window counter decremented to *" and vnc console will also close) or
window errors.
So, from the log, it seems no problem in virt-manager or vminstall workflow.
But since virt-manager calls libgtkvnc APIs to conncet and display VNC console
(open_host is also a gtkvnc API), which might be different from vncViewer's
implementation, I'm not sure if there is potential problem inside libgtkvnc. We
do not have source code of that part to investigate.
Do we have libgtkvnc maintainers?
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.