@drewloker said in 4.4.2 - Downgrade options? CRASHES Master and Clients, No Demo:

Demo still doesn't work.
I brought the whole lab up to 4.5.4.0
It went to Demo, showed my screen for a few second on a couple of the 7 students logged in a lab of 26 clients. Then, Demo stopped working even on the couple that did get my screen.
I was able to back out of Demo mode with out crashing their computer.

Hello
i have the same problem .. i opened a new topic: https://veyon.nodebb.com/topic/1258/veyon-4-5-4-vnc-serveur-crash-on-demo-mode
where I put the logs to see if tobydox manages to understand what is wrong ...
Fred

I also did manipulation on a machine with Veyon 4.3.5 uninstallation then update to version 4.5.5 .. everything is OK ... I will do other tests on the first PC

@tobydox said in Veyon 4.5.1 I can't open website from Master:

Some technical background: first you should make sure the tray icon is visible on all computers. If it's not visible, the Veyon Service for some reason is not able to run it's own worker processes within the user session. The Veyon tray icon is provided by such a worker process. Launching the "Run program" or "Open website" features also launches a (different) worker process inside the user sessions as a helper process. This worker will then start the program or open the website and this way make sure the program or browser is opened with user privileges (instead of Admin/LocalSystem privileges which the Veyon Service is running with).

On computers where the tray icon is not visible, can you please check the VeyonServer.log file for messages starting with WindowsCoreFunctions and post them here?

Veyonserver.log
https://pastebin.com/Z4bGjPd0

VeyonService.log
https://pastebin.com/BH1And2t

@jrpfahl

Try turning off the Windows Defender Firewall (Domain Network) for one of the Windows 10 computers and try again.

I'm sorry, no good news:

I am having this same issue. I used Veyon 4.4.1 and now I get the C++ Runtime error. The master PC is Windows 7.

@tobydox I just updated to version 4.1.4. indeed the problem was solved. Thank you!!

@tobydox
No problem, you can't be on dev and forum at the same time
Your job is really helpful for a lot of people, thanks for that.

I'd like to be more useful here on the forum, but not "good" enough yet with veyon to help much people.

Regards
ET

@MackenzieP

A tech at a neighboring school advised that rather than entering IP addresses into the Configurator’s Host address/IP field (Locations & computers) to instead enter computer names.

A bit confusing to me but he said to make the Host address/IP field match the Name field when using DHCP assigned addresses.

I started "veyon-server" as a USER directly and got these messages:

08/05/2021 17:42:33 Listening for VNC connections on TCP port 11200 08/05/2021 17:42:33 Listening for VNC connections on TCP6 port 11200 08/05/2021 17:42:33 08/05/2021 17:42:33 Xinerama is present and active (e.g. multi-head). 08/05/2021 17:42:33 Xinerama: number of sub-screens: 1 08/05/2021 17:42:33 Xinerama: no blackouts needed (only one sub-screen) 08/05/2021 17:42:33 08/05/2021 17:42:33 fb read rate: 305 MB/sec 08/05/2021 17:42:33 fast read: reset -wait ms to: 10 08/05/2021 17:42:33 fast read: reset -defer ms to: 10 08/05/2021 17:42:33 The X server says there are 10 mouse buttons. 08/05/2021 17:42:33 screen setup finished. 08/05/2021 17:42:33 The VNC desktop is: localhost:5300 08/05/2021 17:42:33 possible aliases: localhost:11200, localhost::11200 PORT=11200 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 08/05/2021 17:42:33 Got connection from client 127.0.0.1 08/05/2021 17:42:33 0 other clients 08/05/2021 17:42:33 check_access: client 127.0.0.1 matches host 127.0.0.1 08/05/2021 17:42:33 incr accepted_client=1 for 127.0.0.1:40640 sock=24 08/05/2021 17:42:33 Client Protocol Version 3.8 08/05/2021 17:42:33 Protocol version sent 3.8, using 3.8 08/05/2021 17:42:33 rfbProcessClientSecurityType: executing handler for type 2 08/05/2021 17:42:33 copy_tiles: allocating first_line at size 33 08/05/2021 17:42:33 Pixel format for client 127.0.0.1: 08/05/2021 17:42:33 32 bpp, depth 24, little endian 08/05/2021 17:42:33 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 08/05/2021 17:42:33 no translation needed 08/05/2021 17:42:33 rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip 08/05/2021 17:42:33 Using compression level 9 for client 127.0.0.1 08/05/2021 17:42:33 Enabling KeyboardLedState protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling NewFBSize protocol extension for client 127.0.0.1 08/05/2021 17:42:33 Enabling SupportedMessages protocol extension for client 127.0.0.1 ...

