TigerVNC Server inside vm collides with noVNC console

[skraw]

Hello,

I tried to make a VNC service work inside a vm with TigerVNC. I had to find out that there seems to be a problem related to the noVNC console of the vm. You cannot start tigervnc server by systemd in the vm (arch linux), because of this crash:

(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xvnc (OsLookupColor+0x139) [0x55f47506f929]
(EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x60) [0x7f8536bbf98f]
(EE) 2: /usr/bin/Xvnc (_ZN14XserverDesktopD2Ev+0xd3) [0x55f474fce1c3]
(EE) 3: /usr/bin/Xvnc (_ZN14XserverDesktopD0Ev+0xa) [0x55f474fce32a]
(EE) 4: /usr/bin/Xvnc (vncExtensionClose+0x28) [0x55f474fc28a8]
(EE) 5: /usr/bin/Xvnc (CloseDownExtensions+0x31) [0x55f47502f701]
(EE) 6: /usr/bin/Xvnc (dix_main+0x3d0) [0x55f47501f9a0]
(EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0x7f8536445153]
(EE) 8: /usr/bin/Xvnc (_start+0x2e) [0x55f474ef16de]
(EE)
(EE) Segmentation fault at address 0x8
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

After googling around a bit I found several posts where the very same happens for a vmware installation. Obviously something collides in both Proxmox noVNC and vmware console.
Is there some way to prevent this collision?

--
Regards

 

[skraw]

PS:
Here is a link to the exact same problem:

https://bbs.archlinux.org/viewtopic.php?id=246256

 

[Chris]

Hi,
this bug seems solved https://bugs.archlinux.org/task/62449
Maybe try to recompile the tigervnc package as it was last updated in july and is flagged as outdated since october https://www.archlinux.org/packages/community/x86_64/tigervnc/