edit: It can’t send notifs :( https://lemmy.ml/comment/4138651

Is there a way to fix this? I am using an app called Superproductivity, it’s a productivity app where you can schedule tasks and keep track of them. Now, the trouble is, it won’t run in the background and it won’t send me notifications. This seems to be common for all Snaps I have installed, is there a way to solve this and make it notify me even when it’s not open?

Also, it also have an app image, do app images have the capacity to notify when they are not open? I have heard they can’t run in the background.

Thank you to everyone who try to help me here :)

  • Efwis@lemmy.zipEnglish
    1·
    9 months ago

    Unlike snaps and flatpaks, Appimages aren’t containerized or sandboxed at all. They are only used to bundle (some) dependencies, so you don’t need to rely on packages provided by your distro’s package manager.

    You might want to look up what Appimages are as well as what containerization is. To help I have found the following.

    AppImage aims to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, portability, distro agnosticism, no installation, no root permission, and keeping the underlying operating system untouched.

    Source: https://en.m.wikipedia.org/wiki/AppImage#:~:text=AppImage%20is%20a%20format%20for,developers%2C%20also%20called%20upstream%20packaging.

    As stated Appimages are containerized/sandboxed as it prevents needing to install any files on the OS.

    Containerized applications are applications run in isolated packages of code called containers. Containers include all the dependencies that an application might need to run on any host operating system, such as libraries, binaries, configuration files, and frameworks, into a single lightweight executable.

    Source: https://cloud.google.com/discover/what-are-containerized-applications

    As you can see, once again, your info is incorrect as this is another example of what Appimages are.

    • d_k_bo@feddit.de
      2·
      9 months ago

      Containerized applications are applications run in isolated packages of code

      My main point is that a running AppImage isn’t isolated, it can access and modify any file that the user has the permission to. So theoretically, an AppImage could read and upload your ssh keys or put rm -rf ~ in your .bashrc.

      A Flatpak app on the other hand needs to either declare specific permissions in its manifest if it wants to e.g. access your home directory or use xdg-desktop-portal to ask for a permission at runtime. This can help when running proprietary/untrusted software or if you want to control what a program can do and what not.

      A more popular example are Android apps which are executed in a strict sandbox and need to ask for permission if they want to read your images, access your microphone etc.

      See also https://en.wikipedia.org/wiki/Sandbox_(computer_security)

      Note that there were some discussions about adding sandboxing to AppImages: https://github.com/AppImage/AppImageKit/issues/152

      • Efwis@lemmy.zipEnglish
        1·
        9 months ago

        So do snaps and flatpacks. And they are still consider containerized / sandboxed. Appimages are the predecessors to snap and flatpack. The only difference is unlike Appimages they got it right for the most part.

        Generally speaking the Appimages integrate with KDE better than all the other DE’s. The codes for Appimages are still containerized from the OS in general as defined in my last post.