Description of problem: When launching a spice url from a browser link (such as spice://localhost:5901), browsers won't launch the virt viewer client. The spice protocol must be registered in Windows in order to do so. Version-Release number of selected component (if applicable): any How reproducible: Steps to Reproduce: 1. In your Windows browser URL window, type this and hit intro: spice://localhost:5901 Actual results: The browser will either try to search for that url or say that there's not any program capable of handling that. Expected results: virt-viewer should be launched and open a connection against the supplied host Additional info: I think the windows installer should register the protocol. Here's a reg file that does it (note that the spice install folder is hardcoded): Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\spice] @="URL:spice" "URL Protocol"="" [HKEY_CLASSES_ROOT\spice\DefaultIcon] @="C:\\Program Files\\VirtViewer v5.0-256\\bin\\remote-viewer.exe,1" [HKEY_CLASSES_ROOT\spice\Extensions] [HKEY_CLASSES_ROOT\spice\shell] @="open" [HKEY_CLASSES_ROOT\spice\shell\open] [HKEY_CLASSES_ROOT\spice\shell\open\command] @="\"C:\\Program Files\\VirtViewer v5.0-256\\bin\\remote-viewer.exe\" \"%1\""
Same applies for VNC protocol. I'm not sure how to integrate this reg setup into our windows installer right now