Open Bug 1915472 Opened 1 year ago Updated 1 year ago

Flatpak lacks access to several dbus buses

Categories

(Release Engineering :: Release Automation, defect, P3)

Tracking

(Not tracked)

People

(Reporter: leftmostcat, Unassigned)

References

(Blocks 1 open bug)

Details

Several dbus buses are accessed in various parts of the code without corresponding access added in the flatpak build script. org.freedesktop.timedate1 is needed for https://bugzilla.mozilla.org/show_bug.cgi?id=1343826 to work within flatpak; org.freedesktop.login1, org.freedesktop.UPower, org.freedesktop.GeoClue2, org.freedesktop.portal.Desktop, and org.freedesktop.portal.Documents, org.gnome.SessionManager, org.freedesktop.PowerManagement, org.freedesktop.ScreenSaver, org.gnome.Mutter.IdleMonitor, and com.canonical.AppMenu.Registrar also appear to be accessed but not mentioned in the build script.

This list is not comprehensive and I have not tested any of the behaviors outside of those which rely on org.freedesktop.timedate1.

See Also: → 1915475
Severity: -- → S3
Priority: -- → P3

At least org.freedesktop.GeoClue2 is covered by org.freedesktop.portal.Location.

From https://flatpak.github.io/xdg-desktop-portal/
Flatpak grants sandboxed applications talk access to names in the org.freedesktop.portal.* prefix.
That covers the org.freedesktop.portal.Desktop and org.freedesktop.portal.Documents.

The org.gnome.SessionManager, org.freedesktop.PowerManagement and org.freedesktop.ScreenSaver should be covered by the org.freedesktop.portal.Desktop:
https://searchfox.org/mozilla-central/source/widget/gtk/WakeLockListener.cpp

Component: Release Automation: Packaging → Release Automation
You need to log in before you can comment on or make changes to this bug.