Another Client was able to connect now!
So: it runs when the "veyon-server" was started again ... do you have an idea, why it crashes?

First I tried it as root -- but the "veyon-server" didn't start!

... X11 MIT Shared Memory Attach failed: Is your DISPLAY=:0 on a remote machine? Suggestion, use: x11vnc -display :0 ... for local display :0 caught X11 error: 08/05/2021 17:12:29 deleted 32 tile_row polling images. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 130 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 60 Current serial number in output stream: 94

@tobydox said in Veyon for Raspbian?:

this is an interesting use case! Building packages for Debian (no matter which platform/architecture) isn't that complicated, just
have a look at our README file. Besides that we recognized the growing demand for armel/armhf/arm64 binary packages so we
might provide them in the future as well.

Be aware that Raspbian has its own non-standard ABI.
In standard Debian armhf means ARMv7 instructions with hardware floating point.
In Raspbian all Debian packages have been rebuild with ARMv6 instructions, for compatibility with older Pi that do not understand the newer instructions.
They do are compiled with hardware floating point, so it is not armel either.

Any chance you will be maintaining an official Debian package submitted to Debian at some point instead of the current situation?
That would simplify things. Let the Debian derivatives do the compiling, and allow users to just apt-get it.

@Sanny Thank you very much, this is the solution I was looking for!

Thank you for your investigations! I opened an issue at https://github.com/veyon/veyon/issues/420 so we can do further investigations and finally fix the issue.

Hi Tobias,

I just described a similar issue here: [https://github.com/veyon/veyon/issues/455](link url)

Thanks in advance,
Julius

Thank you very much for your feedback!

@tobydox

Hello tobydox

I have created an environment variable in the operating system with a value equal to 2

SET VEYON_SESSION_ID = 2

And also in the veyon-client environment.

veyon-cli config set Service/VEYON_SESSION_ID 2

My session ID is two

QUERY SESSION

SESSION NAME USER NAME ID STATE
services 0 Desc
rdp-tcp # 2 administrator 2 Active
console 3 Conn
rdp-tcp 65536 Listen

And in no case have I managed to make the screen that shows to the students the session in which the teacher works.

I have also test with the new version of Veyon 4.4.0

I would like to remind you that both the students and the teacher are working on their own virtual desktop connected by RDP, that is, they are all in session 2 of their own virtual desktop.

@DrewLoker this is already possible - simply enable the "Show confirmation dialog for potentially unsafe actions" option in the master configuration page in Veyon Configurator - see https://docs.veyon.io/en/latest/admin/reference.html#behaviour for details.

I just switched in General from "use system language" to English US... My local language GUI was really annoying in both Configurator and Master, and in older versions there was no English option for some reason.

In 4.1.0 I just noticed there is English. The moment I switched to English and reopened Configurator, clicking "Start service" worked right away

The line
[WARN] WindowsServiceControl: 'VeyonService' could not be started.
is not showing anymore in .log

So far no errors, everything looks fine. Going to install it on few class PCs and see if Master works without issues.

thanks jgordon.

Tested 4.1.4 still the same problem, when I click the test access button and type "asdf" so not a valid user I still get user has access to control master...