we have now the 4.9.7 version

It seems that I have an issue with a software : Rollback RX Pro. If i restart Veyon service, the connection is OK. If i restart Rollback service, Veyon is disconnecting. It seems that Rollback is closing Veyon waiting port 11100. But rollback seems to not use this port... I sent an email ton Rollback support ta have potential answers

consider using key authentication may solve your problem.

Install Ubuntu 20.04.1 Name: "student" "01"-pc Password: 789qwe@ Update and Upgrade SSH sudo apt install openssh-server sudo service ssh status sudo ufw allow ssh sudo service ssh restart Enter the user as sudoers - /etc/sudoers Open the terminal Use the sudo nano command Modify the file using nano, on the last line add "student01-pc ALL=(ALL) NOPASSWD: ALL Save the nano with CTRL+O Veyon Download from GitHub https: //github. com /veyon/ veyon/ releases/ tag/v4.8.0 (It is recognized as a link. Please join the parts, otherwise it won't let me post.) (I use this version; it always works for me) I always install it using the Ubuntu program installer. Configure and Test the keys Extension Install gnome-shell-extension-prefs Disable desktop icons Disable unused software Install the package sudo apt-get install gnome-tweaks Open "Settings" -- First tab "General" --- Turn off "Animations" It works like this here: if I don't follow this order, I can't get Veyon to work. It doesn't allow access to the keychain, which is basically what it needs to locate the machine. In case of problems, I use ssh to stop the service with sudo systemctl stop Veyon and start it again with sudo systemctl start Veyon

When using "Query nested user groups" veyon master takes 3 long minutes to launch, so WOL for the other solution would be appreciated !

Thanks a lot, I will try it!

No one else has wake on lan problems ?

Bonjour, j'ai eu le même souci, et ça venait de notre serveur DNS qui faisait des doublons d'enregistrements pour certains PC.

DE: Wir haben vor ein paar Tagen herausgefunden, dass dieses Problem erscheint, wenn 2 Monitore am PC verbunden sind und zwar, wenn es auf „Erweitert“ eingestellt ist. Leider hat uns das nicht weitergebracht, da wir 2 Bildschirme auch brauchen. Ansonsten haben wir nichts Neues über dieses Skalierungsproblem bei der Demo-Funktion herausgefunden. ENG: We found out a few days ago that this problem appears when 2 monitors are connected to the PC, specifically when it is set to “Extended.” Unfortunately, that didn’t help us any further, since we also need 2 screens. Apart from that, we haven’t discovered anything new about this scaling problem with the demo function.