Package Details: gnome-network-displays 0.92.2-1

Git Clone URL: https://aur.archlinux.org/gnome-network-displays.git (read-only, click to copy)
Package Base: gnome-network-displays
Description: Miracast implementation for GNOME
Upstream URL: https://gitlab.gnome.org/GNOME/gnome-network-displays
Licenses: GPL-3.0-or-later
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 29
Popularity: 1.36
First Submitted: 2019-06-17 15:13 (UTC)
Last Updated: 2024-05-05 14:18 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

auditor_3d commented on 2022-08-11 14:37 (UTC)

it requires wpa_supplicant...which I don't use cause I use iwd....right? are all you all using wpa_supplicant still?

istobic commented on 2022-03-17 09:47 (UTC) (edited on 2022-03-17 09:47 (UTC) by istobic)

requires networkmanager, optionally dnsmasq

Thank you, @yochananmarqos!

istobic commented on 2022-03-16 11:21 (UTC) (edited on 2022-03-17 09:48 (UTC) by istobic)

Hi @yochananmarqos and thanks for maintaining the package. I see why you don't want to have dnsmasq as a (mandatory) dependency. I confirm that dnsmasq is a make dependency of libnm. This is why I would like to suggest adding dnsmasq as an optional dependency since some Miracast clients (e.g. my Samsung TV) do not work without dnsmasq. Also, dnsmasq is explicitly listed as a dependency in the documentation of gnome-network-displays. I'm sure this will help save people time.

TL;DR: Would be great if you could add optdepends=('dnsmasq: necessary for certain clients')

h4ckerle commented on 2022-03-15 17:07 (UTC)

Yes that worked. Thanks a lot!

yochananmarqos commented on 2022-03-15 14:14 (UTC) (edited on 2022-03-15 14:17 (UTC) by yochananmarqos)

@h4ckerle: That appears to be a Pipewire plugin.

gst-inspect-1.0 pipewiresrc

I've added gst-plugin-pipewire as an optional dependency for those using Pipewire.

h4ckerle commented on 2022-03-15 07:13 (UTC) (edited on 2022-03-15 07:13 (UTC) by h4ckerle)

pipewiresrc seems to be a dependency of this. https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/237#note_1408502

istobic commented on 2022-01-21 09:23 (UTC)

@yochananmarqos

This seems to be the misunderstanding. https://gitlab.gnome.org/GNOME/gnome-network-displays/-/blob/master/README.md#network-configuration-and-socket-connection states that dnsmasq is usually used.

In my case, dnsmasq was necessary to establish a connection to my Samsung J-Series TV. gnome-network-displays does not provide any error message when the connection fails because of missing dnsmasq. The only indication for that can be found in the log of networkmanager.

yochananmarqos commented on 2022-01-20 16:14 (UTC)

@istobic: dnsmasq is not mandatory for this package. I do not have it installed and it works fine.

istobic commented on 2022-01-20 16:02 (UTC) (edited on 2022-01-20 16:07 (UTC) by istobic)

Hi yochananmarqos and thank you for taking time to respond to my question. OK, an optional dependency means dnsmasq is not necessarily installed (like in my case) when installing networkmanager. But gnome-network-displays depends on both networkmanager and dnsmasq. Why exactly would one refrain from adding dnsmasq as dependency to this package despite the fact that dnsmasq is a mandatory dependency of gnome-network-displays?

yochananmarqos commented on 2022-01-20 15:37 (UTC)

@istobic: dnsmasq is an optional dependency of networkmanager, there's no need to add it as a dependency here.

« First ‹ Previous 1 2 3 4 Next › Last »