Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Its even worse when you force Firefox to use wayland its icon doesn't even show.
Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesn't use the pinned icon and doesn't even use the firefox icon under wayland at all.
looks more like a KDE issue rather than a flatpak issue
I use gnome and it works with custom Icons so 🫥
I use flatpak and I actually like it. It is one of the ways I can get up to date packages on Debian.
Man up and use unofficial repos that break your system like the rest of us
I don't get it. Do you have two versions of Firefox installed?
Don't know about the OP, but I only have one version installed. If I don't have it open, a single icon shows on the task bar. If I press that icon, FF opens and a second icon shows up, that represents only the opened FF, while the original icon remains.
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 ?
In that particular screenshot I believe you’re right: the one on the left is Firefox ESR while the icon on the right is whatever flatpak version available.
But I know what OP is referring to as it is a open bug currently, the DE don’t doesn’t recognize the launched instance as the pinned program due to the way Flatpak launched apps. Not an issue with Firefox in particular
I actually took the screenshot myself and yes it is a bug* specifically with Flatpak.
Man, everything works great on my PopOS AMD rig with Wayland.
This bug only exists in KDE, based on my experience
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 run flatpak firefox and kde wayland and have no such issue
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.
The whole concept is incredibly ugly
Depends on the viewpoint. As a software consumer, sure. As a software producer though, not having to deal with with tons of different packaging formats and repositories for different distributions and versions is a blessing.
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…