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.
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 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
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
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.
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.
Tied to proprieatry backend, snap store looks like ass and runs like one, spawns loop devices that mess up the /mnt folder, tied to fake .deb packages that install snaps instead. Basically, a lot of proprieatry nonsense that St. Ignucius frowns upon.
Very simple. Debian Testing is rolling distro and has fairly fresh versions, usually couple of months behind. Debian Unstable has all the bleeding edge stuff, also rolling. Neither is unstable and insecure as most would expect. If you want non-Debian, there’s always Arch and Manjaro.
Why would you need another package manager next to the one supplied with the distro? The one that is supplied has packages that are tested and guaranteed to work (when on a stable release).
Yes, they are (sometimes very) outdated, but those packages are working. Additional package managers just add to the dependency hell (introducing bugs).
It’s kinda one size fits all solution. It allows Devs to build their package one way and have it on pretty much every distro, which is a major sticking point for Linux apps. I don’t see why you would use a flatpaks if your distro has the software already though. I use flatpaks alot less now that I’ve moved to endeavour from fedora. The AUR is a godsend.
Also flatpak doesn’t add to dependency hell, the dependencies it installs are also flatpaks and are completely separate from the system. Recently the arch package of steam simply stopped launching proton games for some reason, I thought I messed something up on my system so I rolled to an old btrfs snapshot and it still didn’t work. However the flatpak version of steam just works.
Do you realize why is that? That Dev will build the package once lifetime and dont give a shit about proper testing nor updating libraries. And your home dir is probably exposed to this buggy craphole.
openqa.opensuse.orgThis is what an update goes through when a proper QA process is applied in a standard distro packaging system. This is what flatpak does not ever comes close to. Flatpak is just windows approach ported to linux. Quality and trust comes from package to package and can vary from good to dogwater.
Btw not sure you realize you are complaining about broken package on bleeding edge distro.
Lmao, why are you so agressive? It’s a packaging format not bloody politics. I never complained about anything, I stated that one package format was broken and the flatpak wasn’t. The mere existence of flatpaks does not and will never threaten the traditional packaging method, or it’s QA. Flatpaks merely provide smaller developers an easy way to get their application published, as well as end users a stress free way to install said apps. And yes, they can range from good to dogshit, that comes with the territory of leaving it entirely up to the publishers, but I think Linux users are capable of identifying which flatpaks are dogshit and which aren’t. Also what do you mean my home dir is probably exposed? Like it isn’t exposed when I install a regular package? Remember the steam bug that just completely wiped your install because they made an assumption with a single variable? Buggy software will always exist, at least with flatpak you can limit an apps access to your system
Please stop projecting on others, that would be nice.
Yes, your home is exposed on both sides. One side tested in proper QA, the other in “trust me bro” env. Lol…. one moment you say that bugs happen and right after that you generalize everything based on one shit that happened on steam package. First you say you are not complaining about anything but then you go to “flatpak better!!!”. Fisrt you say flatpak security is good and when you should back your claims you go with “Linux users detect bugs and security holes very good. Of course they do… after the system goes tits up :D
So… either please stop talking nonsense or present some facts that try to back that nonsense at least.
Flatpak is a last resort. Only used when the package is not available on the repository or the version is too out of sync with the environment. If I really really need to run the latest version of that software, it’s easy to run a Flatpak. But that is only and exclusively for final user software, never for services or background running application, or a new can of worms is opened.
Add comment