I recently downloaded linux mint and I wanted use a live wallpaper so I found out I can do that with hidamari.

I’ve downloaded from the software package manager but it doesn’t launch when I click launch.

What am I doing wrong?

Anti Commercial-AI license (CC BY-NC-SA 4.0)

  • Eugenia@lemmy.mlEnglish
    61·
    5 months ago

    Do you mean a flatpak? Flatpaks are notorious for not integrating. Try to see if hidamari is available first as a .deb file in the official repos (uninstall the flatpak first). If that’s not it, then it seems that it doesn’t work with the Cinnamon desktop, which has control over the wallpaper functions.

    • Danterious@lemmy.dbzer0.comOP
      51·
      5 months ago

      I was able to solve the problem. Instead of downloading it from the Software Manager I installed it from the terminal instead.

      When I installed it from the software manager it didn’t download one of the packages (org.gnome.platform/44) but when I did it from the terminal it did.

      Thx though.

      Edit: Yeah it was a flatpak.

      Anti Commercial-AI license (CC BY-NC-SA 4.0)

    • gigachad@sh.itjust.works
      1·
      5 months ago

      Can you elaborate on that? I am a new Linux user and read a lot about flatpaks in the last week. My impression was, that while space demanding, flatpaks are super easy integrated and that’s why they are so succcessful?

      • Fisch@discuss.tchncs.deEnglish
        2·
        5 months ago

        It depends, since flatpaks are sandboxed, they don’t have access to anything by default. The developer can set defaults for what their app is allowed to access and the user can also manually change that. There’s also portals, so you can give them access for a file once (e.g. when opening in a file in an app) or allow them to see your screen and so on. There’s still a lot of things that don’t have portals tho, so flatpaks don’t have access to that.

      • Eugenia@lemmy.mlEnglish
        6·
        5 months ago

        It’s not false information. There are a lot of system-oriented things that don’t work through appimages or snaps or flatpaks, exactly because they’re sandboxed.

        • Fecundpossum@lemmy.worldEnglish
          6·
          5 months ago

          Love it when people speak with authority and are confidently incorrect. Eugenia is right.

          You could potentially use flatseal to grant the flatpak the necessary permissions, and you might find out what those permissions are by looking for other users experiences with the flatpak version.

          Or, you find the .deb file and it installs natively without being sandboxed. OR, you can find a PPA repository for it, load said repository and install your software.

          But those things require learning a little. Linux rewards self starters who can use a search engine and forums. Hope this maybe points you in the right direction.

        • boredsquirrel@slrpnk.net
          12·
          5 months ago

          Yes the wallpaper stuff could be problematic.

          But desktop integration works without issues. App stores also use flatpak install directly instead of packagekit, at least on cross-distro desktops like KDE and GNOME. Which works way better.

          Regarding “they dont work well for system related stuff”, on Unix stuff everything is a file, and especially dedicated apps like a wallpaper switcher can have very specific static filesystem permissions, allowing them to do exactly what they need.

          Appimages are totally different, a flawed concept by design and have no installer by default so they often have no integration at all. They are also not sandboxed at all and thus just as unrestricted as system apps, while they have no repo, no updating mechanism, no shared libs and are basically a security nightmare.

          I dont know about snaps. Their sandboxing needs Apparmor so it is not cross platform.