path does not exist error

[fenbyte]

Describe the bug

trying to install a flatpak with bazaar results in a "path does not exist" error after the download finishes

OS

void linux aarch64, kde plasma 6.6.2, linux 6.18.9+1-asahi_1, flatpak 1.16.3

Version

Bazaar - Discover and install applications

          ID: io.github.kolunmi.Bazaar
         Ref: app/io.github.kolunmi.Bazaar/aarch64/stable
        Arch: aarch64
      Branch: stable
     Version: 0.7.11
     License: GPL-3.0-or-later
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 17.3 MB
     Runtime: org.gnome.Platform/aarch64/49
         Sdk: org.gnome.Sdk/aarch64/49

      Commit: a32efdb3cb90a3f3ec8b02a59b4f58d602c72b41232903ec261da56fe8a8c8a5
      Parent: 6fec4e8160596b1103017e730254c538b9ca3b37563f2c239443b8d0eab387aa
     Subject: Merge pull request #106 from kolunmi/0.7.12 (2069ab570b29)
        Date: 2026-03-07 23:46:19 +0000

Configured Flatpak Remotes

Name           Options
flathub        system
flathub        user
flathub-beta   user
signal-flatpak user

Hardware

CPU: Apple M2
GPU: Apple M2
RAM: 16GB

Extra information or context

No response

[fenbyte]

i tested this on an x86_64 machine and it happens there too. after more research this seems to be because of the lack of systemd... lots of distros use alternative init systems and flatpak itself does not depend on systemd, can this be addressed somehow?

[fenbyte]

after doing more research and talking to some people it seems that bazaar checks for /run/systemd to determine if it's running on a systemd system, but this isn't correct because elogind also creates that directory even on non-systemd distros.