pulsar-tidalcycles icon indicating copy to clipboard operation
pulsar-tidalcycles copied to clipboard

Failing to boot on Pop_OS

Open hobgoblina opened this issue 2 years ago • 5 comments

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.

hobgoblina avatar Apr 17 '23 21:04 hobgoblina

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?

ndr-brt avatar Apr 18 '23 06:04 ndr-brt

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

hobgoblina avatar Apr 18 '23 15:04 hobgoblina

hey, do you have updates on this?

ndr-brt avatar Aug 23 '23 07:08 ndr-brt

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.

shiyouganai avatar Dec 01 '23 02:12 shiyouganai

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

ndr-brt avatar Dec 01 '23 08:12 ndr-brt