Bug 54885 - 4.4 backport Veyon: Delay in presentation mode on teacher pc
Summary: 4.4 backport Veyon: Delay in presentation mode on teacher pc
Status: CLOSED WONTFIX
Alias: None
Product: UCS@school
Classification: Unclassified
Component: Veyon
Version: UCS@school 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Tobias Wenzel
QA Contact: Jürn Brodersen
URL:
Keywords:
Depends on: 56931
Blocks:
  Show dependency treegraph
 
Reported: 2022-06-21 11:05 CEST by Tobias Wenzel
Modified: 2024-05-16 11:27 CEST (History)
8 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.343
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support: Yes
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021101121000408, 2021101121000301, 2021101821000164, 2022050521000401
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Wenzel univentionstaff 2022-06-21 11:05:27 CEST
+++ This bug was initially created as a clone of Bug #53907 +++

After switching from iTalc to Veyon, there is a delay in image transfer on a teacher PC in presentation mode.

This delay does not exist on client computers.
Comment 3 Tobias Wenzel univentionstaff 2024-04-30 12:28:47 CEST
When updating to a newer version, I received an error when I opened the computerroom module because Veyon is not running:

univention-app logs  ucsschool-veyon-proxy
#### 'docker logs 2a1fb35f0692b13f5c0f2a573d3dcccbd97cdf478113a95628af74deb5f76217' output:
QThread::start: Thread creation error (Operation not permitted)

This is connected to the version being too low:

docker -v
Docker version 18.09.7, build 2d0083d

It looks like the problems could also be fixed with the upcoming documentation for the Veyon Master.
Comment 4 Jürn Brodersen univentionstaff 2024-05-13 14:24:02 CEST
I did a quick check if a back port of the seccomp profile (/etc/docker/seccomp-systemd.json) from 5.0 would help. But it didn't work for me, seems to be more complicated.

-> wontfix