[Spice-devel] Userquestion - remote-viewer connection fails with "Connection type could not be determined by URI"

Fri Nov 18 11:46:21 UTC 2022

Il giorno ven 18 nov 2022 alle ore 10:48 Stefan Silberstein
<linuxstony at gmail.com> ha scritto:
>
> Hope this wall of text helps you in any way :D
>
> stony at Aperture-Science:~$ history | grep spice | hexdump -C
> 00000000  20 31 32 30 36 20 20 72  65 6d 6f 74 65 2d 76 69  | 1206  remote-vi|
> 00000010  65 77 65 72 20 73 70 69  63 65 3a 2f 2f 31 39 32  |ewer spice://192|
> 00000020  2e 31 36 38 2e 31 37 38  2e 35 31 3a 35 39 30 30  |.168.178.51:5900|
> 00000030  0a 20 31 32 31 30 20 20  72 65 6d 6f 74 65 2d 76  |. 1210  remote-v|
> 00000040  69 65 77 65 72 20 73 70  69 63 65 3a 2f 2f 31 39  |iewer spice://19|
> 00000050  32 2e 31 36 38 2e 31 37  38 2e 35 31 3a 35 39 30  |2.168.178.51:590|
> 00000060  30 0a 20 31 33 30 39 20  20 72 65 6d 6f 74 65 2d  |0. 1309  remote-|
> 00000070  76 69 65 77 65 72 20 73  70 69 63 65 3a e2 81 84  |viewer spice:...|
> 00000080  e2 81 84 31 39 32 2e 31  36 38 2e 31 37 38 2e 35  |...192.168.178.5|

There you go!

$ echo -e '\xe2\x81\x84'
⁄

that's no a ASCII slash. echo -n / | hexdump -C
00000000  2f                                                |/|
00000001

(one byte, your is 3 bytes, surely not ASCII)

... omissis (a lot more there) ...

> 0000179c
> stony at Aperture-Science:~$
>
> For now I will fade into the shadow of userdom again :)
>
> Stefan
>

Frediano

