xdg-desktop-portal-gtk VS flathub

I came across this, could this be playing a role? If it fixes Fedora 37 then it would be a clue and perhaps then the package could enter the string itself? https://github.com/flatpak/xdg-desktop-portal-gtk/issues/72

However, the actual dialogs and access points are provided by a backend, which differs from what desktop are you using. For example, Gnome uses xdg-desktop-portal-gtk, KDE uses xdg-desktop-portal-kde and so on.\ If there is an issue with the implementation of an portal, you need to find the backend you use and report it to them.

Is the Web search provider enabled in Settings? Those can apparently trigger background detection: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/293

That sounds like https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137

gui-libs/xdg-desktop-portal-lxqt Available versions: 0.2.0 Homepage: https://lxqt-project.org/ Description: Backend implementation for xdg-desktop-portal using Qt/KF5/libfm-qt gui-libs/xdg-desktop-portal-wlr Available versions: 0.4.0(0/9999) 0.5.0(0/9999) ~0.6.0(0/9999) **9999(0/9999)*l {elogind systemd} Homepage: https://github.com/emersion/xdg-desktop-portal-wlr Description: xdg-desktop-portal backend for wlroots [I] kde-plasma/xdg-desktop-portal-kde Available versions: (5) 5.24.6 ~5.25.4 {debug} Installed versions: 5.24.6(5)(01:02:06 07/29/22)(-debug) Homepage: https://kde.org/plasma-desktop Description: Backend implementation for xdg-desktop-portal that is using Qt/KDE Frameworks [I] sys-apps/xdg-desktop-portal Available versions: 1.14.6 {geolocation screencast systemd} Installed versions: 1.14.6(20:25:44 08/27/22)(-geolocation -screencast -systemd) Homepage: https://flatpak.org/ https://github.com/flatpak/xdg-desktop-portal Description: Desktop integration portal sys-apps/xdg-desktop-portal-gnome Available versions: 42.3 {X wayland} Homepage: https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome Description: Backend implementation for xdg-desktop-portal using GNOME sys-apps/xdg-desktop-portal-gtk Available versions: 1.8.0 1.14.0 {X wayland} Homepage: https://flatpak.org/ https://github.com/flatpak/xdg-desktop-portal-gtk Description: Backend implementation for xdg-desktop-portal using GTK+ Found 6 matches

you still xdg-desktop-portal-wlr in sway for screen sharing. the purpose of the gtk portal on non-gnome setups is to pass through some gtk settings (e.g. fontconfig, aliasing, gtk theme) to flatpak apps. your gtk flatpak apps won't follow the system theme and fontconfig unless you have the xdg-desktop-portal-gtk installed. right now it's borked though see below for more details - https://bugs.archlinux.org/task/72686?project=1&string=xdg-desktop-portal-gtk - https://github.com/flatpak/xdg-desktop-portal-gtk/issues/360

> Nobody ever even audits the binary contents of flatpaks on flathub (were they actually built from the source? the author attests so!).

IME/IIRC There aren't (or shouldn't be) any binary contents on Flathub that are submitted by the author, at least for projects with source available? You're supposed to submit a short, plain-text recipe instead, which then gets automatically built from source outside the control of the author.

> The Flathub service then uses the manifest from your repository to continuously build and distribute your application on every commit.

https://docs.flathub.org/docs/for-app-authors/submission/#ho...

Usually the recipes should just list the appropriate URLs to get the source code, or, for proprietary applications, the official .DEBs. Kinda like AUR, but JSON/YAML. Easy to audit if you want:

https://github.com/orgs/flathub/repositories

I also don't believe third parties maintainers packaging software on flathub is a big issue but I'm also not familiar with how other distro repos trust their maintainers. Hopefully more developers maintain their flatpak themselves (or someone they trust) and get their apps verified. If most apps are verified, warning users of unverified apps might be a good idea.

There's ongoing discussion about splitting open source and proprietary apps in to seperate repos [1]. Additionally having seperate repos for verified and unverified apps might make it more obvious where an app comes from in the cli.

But I don't know how seamlessly an app could transition between being in the third party repo and being in the official repo. Having the user quietly stop receiving updates seems like a bad idea, but automatically migrating might not be desirable either.

I also think flatpaks cli interface needs some work. It is functional but far from distro package managers.

Being verified is especially important for critical apps. Recently someone added malicious versions of apps to the snap store [3]. This lead to people getting their cryptocurrency stolen.

[1] https://github.com/flathub/flathub/issues/691

[2] https://docs.flathub.org/docs/for-app-authors/requirements

[3] https://forum.snapcraft.io/t/temporary-suspension-of-automat...

That means Linux users can now install Bforartists on any Linux distro easily, regardless of glibc version! https://github.com/flathub/flathub/pull/4295

Still having some problems with the flathub build, see https://github.com/flathub/flathub/pull/4082 for the current status.

Here is the flathub draft pull request: https://github.com/flathub/flathub/pull/4082

i assume you dont know how flathub works , theirs little or no QC , done flathub is just get told theirs an update for the package , if yo go look at the github repo pes https://github.com/flathub/flathub/pull/4164 for example , only updates the link to the girt repo , theirs 0 code checked

It all should be written in pages for contributors, read the docs for fusion, and the docs for flathub.

These are criticisms of the flatpak ecosystem as it stands today. Currently, the Firefox ESR package on flathub seems to be caught in limbo or maybe dead. Mozilla publishes both a snap and a flatpak of Firefox latest, but only a snap of the ESR version. This raises the question of why. Have Mozilla chosen to invest more in snaps than in flatpaks? If so, what's their reasoning? (More users on snaps, making it similar to why they put more investment into Windows than Linux? Something else?) If they haven't invested more into snaps than flatpaks, is this a sign that it's harder to maintain flatpaks (or at least on flathub) than snaps? If that's true, I would hope that flatpak/flathub would be soliciting feedback from Mozilla about it.

Because that may be very hard to sandbox: https://github.com/flathub/flathub/issues/3366