While other flatpak apps have no problems. Any suggestions?

  • fenndev@leminal.spaceEnglish
    4·
    7 months ago

    Any issues lately with your network? When DNS is down or having issues, Firefox and forks take forever to start up.

    • SolarPunker@slrpnk.netOP
      1·
      7 months ago

      Nothing special, I don’t think that’s the problem since the lag is at every launch and it takes something like a minute to appear.

      • Bitrot@lemmy.sdf.orgEnglish
        5·
        7 months ago

        It also happens when the hosts file is messed up and the system can’t resolve its own hostnames. Opensuse used to be pretty notorious for doing something odd to the hosts file by default that really only affected Firefox.

        Edit: the increased security they’re trying around the browser might also be triggering that local resolution issue

      • gnuhaut@lemmy.ml
        11·
        7 months ago

        I don’t think that’s the problem

        Listen to the parent, this is almost certainly something to do with DNS (i.e. Firefox is not getting an answer for some reason, then timing out, then using maybe a backup DNS server; maybe there are multiple rounds of this). Who knows how your distro and that flatpak produce this interaction, but something is going on there.

  • Para_lyzed@lemmy.world
    4·
    7 months ago

    Is this new, or has it been happening for a few days/weeks? I’m on Fedora Atomic (which Bazzite is based on) and have never experienced this (though I mostly use Mullvad browser, a fork of Firefox). I tried Bazzite a few weeks ago and also never experienced this with the Firefox flatpak. If it’s been happening for awhile, it may be hardware-specific or a config thing. Out of curiosity (just to get a 1:1 comparison), do you experience the same thing with the Mullvad browser flatpak?

      • Para_lyzed@lemmy.world
        3·
        7 months ago

        Hm, it could be a new issue then. I’m not seeing it on the Bazzite issues page, perhaps you should open a new issue on it here, and provide your hardware specs. At the very least, you could see if this issue is reproducible on other installs, and someone there could help to obtain more useful debug info to determine the actual problem. You could also report it on the Mozilla Bugzilla page, as chances are this is a Firefox issue and not a Bazzite issue, but I admit that the interface for bug reports is less intuitive for non-developers there. Bazzite devs would likely direct you to there first anyway though.

        All I can really say myself is that I don’t experience this on Fedora Atomic KDE 40.20240607 with Mullvad Browser or the Firefox flatpak. I suspect it is either a hardware/config issue (on fresh install, I’d say a config issue is a distro issue if you haven’t changed anything), or that this is Bazzite specific and not present in upstream Fedora Atomic. Regardless, it’s a good idea to report this so that other users don’t experience the same bug

  • ColdWater@lemmy.ca
    3·
    7 months ago

    I have many flatpak apps bork down on me (steam, wine, emulators…) just install from your distro repo instead and only use flatpak if you don’t have other choices

  • GolfNovemberUniform@lemmy.ml
    2·
    7 months ago

    I noticed this too on my slowest machine. I guess you should just use native packages or other formats to fix it (as the other person said). I’d stick with Flatpak if possible though. It’s more secure

    • SolarPunker@slrpnk.netOP
      4·
      7 months ago

      Anything else works fine, the only other problem I’ve noticed is that some GTK applications don’t respect the KDE Plasma theme (in my case only Quod Libet).

      • khorovodoved@lemm.ee
        7·
        7 months ago

        Sorry for giving a rather useless advice. Of cause, you know about native packages, but since you are asking about flatpak, you, probably, have a reason to chose it. So, my original message was mostly intended as a joke, for which I am sorry.

        • Telorand@reddthat.com
          71·
          7 months ago

          Just curious why you think it’s dumb. I think it’s a great idea, since it gives more protection by containerizing the app.

          Like I told OP, I haven’t had any particularly long load times, but “long” is a subjective measure, after all.

          • boredsquirrel@slrpnk.net
            8·
            7 months ago

            It is a great idea but the concept is flawed

            This issue helps to understand it

            seccomp background

            libseccomp is a long established security “firewall for syscalls”, it allows to restrict what actions programs can perform on the system.

            I dont know what exactly these are, often low level stuff I guess, but one of these actions is “create an unprivileged user namespace”.

            Flatpak uses a single, “badness enumerating” seccomp filter, which means they block the syscalls “A”, “B” and “C” for all programs. All others are allowed, and (see the issue) programs cannot define a more restrictive one.

            user namespaces

            A namespace is a virtual filesystem on top of the “real” one, where certain real system files are mounted to. This means unprivileged programs can suddenly do “OS stuff”, needed to create this filesystem.

            contra user namespaces

            Many distros like Debian (and Arch) didnt enable this feature for a long time, because user namespaces mean that unprivileged userspace programs, like your browser, can suddenly access low level system components like the filesystem.

            If there now is a bug in such a component, user namespaces allow the program to directly access a way more privileged area, escape here and thus have privilege escalation.

            This would not be possible when not using user namespaces.

            Flatpak has a seccomp filter that blocks the creation of user namespaces, to avoid this low level system access. Which is a very good thing, but the missing modularity doesnt allow anything else!

            pro usernamespaces

            Over time even slow pacing distros like Debian enabled user namespaces.

            Today they are the core feature of bubblewrap, podman, docker, (and thus distrobox and toolbox)…

            The concept is that a rootless binary, running in userspace, can access system components which would normally require root.

            Firejail is the opposite example, it is a root binary and sandboxes apps also when user namespaces are disabled. Chromium has a fallback suid sandbox which also is a root, same with bubblewrap after the modification by 34N0 implemented in the “no userns” images of secureblue.

            The problem is, a root binary has root access. If there is a flaw in it, which was the case with firejail, the “nice and secure isolated app” could now use the root binary to escalate its privileges to root level, more than what it could have done without it.

            Browsers and Sandboxes

            A browser is basically a platform to run “apps” on. Nearly all websites nowadays require executable code, which means browsers are the attack surface for malware. Scrap your verified Flathub or well maintained distro repository, a single website could use a weakness and break your system.

            This was a thing back in the time… crazy huh?

            Chromium (Chrome, Edge, Brave, Vivaldi, Opera, …) has the said rootful sandbox as a fallback, I guess implemented back when user namespace sandboxes were not adopted enough.

            But is normally uses a user namespace sandbox for process isolation, every tab runs in a different process, on Android too.

            Firefox also uses user namespace sandboxes for tabs, but additionally uses seccomp-bpf to restrict the syscalls that the isolated tabs/processes can execute.

            Flatpak and Chromium

            Chromium relies exclusively on the ability to create sandboxes, with a root binary (the strange not really used fallback method) or with user namespaces.

            So much that it straight up doesnt run if it cannot do that. The same goes for Electron apps, which are a browser platform running a single or very few processes.

            This is why zypak was created. It redirects the calls of Chromium to flatpak, so it uses the builtin Flatpak sandbox instead.

            As I said, all Flatpak apps (and thus all processes) use the same seccomp filter, so I assume that zypak is less secure than the native sandbox, which is battle tested by Google, Microsoft and more companies.

            But it uses a sandbox, it is rootless and uses user namespaces. It just needs a little testing, a security audit, a bit of pentesting.

            At the current stage I would honestly not trust it, so Flatpak Chromium browsers are not recommended for “production”.

            Flatpak and Firefox

            The Firefox Flatpak is official.

            What the heck?

            Thats what I asked byself and created this issue but honestly, this issue thread is way more informative.

            Right now we just fork(), so replacing that with flatpak-spawn would cause a massive increase in memory usage? You would no longer have CoW sharing of memory.

            So Firefox would need big architectural changes to support a sandbox like Flatpak’s. It uses copy-on-write to save Memory and be more efficient.

            For some reason Chromium works just fine with zypak.

            it’s not clear to me the “Flatpak Sandbox” it’s creating is comparable to what we have now (even with just seccomp-bpf). We launch our subprocesses with specific, nailed down sandboxes.

            They should absolutely compare their seccomp filters. But this indicates the same issue as the one at the beginning, always using the same seccomp filter is not suited for an entire platform like a browser.

            Fair usage in Flatpak

            To sum it up:

            Electron apps are likely fine to be ran as Flatpaks. The zypak sandbox may not isolate the processes from another as well as the normal one does, but they are controlled and known code.

            Electron uses Chromium because of laziness, not because it needs the security of the platform. Daniel Micay, the creator of GrapheneOS, would also list a few very technical things why Electron has crippled security features of Chromium.

            Thunderbird is using Firefox similar to Electron, just as a platform for known code, so this will be fair too.

            Flatpak Firefox… is probably okay secure. If you use UBlock Origin with some filterlists, and an opt-in NoScript setup (which I highly recommend for privacy and security), the risk is even lower.

            But the risk is literally getting malware, losing all your data, getting breached or intruded. So why leave out this security measurement.

            But, its true, Flatpak isolates the browsers from the system, which is really nice. If there is a weakness in the browser platform, a process could not just escalate and access everything Firefox can.

            Bubblejail

            So isolating the browser from the system using Bubblewrap, a modern and rootless sandboxing tool, sounds like a good idea.

            The only issue is the always-the-same seccomp filter. The best solution would be a fix for the issue at the beginning, but for now we can use bubblejail.

            It is a tool that makes the creation of bubblewrap and seccomp filters easy, and adds Desktop entries to launch existing apps through that sandbox.

            For some reason it doesnt work at all anymore for me… but it did in the past. It is certainly not ready, but with some helping hands it can fix all the gaps, where system apps are needed for certain abilities.

            May that me a VPN app, Nextcloud-client adding icons to your task manager, an IDE like VSCodium, Zed, Lapce, Kate… or isolating all your system apps!

            So currently I use Fedora Firefox, which is very well maintained and checked for security build flags.

            I will continue making bubblejail work, which will be a good solution for this problem.

      • Telorand@reddthat.com
        4·
        7 months ago

        Probably best that you do the same (installing packages in the FS overlay kind of starts to defeat the point of containerization). You could try installing it with a distrobox and then exporting the app—see if that fixes your loading issues.

        I run Bazzite on a gaming laptop from 2015, and I haven’t noticed any particularly long load times. Do you have some browser extension(s) that are maybe causing issues?

        • SolarPunker@slrpnk.netOP
          4·
          7 months ago

          My only extension is uBlock Origin but it isn’t the problem (I uninstalled it to test and nothing changed). Thanks for your suggestion, I’ll try to play with distrobox (I’m new to Bazzite and immutable distros).

          • khorovodoved@lemm.ee
            3·
            7 months ago

            Distrobox will introduce a startup lag of it’s own. I would rather recommend (seriously this time) something like nix (it is officially supported for your distro) or junest.

            • Telorand@reddthat.com
              3·
              7 months ago

              Nix might have been removed. I’ll have to check, but I feel like the ujust command forv setting up nix went away a version or two ago.

              But I think you can set distroboxes to run at startup, so you’d never know the difference when it came time to actually launch the program. Right (correct me if I’m wrong)?

              • khorovodoved@lemm.ee
                3·
                7 months ago

                Maybe, I do not use bazzite and cannot check. But it used to be a feature. You can, of cause, start distrobox at startup, but literally running almost two operation systems might not be the best for performance and RAM usage.

                • Telorand@reddthat.com
                  2·
                  7 months ago

                  Could be a case for toolbox, which I admittedly know even less about. Either way, people here have offered several options to try!

                • SolarPunker@slrpnk.netOP
                  1·
                  7 months ago

                  Are there any processes in particular that I should keep an eye on? At the moment I don’t notice any new particularly high load.

            • SolarPunker@slrpnk.netOP
              1·
              7 months ago

              Oh thx for the info, I can maybe try with rpm-ostree in the case of lag. Nix is very good but I’m liking Bazzite very much for my needs, everything else seems working very good.

              • khorovodoved@lemm.ee
                1·
                7 months ago

                You don’t quite understand me, it seems. I do not mean nixos distro. Nix is already available inside Bazzite as an additional package manager.

              • khorovodoved@lemm.ee
                2·
                7 months ago

                The lag would be noticeable when you launch Firefox with stopped container (for example after reboot or manual stop).

                • SolarPunker@slrpnk.netOP
                  1·
                  7 months ago

                  Ok, I’ve tested this, I’ve noticed a lag of a couple of seconds for the first time I launched a distroboxed app.

            • Para_lyzed@lemmy.world
              1·
              7 months ago

              Is it? I was looking a few months ago at Nix support in Fedora Atomic (which Bazzite is based on), and it required some minor hacks to get the /nix folder and Nix itself working properly with rpm-ostree distros, as root is otherwise immutable. Plus, Nix isn’t available by default in the Fedora repos it seems. I believe it required something along the lines of making a /var/nix folder and symlinking it, but I believe you’d also have to work around SELinux contexts on the folder and symlink. I’ve heard of people even having issues after that, so I wouldn’t consider it “official” support. Here’s an open issue thread about it

              • khorovodoved@lemm.ee
                1·
                7 months ago

                Well, I know it used to be available and officially supported through available installation script. I do not have bazzite installed right now and their website does not have a proper documentation, so I can not check if it is available now.

          • Telorand@reddthat.com
            2·
            7 months ago

            You can try rpm-ostree to install in the lowest userspace layer, but Bazzite purposely switched to flatpak Firefox and discourages installing software using rpm-ostree, unless you absolutely have to.

            • SolarPunker@slrpnk.netOP
              1·
              7 months ago

              Oh I forgot about rpm-ostree ty! In this case of flatpak not working it is suggested rpm-ostree or distrobox?

      • edinbruh@feddit.it
        33·
        7 months ago

        IMHO I would avoid the ublue distros and just go for official fedora spins. The guys have good intentions, but they don’t have the means to maintain that many distros “properly”. I often end up enabling copr packages for bazzite in my fedora install, just to find out the program doesn’t work.

        That being said, as the other comments told you, you can still install native apps on immutable distros, it’s just a bit more work. I don’t expect distrobox or toolbox to be much faster than flatpak, as they are all just containers with a nice cli, except flatpak is easier to update. But trying costs nothing

  • Magister@lemmy.world
    57·
    7 months ago

    I’m so glad to use a distro with 0 flatpak/snap/whatever, my FF is always the latest one, with a simple .deb install from apt, ❤️ MX Linux