wayland | Core Wayland protocol and libraries | Video Utils library

I finally found! And it's the kmssink but I'll explain more why.

First I talked about the waylandsink. The thing is I did not know was wayland is a protocol and it seems to only work for displaying content inside a Desktop Environment (DE). So I guess you could create windows for each display and then link your sink to those windows. But I was looking for a way to display without any DE so waylandsink is a not an option.

For glimagesink from what I tried it's also in a DE so I did not explore more about it.

Then there's the framebuffer using the fbdevsink. It works without DE, but suffers from limitations... There seems to be only one framebuffer situated in /dev/fb0 and what we draw in it is displayed on every screen regardless of the display resolution. So if we have 2 displays with different resolution we cannot do fullscreen without having some cropping on one of them. Plus we cannot display different video on each screen because the framebuffer is duplicated. Finally while I was testing it, I found out some time there were frames that were drawn at the same time into the framebuffer, so it was causing the video to have some weird visual. Maybe the issues I listed could have been fixed in some way but there are just too many so I discarded this option

When I checked the documentation for the kmssink it says there are 2 main parameters I was interrested:

• bus-id
• connector-id

By specifying the bus-id I though I could display on a specific screen. But all the displays use the same bus-id: 0000:00:02.0 so it's not the parameter to specify a display.

Then there is connector-id. It's an integer and it can be used to specify the display. In my case it's 77 for HDMI-A-1 and 92 for HDMI-A-2.

How do you get the connector-id? Well that's not simple... A command exists to get them and it's called modetest. The thing is it seems to be only included in some embedded devices. I found out that the command was included in the package libdrm but in my case installing it did not give me access to the command... I'm using GStreamer with Rust so by importing the drm package I was able to get a list of connector-id and a lot of data about displays.

So in the end I can do:

Code works for me if I use upper case Z instead of Shift-z (with lower case z)

I got the same issue after upgrading to Ubuntu 21.10 (from 20.10).

Installing an older version of OpenCV worked for me.

Settings are external, project wide configuration, they cannot be defined or assigned values in conanfile.py files.

Settings are defined in your profile, like the "default", you can see it printed when you type conan install, something like:

The first thing you usually try in such a case is uninstall and reinstall the software...

I reverted back to Xorg from wayland and its working, no more warnings

Here are the steps:

1. Disbled Wayland by uncommenting WaylandEnable=false in the /etc/gdm3/custom.conf
2. Add QT_QPA_PLATFORM=xcb in /etc/environment
3. Check whether you are on Wayland or Xorg using:

This works both on Linux and Windows, from within PyCharm and from within a terminal. I am sure there is a lot of unused functionality in PyQt, like this. It hurts me to write code like this because I prefer them lean and simple. Suggestions to that end are welcome.

I missed a dependency, qt5-default. I ended up having these lines for Mayavi running on Docker/CircleCi:

I was able to work around the segmentation fault, by disabling the Vulkan support for AVDs. This can be easily achieved by adding the following line to the file ~/.android/advancedFeatures.ini: