Bug 1012042 - Associate with .vv files at installation
Associate with .vv files at installation
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: mingw-virt-viewer (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Marc-Andre Lureau
Desktop QE
Depends On:
  Show dependency treegraph
Reported: 2013-09-25 11:24 EDT by Tomas Jamrisko
Modified: 2013-09-25 12:50 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-25 12:50:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Jamrisko 2013-09-25 11:24:20 EDT
Description of problem:
remote-viewer isn't associated with vv files after installation. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install remote-viewer
2. get a vv file and try opening it (by double clicking) 

Actual results:
It doesn't work unless user manually finds the executable

Expected results:
It should set the appropriate registry keys at installation
Comment 1 Marc-Andre Lureau 2013-09-25 11:49:50 EDT
How did you install the virt-viewer? Only the MSI supports mime registration.
Comment 2 Tomas Jamrisko 2013-09-25 12:31:52 EDT
installed through rhevm user portal -> it was the cab file.
Comment 3 Marc-Andre Lureau 2013-09-25 12:50:32 EDT
Then this isn't supported on purpose. We don't want to mix cab or msi installation. Ie, if you use the portal with MIME, (or open vv files), then you have to install the MSI. The CAB client installation approach is hopefully getting away.

Note You need to log in before you can comment on or make changes to this bug.