[–] 4 points 10 months ago (1 child)

For me the benefit was apps actually install and work now. In previous attempts to switch to Linux in years past, I would always go back to windows due to apps not working and dependency hell. With flatpak everything just works. I also appreciate the ability to manage permissions easily, and the application data is stored in one consistent location.

4GB per app sounds extreme though. That is not my experience at all.

  • source
  • [–] [S] 3 points 10 months ago (1 child)

    Huh, interesting, here's what the software install screen looks like in LMDE7... I have not installed any Flatpaks yet so that could be it? I'm not sure otherwise. I've run into several other large Flatpaks since, so maybe it's some bug idk.

  • source
  • parent
  • context
  • [–] [S] 3 points 10 months ago (4 children)

    Thank you, yeah I noticed some apps are only Flatpak which is why I asked, I understand dependencies but that seems like a lot of extra software to lean on for a screenshot tool, thought there might be more to it. I'll check out Flatseal if I need use them.

  • source
  • parent
  • context
  • [–] 14 points 10 months ago (5 children)

    Flatpak does deduplication, if two apps include the same dependencies then that's only stored once.
    What this means is that the more you lean into flatpaks, the smaller the individual app footprint on your drive becomes.

    The main benefit as an end user is gaining access to software that might've never ended up in the distro repository either way. And not having to worry about missing dependencies is a nice bonus.
    I recommend getting Flatseal to get a nice GUI for handling flatpak permissions.

  • source
  • [–] 6 points 10 months ago (1 child)

    Whoa! That's a gigantic Flatpak. I like FP because I can centrally managing app permissions with flatseal. I also like it when installing apps that have x86 libraries that I didn't want to install on my x64 only box. Not perfect, but it's nice also installing apps that only live in userspace and didn't touch my core os files. I like to to keep system and userspace separate. It's also nice to uninstall and remove everything associated. Pro-tip: try to only install flatpaks from original app devs if you can.

  • source
  • [–] 11 points 10 months ago (2 children)

    Have you ever tried to install a package and the install failed because of a missing dependency? You spend time chasing down that specific dependency, you find it and try to install it, but then the dependency itself fails to install because of a further missing dependency of its own. This is two steps into "dependency hell".

    This doesn't occur with a Flatpak install because all the dependencies are baked into the Flakpak.

  • source
  • [–] 11 points 10 months ago* (1 child)

    Primarily, it is to the app developer's advantage to use flatpak for distribution, as that lets you concentrate on getting one consistent version of your software out on an environment that is the same for everyone - the flatpak sandbox. If you use traditional methods, one of two things have to happen - you need to maintain multiple versions of your deb and/or rpm package, to cater to Ubuntu, Debian, Fedora, SuSE, and Enterprise Linux users. That didn't include Arch, Gentoo, Slackware, or from scratch source compilers. Which gets to part 2, hoping each community will make and keep up to date the source code builds themselves, because: Having source code and build environment settings for different distros to build from source and have it work in each distro, which may require or have available only certain versions of any libs you call on, that might not work with your code. This is "dependency hell", and it only gets worse the more linuxes you want to support directly.

    It's a lot easier to just ship the flatpak with the dependencies in them or linked in their flatpak libs as well. One set of dependencies and one build that runs on everything.

  • source
  • [–] 15 points 10 months ago* (1 child)

    Flatpaks ship all the dependencies of the application (i.e. the libraries that the program uses) in a single bundle, which usually accounts for much of the size.

    The upside to that is that flatpaked apps are universally compatible across distros; the downside is the file size.

    Another catch to flatpaks is that they run in a sandboxed environment, and each application has its own varying levels of isolation from your main system. This can lead to unintuitive issues like not being able to see files you save in a flatpaked browser unless you save to ~/Downloads. This sandboxing does have some security benefits, but is not generally considered robust protection from malware.

  • source
  • [–] [S] 3 points 1 year ago* (last edited 1 year ago)

    It turns out that this problem is more wide spread than I thought and is probably related to some hardware or to the distro itself/updates.

    I just discovered this happens in other apps and in steam gaming mode. So whatever is going on, I'm going to have to start over and eliminate stuff. Thanks for this answer though.

    Edit: I am going to assume (because it is working now, after removing every cable, swapping to a different port and eliminating a bunch of hardware from the setup before swapping everything back) that reseating something fixed this glitch. I don't know what it was that I reseated that fixed it, but it's all working as it should now, and it's setup exactly as it was when I started having issues.

    If anyone else comes here looking, that's the only solution I have at the moment.

  • source
  • parent
  • context
  • [–] 3 points 1 year ago (1 child)

    Use Toolbox or Distrobox as a simplified Podman (FOSS Docker without the daemon bs).

    You either install both Firefox and dependencies in the Distrobox container, or you install just the dependency you need and symlink, export, or alias it, (depending on how you want to access it by system, user session, or bash respectively).

    Be aware that by default these container distros in Toolbox/Distrobox are bare bones terminal like sandboxes. They do not have all of the GUI graphics stuff installed, so you may need to install a few extra bits for x11 or Wayland support and such.

    With both Distro/Toolbox, it defaults to a copy of your distro for the sandbox, but you can choose nearly any other distro too. Gentoo is one of the most advanced distros, and the Portage/emerge package manager enables source code compilation configurations unlike any other distro. That is always an option for really getting into the weeds. Much of Arch's binaries are actually built on Gentoo... And thus why Arch may already have exactly what you need if spun up in a distrobox container no matter what distro you are on.

    I strongly recommend creating an additional user on your system first and installing the sandbox with this unique user. Use the groups attribute to give access to your main user if you need it. Sandboxing in this context is only about dependency issues and not isolation or security as the ambiguous name implies. It will still make files and stuff all over the place. If a unique user session creates the stuff it becomes possible to find everything that users owns and therefore remove it at a later date.

  • source
  • [–] 1 point 1 year ago

    Mind if you elaborate?

    Also, this community might not be the best place for this post. Someone might need to make a proper Scratch community for this (although it might not get seen as much).

  • source
  • [–] 2 points 1 year ago

    NTFS doesn't like to not cleanly getting shit down. I remember I needed to boot windows again and then shutdown, in order to access my NTFS volume from Linux, because last time windows didnt shutdown cleanly. Glad you got it fixed

  • source
  • parent
  • context
  • [–] 3 points 1 year ago

    Not sure if cachy-os will auto mount. But after installing the ntfs-3g package, make sure you reboot.

    If it still doesn't work you can try to manually mount it or edit you're fstab so it it auto-mounted and assigned to the same device label.

  • source
  • parent
  • context
  • view more: ‹ prev next ›