Originally created by @kytv on #10442 (Redmine)

An error dialog is displayed:

• title: “An error occurred”
• text: “The movie could not be read.”

Nothing obvious in the Journal (e.g. no AppArmor error) except that for each attempt, I see this: org.gnome.Shell.desktop[7280]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200013 ().

Running torsocks totem https://tails.boum.org/lib/test_suite/test.webm works fine in a local VM (2 vCPUs, 2GB RAM) running Tails 4.0~beta1 on my sid system:

• virtio GPU with 3d acceleration enabled
• virtio GPU without 3d accel
• same GPU as the one we use on Jenkins: type='qxl' ram='65536' vram='131072' vgamem='16384'

I can’t reproduce either when I run the test suite manually in a Stretch VM on my system; so nested virtualization is not the only explanation.

But I can reproduce this problem on my local Jenkins (worker1.ant01, nested virtualization), which shows that the problem is not specific to lizard.

wget https://tails.boum.org/lib/test_suite/test.webm works just fine when run by hand on worker1.ant01 and isotesterN.lizard. The former uses our VPN to connect to tails.b.o while the latter uses direct inter-lizard-VM IP connectivity to do so. Both resolve tails.b.o to a RFC1918 address.

Feature Branch: test/10442-totem-watching-webm-over-https

Parent Task: #10288

Related issues

• Related to #11403 (closed)
• Related to sysadmin#14588 (closed)
• Blocked by #9521 (closed)
• Blocked by #10497 (closed)
• Blocked by #10381 (closed)
• Blocked by #6729 (closed)