search

tidalcycles / pulsar-tidalcycles

Pulsar plugin for TidalCycles
https://web.pulsar-edit.dev/packages/tidalcycles
GNU General Public License v3.0
50 stars 28 forks source link

Failing to boot on Pop_OS #204

Open hobgoblina opened 1 year ago

hobgoblina commented 1 year ago

Tidal is working fine in other coding environments, but not with Pulsar. When using default paths, it isn't finding the BootTidal.hs nor ghci. Even when supplying paths for both, I'm still seeing t> /bin/sh: line 1: /usr/bin/ghci: No such file or directory.

ndr-brt commented 1 year ago

hi, thanks for reporting. according to the console output in your message, it seems like ghci is not placed where's expected to. What if you try to execute ghci in your terminal?

hobgoblina commented 1 year ago

ghci and ghc-pkg are both in $PATH and run fine in terminal. it def doesn't seem like an issue with the tidal install or its dependencies... it's all working without issue in other text editors, and I'm getting the same error output even when supplying the path to ghci (gathered via which ghci) in the pulsar package settings

ndr-brt commented 1 year ago

hey, do you have updates on this?

shiyouganai commented 11 months ago

Today, I encountered a duplicate of this issue on my Fedora Linux 39 machine. Like @necropolina, ghci and ghc-pkg were installed and in $PATH (they were in /usr/bin/). For me, the issue was because I had installed the flatpak package of pulsar from flathub, which due to a root cause I did not identify probably lacks the necessary flatpak sandbox permissions to see or execute those external executables.

When I uninstalled the flatpak and instead installed the rpm package provided here, I was able to successfully boot and use Tidal.

ndr-brt commented 11 months ago

Today, I encountered a duplicate of this issue on my Fedora Linux 39 machine. Like @necropolina, ghci and ghc-pkg were installed and in $PATH (they were in /usr/bin/). For me, the issue was because I had installed the flatpak package of pulsar from flathub, which due to a root cause I did not identify probably lacks the necessary flatpak sandbox permissions to see or execute those external executables.

When I uninstalled the flatpak and instead installed the rpm package provided here, I was able to successfully boot and use Tidal.

this could be something to report to the Pulsar community as well