@@ -20,13 +20,11 @@ DEPENDS = " \
"
PORTAL_BACKENDS ?= " \
- ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'xdg-desktop-portal-wlr', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'gtk', 'xdg-desktop-portal-gnome', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'gtk+3', 'xdg-desktop-portal-gnome', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'gtk4', 'xdg-desktop-portal-gnome', '', d)} \
+ ${@bb.utils.contains('DISTRO_FEATURES', 'gtk+3', 'xdg-desktop-portal-gtk', '', d)} \
+ ${@bb.utils.contains('DISTRO_FEATURES', 'gtk4', 'xdg-desktop-portal-gtk', '', d)} \
"
-RDEPENDS:${PN} = "bubblewrap ${PORTAL_BACKENDS}"
+RDEPENDS:${PN} = "bubblewrap rtkit ${PORTAL_BACKENDS}"
inherit meson pkgconfig python3native features_check
According to the used desktop environment there are high level xdg-desktop-portal backends available. There are implementations for kde, lxde, gnome, wlroots. Even hyprland provides its own portal backend addition. These backends are known to cause unexpected behavior if mixed together, so it was a little bit overambitious to set the gnome portal as a runtime dependency by default as it may break other environments. Remove it from RDEPENDS Signed-off-by: Markus Volk <f_l_k@t-online.de> --- .../xdg-desktop-portal/xdg-desktop-portal_1.16.0.bb | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)