<div dir="ltr"><div dir="ltr">On Sat, 2 Nov 2019 at 23:29, Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Same failures on the Debian 10 worker:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<a href="https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778" rel="noreferrer" target="_blank">https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778</a><br></blockquote><div><br></div><div><div dir="ltr"><div>runqemu - ERROR - Failed to run qemu: Xlib: extension "RANDR" missing on display ":1".<br>qemu-system-x86_64: ../libepoxy-1.5.3/src/dispatch_common.c:863: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.<br></div><div><br></div><div>Thanks - the Gtk part is passing fine, so it's something SDL does that upsets the X/GL stack on the Debian 10 host.</div><div>I am reluctant to disable the SDL part of the virgl tests on Debian 10, as it is a new distro (unlike centos 7).<br></div><div><br></div><div>I'll try to see if I can run Debian 10 in a VM here and try to reproduce. Or is it possible to debug directly on a Debian 10 worker?<br></div></div></div></div></div></blockquote><div><br></div><div>So I actually went ahead, and installed Debian 10 into a qemu image, then transferred a pre-populated build directory into it, and ran runqemu there against tigervnc (hurray for the nested kvm feature!). </div><div><br></div><div>Both 'runqemu kvm sdl gl' and 'runqemu kvm gtk gl' work fine, including running kmscube!<br></div><div><br></div><div>So I'd like to see what packages are installed on the Debian 10 worker vs. my Debian 10 installation. </div><div><br></div><div>Can you issue 'dpkg -l' on the worker, and send me the output, please? Maybe something is missing?</div></div></div></blockquote><div><br></div><div>After additional digging I reproduced this. The culprit is the outdated VNC server implementation that runs on the Debian 10 autobuilder (and maybe others as well). <br></div><div><br></div><div>Specifically, it's tightvncserver, where all Linux development has ceased 10 years ago (!).</div><div><a href="https://www.tightvnc.com/">https://www.tightvnc.com/</a></div><div><br></div><div>If you replace that with tigervnc (a modern, supported fork of tightvnc), then the tests pass fine.</div><div><a href="https://tigervnc.org/">https://tigervnc.org/</a></div><div><br></div><div>As Fedora has already obsoleted tightvnc in favor of tigervnc, I think we should do the same on all debian machines (debian provides both tightvnc and tigervnc, but treats them as equal).</div><div><a href="https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package">https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package</a></div><div>I also checked that tightvnc is not available for opensuse either.<br></div><div><br></div><div>Alex<br></div><div><br></div></div></div>