FS#79754 - [xdg-desktop-portal-gnome] Should depend on xdg-desktop-portal

Attached to Project: Arch Linux
Opened by Eric Long (hack3ric) - Friday, 22 September 2023, 11:48 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 26 September 2023, 20:41 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Recently after upgrading my system, GNOME's dark mode won't work. Installing xdg-desktop-portal solved the issue. Since I excluded anything that depends on flatpak (which is the only package that requires xdg-desktop-portal in gnome package group), I didn't have xdg-desktop-portal installed before, and it seemed dark mode worked well without it before until now.

It seems like not only xdg-desktop-portal-gnome depends on xdg-desktop-portal on Debian, but also -kde. Both of the relations are missing on Arch. Since I'm not a KDE user, I wonder if the latter is really needed. But still, GNOME needs xdg-desktop-portal to function properly now, if I wasn't wrong.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 26 September 2023, 20:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  xdg-desktop-portal-gnome 44.2-2
Comment by Toolybird (Toolybird) - Friday, 22 September 2023, 23:17 GMT
See also  FS#79759 . It seems the combo of libadwaita-1:1.4.0-1 and missing xdg-desktop-portal causes the dark mode breakage. Rolling back to libadwaita-1:1.3.5 *OR* installing xdg-desktop-portal makes it work again.

From the ArchWiki "Portals were designed for use with applications sandboxed through Flatpak, but any application can use portals to provide uniform access to features independent of desktops and toolkits."

My interpretation of those sentences is you shouldn't *have to* have xdg-portal-desktop installed for a functional desktop.

It's unclear to me how the dependency relationship should really work. There is definitely some inconsistency here, because the backends xdg-desktop-portal-{hyprland,lxqt,wlr,xapp} all depend on xdg-desktop-portal while the others don't. Deferring to PM's better judgment here.
Comment by Michel Koss (MichelKoss1) - Monday, 25 September 2023, 18:38 GMT
xdg-desktop-portal evolves beyond flatpak especially on Gnome.

The dependency chain should be like this:

Desktop Meta package (kde,gnome, etc) - > xdg-desktop-portal-{desktop-name} -> xdg-desktop-portal.

This is how other distros like fedora or debian have it.

Currently Arch has it backwards which leads users to broken setup like having xdg-desktop-portal-gnome without xdg-desktop-portal which doesn't make sense.

Loading...