Flatpak integration is still not great

looks more like a KDE issue rather than a flatpak issue

I use flatpak and I actually like it. It is one of the ways I can get up to date packages on Debian.

I don't get it. Do you have two versions of Firefox installed?

What are you talking about ? isn't the firefox icon on the left a standard app from a distro repo instead of a flatpak like the one on the right ?

I use the Firefox flatpak on multiple different desktops and distros and I've never seen this issue. All on wayland (no difference on x11 either). Weird.

i have no issues with flatpak, once i found out how to fix gtk scaling and theming issues on kde. here's a link if anyone has those problems as well https://bugsfiles.kde.org/attachment.cgi?id=135846.

PEBKAC

I'm using KDE + Firefox Flatpak + Papirus Icons and I haven't had this issue (so far). Could it be an icon pack issue or something similar? Otherwise yeah it's either KDE or the flatpak

Is this really a flatpak issue? I've been dealing with this with Firefox periodically for many years, even before flatpak

I never intend to use a flatpak or snap, and avoid them like the plague. The whole concept is incredibly ugly to me, and wasteful of computer resources.

bwrap is so much better without Flatpak.

To start you off: $ bwrap --dev-bind / / --tmpfs ~ bash

This basically gives you a shell in a clean virtual home directory (but no meaningful security improvement yet). You can test new builds of software as if you have only the default settings. If you need to access files, move them to /tmp/.

To see the clean virtual home directory, replace --tmpfs ~ with --bind "$(mktemp -d)" ~. You can browse it where mktemp puts it (usually /tmp/*).

To start to lock down security, replace the --dev-bind with --ro-bind, and add various --new-session, --uid/--gid, and --unshare-all/--unshare-* flags. You can run untrusted and semi-trusted/less-trusted applications with less security risk this way (as long as you're aware of pitfalls, such as the /tmp/.X11-unix/X0 socket and other possible avenues of escape).

To block network access, use --unshare-net or --unshare-all. To virtualize /dev and /proc, use --dev /dev and --proc /proc.

Some programs might need --dev-bind /dev/dri /dev/dri for graphics driver access, or similar constructs.

EDIT: …I actually created a way to create completely portable application executables for Linux by using bwrap (or proot, as a fallback) to virtualize a Nix root from inside an AppImage, earlier this year. bwrap offers a lot of granularity in modifying and containing the virtual environment, to the degree that you can basically emulate an entire guest OS/distro on top of the host distro, without even needing root privileges— And without even needing bwrap itself to be installed, since it can work using entirely standard Linux kernel features.

Oh.. dude… Fanboys won’t like that…

the scuffed difference between my normal theming and flatpak theming is the only reason why I despise flatpak. I cannot for t he life of me get it to do what I want it to do. Flatpak containers are also kinda annoying to access

Why don't you use distro's package manager?

the only reason to use flatpaks is if your system doesnt come with a good package manager and repositories (pacman+aur, nix, etc), and dont want to build from source.

snaps, on the other hand, should be avoided at all costs imo.

Because it is FOSS. Money is always the issue.

Haven't had this issue on Gnome, might be a KDE specific issue. I really don't use KDE much except on my Steam Deck so I haven't encountered it very often.

The problem "without" flatpak is more than the problem "with" flatpak.

KDE issue, not Gnome issue

Just don't use flatpaks... it's a miserable experience all around
(and snaps are somehow even worse)

Flatpak ... is still not great

ftfy

Flatpak works great. I'm sorry you don't know how to use a computer.

Fedora has yet to make anything that works. That’s why.