Re: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy

On Tue, Dec 17, 2013 at 11:26 AM, Tomas Jelinek wrote: Please note that on F19 I have: spice-xpi-2.8-3.fc19.x86_64 and on F20 I see there is spice-xpi-2.8.90-1.fc20.x86_64 SO does this mean that only in upcoming Fedora 20 (right today... ;-) one would have spice-xpi functionality? This test seems to confirm: I'm doing further testing on f19 client with spice-gtk3-0.20-6.fc19.x86_64 (spice-gtk not installed, is it correct?) spice-xpi-2.8-3.fc19.x86_64 virt-viewer-0.5.6-1.fc19.x86_64 firefox-26.0-2.fc19.x86_64 I changed proxy (10.4.4.63) port to 80 as at the moment is the only opened on that lan. I changed accordingly the engine config and restart hypervisor ip is 10.4.4.59 1) if I select native client option I correctly get the console window for a VM and in netstat tcp 0 0 10.4.23.21:44980 10.4.4.63:80 ESTABLISHED 2) If I select browser plugin for the same VM I get error and I see with netstat that it is trying host ip and not proxy one tcp 0 1 10.4.23.21:51365 10.4.4.59:5901 SYN_SENT In terminal session before launching firefox I have set: export SPICE_DEBUG=1 What I get when I try console via spice-xpi is: (plugin-container:15279): SpiceXPI-CRITICAL **: controller connect: No such file or directory (plugin-container:15279): SpiceXPI-CRITICAL **: controller connect: No such file or directory while in f20 I get, also with spice plugin: tcp 0 0 10.4.4.67:32850 10.4.4.63:80 ESTABLISHED and in ps output: gcecchi 2145 1 1 09:33 ? 00:00:01 remote-viewer --spice-controller Hope that can get it also on Fedora 19, if the bug referred for 6.x and resolved in 6.5 is this one I found: https://bugzilla.redhat.com/show_bug.cgi?id=994613 should be "only" a matter to port upstram patch to fedora 19, correct? Thanks, Gianluca