Red Hat Bugzilla – Bug 864003
no feedback when starting uninstalled remote-viewer
Last modified: 2015-09-07 02:32:49 EDT
Description of problem:
Uninstalling virt-viewer binary on windows 7 client using Add/Remove and later trying to connecting to a VM from User Portal results in a pretty much silent failure
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install remove-viewer through rhevm
2. remove virt-viewer using Add/Remove software in windows
3. Try connecting to a VM from User Portal
a) installer should start
b) user should be notified, that remote-viewer is not installed
Do you keep internet-explorer running while removing virt-viewer (in 2 and 3) ?
What happens if you don't (close internet-explorer as step 1.5) ?
Anything important in spice-x log file ?
Yes, IE has to be running while virt-viewer is uninstalled, it locks SpiceX.dll, which doesn't then doesn't get removed.
It works just fine with IE closed.
Logs of SpiceX show just that cpicec wasn't found.
If the activex would take the "VirtViewerMutex" that would prevent uninstaller from kicking in
Either use the mutex solution proposed in #3 could work or
Perhaps removing /REBOOTOK from nsis script will be enough to inform user that activex uninstall wasn't successfull.
Atm. a reboot should be is easy enough to solve the problem.
The obvious solution is to stop using and supporting activex...
Tomas, don't you get an error from portal after it calls Connect() ? Isn't that enough to investigate error then from the log?
The portal (3.3) doesn't report any error. Events tab for the VM do not indicate any problem either -- green tick with "user initiated console session".
The only error that is logged is by spicex:
'1394187322 ERROR [3352:3392] COSpiceX::Connect: Failed to run spicec (C:\WINDOWS\Downloaded Program Files\spicec.exe --controller) -- 2'
I think that an error like that should be somewhat more visible -- at least no green tick in portal...
(In reply to Tomas Jamrisko from comment #7)
> The portal (3.3) doesn't report any error. Events tab for the VM do not
> indicate any problem either -- green tick with "user initiated console
> The only error that is logged is by spicex:
> '1394187322 ERROR [3352:3392] COSpiceX::Connect: Failed to run spicec
> (C:\WINDOWS\Downloaded Program Files\spicec.exe --controller) -- 2'
> I think that an error like that should be somewhat more visible -- at least
> no green tick in portal...
The error is returned from the Connect() method. I think this is a portal issue. Could someone confirm that portal is not catching errors/exceptions of Connect()?
didn't get to it
i'd like to mention again the last line in comment #5 :-)
we're phasing out activex as much as we can, it is still supported, but we won't be able to fix this in 3.6 timeframe, and in the next release we'll hopefully get rid of it - so closing the bug...