> Am Fr., 18. Nov. 2022 um 11:25 Uhr schrieb Frediano Ziglio <freddy77 at gmail.com>:
>>
>> Il giorno ven 18 nov 2022 alle ore 06:08 Stefan Silberstein
>> <linuxstony at gmail.com> ha scritto:
>> >
>> > Hi Frediano, Hi List,
>> >
>> > after I was able to start the virtual machine with the GUI I tried your command
>> >
>> > LANG=C remote-viewer spice://192.168.178.51:5900
>> >
>> > and it started right up into the virtual machine.
>> >
>> > HOWEVER
>> >
>> > even
>> >
>> > remote-viewer spice://192.168.178.51:5900
>> >
>> > now opens the virtual machine - without problems. (Yeah - i am stunned myself)
>> >
>> > I slept over it then tried again today - thinking it never worked again the day after...
>> >
>> > Result is that I am able to open up the VM just fine....
>> >
>> > This is the worst - something works without changing anything so I have no chance of knowing what the problem is/was in the first place
>> >
>> > At a loss for words,
>> >
>> > Stefan
>> >
>>
>> Well, problem solved :-)
>>
>> I would check with a command like "history | grep spice | hexdump -C"
>> (you can post the output) for some weird input. The errors you
>> reported are basically (or at least they should) parsing errors for
>> the URI you passed.
>>
>> Frediano
>>
>>
>>
>> > Am Do., 17. Nov. 2022 um 10:30 Uhr schrieb Stefan Silberstein <linuxstony at gmail.com>:
>> >>
>> >> Some details:
>> >> Operating System: Kubuntu 22.04
>> >> KDE Plasma Version: 5.24.6
>> >> KDE Frameworks Version: 5.92.0
>> >> Qt Version: 5.15.3
>> >> Kernel Version: 5.15.0-53-generic (64-bit)
>> >> Graphics Platform: X11
>> >> Processors: 8 × AMD Ryzen 5 1500X Quad-Core Processor
>> >> Memory: 15.6 GiB of RAM
>> >> Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
>> >>
>> >> Opening a Konsole "bash":
>> >>
>> >> Konsole
>> >> Version 21.12.3
>> >>
>> >>
>> >> Locale:
>> >>
>> >> stony at Aperture-Science:~$ locale LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL=
>> >>
>> >> I will try to open it today at noon - during my lunch break.
>> >> (ATM I am glad it works because i gotta work from home and this windows-machine is the only way to connect to the Server in my company for me)
>> >>
>> >> I will get back to you in approximately two hours.
>> >>
>> >> Stefan
>> >>
>> >> Am Do., 17. Nov. 2022 um 10:18 Uhr schrieb Frediano Ziglio <freddy77 at gmail.com>:
>> >>>
>> >>> Il giorno gio 17 nov 2022 alle ore 09:13 Stefan Silberstein
>> >>> <linuxstony at gmail.com> ha scritto:
>> >>> >
>> >>> > Hi,
>> >>> >
>> >>> > no this is the normal forward-slash with "shift+7" on the german keyboard - googlemail messed it up translating it to something else.
>> >>> > The URL  is normally typed.
>> >>> >
>> >>> > This is really weird and I will try to help you as much as I can to get to the bottom of it.
>> >>> >
>> >>> > Stefan
>> >>> >
>> >>>
>> >>> That's pretty weird. That code has been there for ages. I tried but no
>> >>> problems for me.
>> >>> This operating system and version are you using?
>> >>> Which shell?
>> >>> Maybe it's the locale? Try launching something like "LANG=C
>> >>> remote-viewer spice://192.168.178.51:5900" (LANG environment change)
>> >>>
>> >>> Frediano
>> >>>
>> >>> > Am Do., 17. Nov. 2022 um 10:08 Uhr schrieb Frediano Ziglio <freddy77 at gmail.com>:
>> >>> >>
>> >>> >> Il giorno gio 17 nov 2022 alle ore 07:57 Stefan Silberstein
>> >>> >> <linuxstony at gmail.com> ha scritto:
>> >>> >> >
>> >>> >> > Hello again,
>> >>> >> >
>> >>> >> > so - yesterday I worked from home - as I wrote I was able to connect by specifying the user root with "remote-viewer spice://root@192.168.178.51:5900"
>> >>> >> >
>> >>> >> > Today I want to connect the exact same way (yesterday i simply closed the remote-viewer window and the server keept on running so the windows-VM was running the whole night) - and I can not connect.
>> >>> >> >
>> >>> >> > Error Message on the console  "** (remote-viewer:6146): CRITICAL **: 07:55:52.853: virt_viewer_util_extract_host: assertion 'uri != NULL' failed"
>> >>> >> > Error Message on the popup says translated: Connectiontype could not be determined by URI.
>> >>> >> >
>> >>> >>
>> >>> >> Hi,
>> >>> >>    That means that the code was not able to parse the URI.
>> >>> >>
>> >>> >> > IP of the server itself is 192.168.178.51
>> >>> >> > IP of the Virtual Machine is 192.168.178.64 and i pingable
>> >>> >> > Port 5900 on the server is open: 5900/tcp open  vnc
>> >>> >> > remote-viewer --spice-debug spice:⁄⁄192.168.178.51:5900 does not produce a more verbose output :(
>> >>> >> >
>> >>> >>
>> >>> >> In this example you are not using ASCII slashes (//), maybe that's the problem.
>> >>> >>
>> >>> >> > Update in the meantime
>> >>> >> > But maybe this is helpful to you:
>> >>> >> >
>> >>> >> > I simply started "remote-viewer --spice-debug"
>> >>> >> > Then i got the GUI (which i wasnt even aware it existed).
>> >>> >> >
>> >>> >> > When I choose the same entry on that list - I AM able to connect.
>> >>> >> >
>> >>> >> > So the error only exists only when I try to connect via command line?! (This is when I am able to connect tomorrow via GUI ;) )
>> >>> >> >
>> >>> >> > Shouldn't this be the same ?
>> >>> >> >
>> >>> >> > I mabe I can help - maybe this is indeed a bug?
>> >>> >> >
>> >>> >> > Stefan
>> >>> >> >
>> >>> >>
>> >>> >> Frediano
>> >>> >>
>> >>> >> > Am Mi., 16. Nov. 2022 um 09:37 Uhr schrieb Victor Toso <victortoso at redhat.com>:
>> >>> >> >>
>> >>> >> >> On Wed, Nov 16, 2022 at 09:27:21AM +0100, Stefan Silberstein wrote:
>> >>> >> >> > I appreciate the time to answer me.
>> >>> >> >> >
>> >>> >> >> > In the meantime (out of desperation because i needed the virtualmachine for
>> >>> >> >> > work) I gave it a go with specifying root as user and not the servers
>> >>> >> >> > username "server".
>> >>> >> >> >
>> >>> >> >> > I was able to connect to the virtual Windows10 installation with
>> >>> >> >> >
>> >>> >> >> > remote-viewer spice://root@192.168.178.51:5900
>> >>> >> >>
>> >>> >> >> Cool
>> >>> >> >>
>> >>> >> >> > But again - then I dont unterstand why it worked as user and
>> >>> >> >> > later on with specifying the user later on (which doesn't work
>> >>> >> >> > right now anymore)
>> >>> >> >> >
>> >>> >> >> > So it is a permissions problem on my side and I successfully
>> >>> >> >> > wasted your time. :/
>> >>> >> >> >
>> >>> >> >> > Sorry about that.
>> >>> >> >>
>> >>> >> >> Don't worry about that. Happy to hear it worked.
>> >>> >> >>
>> >>> >> >> >
>> >>> >> >> > This happens when "users" try to play with the big boys toys :D
>> >>> >> >> >
>> >>> >> >> > Have a nice day you all and thanks for your time.
>> >>> >> >>
>> >>> >> >> You too.
>> >>> >> >> Cheers,
>> >>> >> >>
>> >>> >> >> >
>> >>> >> >> > Stefan
>> >>> >> >> >
>> >>> >> >> > Am Mi., 16. Nov. 2022 um 09:21 Uhr schrieb Victor Toso <
>> >>> >> >> > victortoso at redhat.com>:
>> >>> >> >> >
>> >>> >> >> > > Hi Stefan,
>> >>> >> >> > >
>> >>> >> >> > > On Tue, Nov 15, 2022 at 09:53:05PM +0100, Stefan Silberstein wrote:
>> >>> >> >> > > > Hello developers,
>> >>> >> >> > > >
>> >>> >> >> > > > I can imagine that this will be an annoying question for you -
>> >>> >> >> > > > so I apologize in advance.
>> >>> >> >> > > >
>> >>> >> >> > > > I am a user - with a longer history with linux BUT i am
>> >>> >> >> > > > completely new to virtualization.
>> >>> >> >> > > > Due to the fact that I got a server donated to me I wanted to
>> >>> >> >> > > > give it a go and it worked like a charm.
>> >>> >> >> > > >
>> >>> >> >> > > > Installed virt-manager, installed Windows10  connected with
>> >>> >> >> > > > virt-manager - absolutely no problem.
>> >>> >> >> > > >
>> >>> >> >> > > > Due to the fact that I need dual monitors I learned that I
>> >>> >> >> > > > could add another display and connect with spice - and it
>> >>> >> >> > > > worked immediately.
>> >>> >> >> > > >
>> >>> >> >> > > > BUT - without me changing anything (consciously) I wasn't able
>> >>> >> >> > > > to connect to the virtual machine the next week.
>> >>> >> >> > > >
>> >>> >> >> > > > It refuses with "Verbindungstyp konnte nicht von URI ermittelt werden"
>> >>> >> >> > > > (Connection type could not be determined by URI)
>> >>> >> >> > > >
>> >>> >> >> > > > Then i tried to connect with sudo and specifying the user in
>> >>> >> >> > > > the command line and it once again connected:
>> >>> >> >> > > >
>> >>> >> >> > > > sudo remote-viewer  spice:⁄⁄server at 192.168.178.51:5900
>> >>> >> >> > >
>> >>> >> >> > > Perhaps the URL is the problem. If the IP is 192.168.178.51 and
>> >>> >> >> > > the port for the VM is 5900, then try
>> >>> >> >> > >
>> >>> >> >> > >     remote-viewer spice://192.168.178.51:5900
>> >>> >> >> > >
>> >>> >> >> > > If server is a dns that can be resolved, should be fine to use it
>> >>> >> >> > > instead of ip address
>> >>> >> >> > >
>> >>> >> >> > >     remote-viewer spice://server:5900
>> >>> >> >> > >
>> >>> >> >> > >
>> >>> >> >> > > > And now - again without changing anything - it doesn't connect
>> >>> >> >> > > > with that command as well.
>> >>> >> >> > > >
>> >>> >> >> > > > I have sadly NO clue whatsoever where to even search for a
>> >>> >> >> > > > solution - the internet didn't help me here...
>> >>> >> >> > > >
>> >>> >> >> > > > Do you have any hint at all what I might do wrong here?
>> >>> >> >> > > >
>> >>> >> >> > > > The machine is available - the port is open and visible
>> >>> >> >> > > > PORT     STATE SERVICE
>> >>> >> >> > > > 22/tcp   open  ssh
>> >>> >> >> > > > 80/tcp   open  http
>> >>> >> >> > > > 3389/tcp open  ms-wbt-server
>> >>> >> >> > > > 5900/tcp open  vnc
>> >>> >> >> > > >
>> >>> >> >> > > > ufw on the server is shut down.
>> >>> >> >> > > >
>> >>> >> >> > > > ANY help would be greatly appreciated.
>> >>> >> >> > >
>> >>> >> >> > > You can get more verbose information of issues with --spice-debug
>> >>> >> >> > > command line option too.
>> >>> >> >> > >
>> >>> >> >> > > Cheers,
>> >>> >> >> > > Victor
>> >>> >> >> > >