after the latest release of gnome network displays version 0.95 I decided to give it a try by installing it in my system (ubuntu 25.04 development).
In order to install it locally I had to install first the following packages:
gettext
gir1.2-colord-1.0 (1.4.7-3)
libcolord-dev (1.4.7-3)
libcolord-gtk-headers (0.3.1-1build2)
libcolord-gtk4-dev (0.3.1-1build2)
libgraphene-1.0-dev (1.10.8-5)
libgtk-4-dev (4.18.2+ds-1)
gir1.2-xdp-1.0 (0.9.1-1)
gir1.2-xdpgtk4-1.0 (0.9.1-1)
libportal-dev (0.9.1-1)
libportal-gtk4-dev (0.9.1-1)
gir1.2-appstream-1.0 (1.0.4-1)
libadwaita-1-dev (1.7.0-1ubuntu1)
libappstream-dev (1.0.4-1)
dbus-x11 (1.16.2-2ubuntu1)
xdg-desktop-portal-dev
and then to proceed with the installation.
In order to invoke it I had to type the command:
/usr/local/bin/gnome-network-displays
Still I wasn’t able to connect with the television, yet I describe here the steps in case someone else tries the same thing and fails.
still, after the installation of the new version I didn’t notice any improvement with the connection of my laptop to a smart tv. At the time, a new version arrived (0.96) and still even this one didn’t work.
Trying to open the program from terminal and see any error messages, I was able to see the following:
(gnome-network-displays:2): Gnd-WARNING **: xx:xx:xx.xxx: codec list not initialized
WfdMediaFactory: Error creating video encoding pipeline.
gst_element_link_pads_full: assertion ‘GST_IS_ELEMENT (src)’ failed gnome network displays
gst_bin_add: assertion ‘GST_IS_ELEMENT (element)’ failed gnome network displays
The thing is that issuing the command: G_MESSAGES_DEBUG=all gnome-network-displays
I was able to see that codecs were initialized somehow, so this was a little bit contradictory.
In every attempt, I was able to see a split screen on the tv, yet on the side of the laptop a black screen appeared.
In order to solve the issue I installed the package: intel-media-va-driver-non-free
which installed also the package: intel-media-va-driver-non-free:i386
and removed the packages:
intel-media-va-driver
intel-media-va-driver:i386
I hope that someone might find it helpful and not lose much time figuring out what the solution will be.