Bug 1297864

Created attachment 1114025 [details]
remote-viewer log

Hi Andrei,
What are the implication of this bug? Does it mean the end user would not be able to reopen the remote-viewer and will have to kill the first process first, in order to start a new one?

Also, is this true when you open the remote-viewer from RHEV portals or only when you run it manually?

There are two cases.

The first one. In "console options" "Native client" is selected. In this case remote-viewer.exe process remains running after I close it. I can re-open connections to the same VM as much as I wish. But, at some point client's OS can go out of memory.

The second one. In "console options" "Browser plugin" is selected. This case is much worse than the first one. It doesn't allow to re-open connection to the same VM. As I close remote remote-viewer Internet Explorer thinks that RV is still running and IE doesn't allow to open new connection. Summarizing up, I can connect only once to the same VM.

Works for me on a Win7 x64.

Installed:
  SmartCardManagerSetup-1.1.0-13.win32.i386.exe
  CoolkeySetup-1.0.0-2.win64.x64.exe
  virt-viewer-x64-2.0-8.msi ("VirtViewer v2.0-128" directory)

Followed steps in comment #0 (using a regular cmd shell)
Tried connecting both from command line to a "local" VM and using
RHEV-M with a vv-file (Native Client)

Uri, do you see a registered coolkey module?

.\modutil.exe -dbdir 'c:\ProbgramData\nssdb' -list

Does your Win7 have latest updates from Microsoft?

What version of coolkeypk11.dll do you use? 32 or 64 bit?

n
 (In reply to Andrei Stepanov from comment #5)
> Uri, do you see a registered coolkey module?
> 
> .\modutil.exe -dbdir 'c:\ProbgramData\nssdb' -list
> 
> Does your Win7 have latest updates from Microsoft?
> 
> What version of coolkeypk11.dll do you use? 32 or 64 bit?

Andrei, can you confirm that before update it worked properly?


In any case it it is not a blocker for 3.6.

(In reply to Andrei Stepanov from comment #5)
> Uri, do you see a registered coolkey module?
> 
> .\modutil.exe -dbdir 'c:\ProbgramData\nssdb' -list

C:\Program Files\VirtViewer v2.0-128\bin>modutil.exe -dbdir "\ProgramData\pki\ns
sdb" -list

Listing of PKCS #11 Modules
-----------------------------------------------------------
  1. NSS Internal PKCS #11 Module
         slots: 2 slots attached
        status: loaded

         slot: NSS Internal Cryptographic Services
        token: NSS Generic Crypto Services

         slot: NSS User Private Key and Certificate Services
        token: NSS Certificate DB

  2. SpiceGemalto
        library name: \windows\system32\coolkeypk11.dll
         slots: 1 slot attached
        status: loaded

         slot: QEMU QEMU USB CCID 0
        token:
-----------------------------------------------------------


> 
> Does your Win7 have latest updates from Microsoft?
> What version of coolkeypk11.dll do you use? 32 or 64 bit?

I tested on both 32 and 64 bit Windows 7.
The 64 bit Windows 7 is updated.
The 32 bit Windows 7 is freshly installed.

The coolkey version is 
SmartCardManagerSetup-1.1.0-13.win32.i386.exe

To make it clear: "Works for me" means that I can run remote-viewer and
connect to a remote VM, and when I close remote-viewer (tried both using
menu File -> Quit and clicking on right-most corner x (close) button),
Windows Task Manager has no entry for remote-viewer.exe

An MSI installer was used to install virt-viewer

oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.

Andrei, can you please try to reproduce on 4.0 ?

I can reproduce it with rhevm-spice-client-x64-msi-4.0-2.el7ev.noarch

/usr/share/spice/virt-viewer-x64.msi

installed on Windows 7 64 (with recent updates)

I managed to reproduce this bug on Win 64bit client

oVirt 4.2.0 has been released on Dec 20th 2017. Please consider re-targeting this bug to next milestone

As there is no real reproducer and the effects are not very serious, closing this as WONTFIX.