I installed Sonic Pi 3.3.1 via the software installer with flatpak inside Linux Mint (Cinnamon) on two machines with versions 20.2 and 20.3. It seems to install nicely, I get the splash screen but then it complains about not seeing the server:
Critical error! - Could not boot Sonic Pi Server.
I have seen hints about killing and restarting pulseaudio but my system does not have a command cjack…
It wozld be great if the installer would test all the prerequisites systematically…
Thanks for your great work I hope to be able to enjoy soon
Just a heads up - boot up errors are better tracked on our GitHub issues page - easier to manage them there.
(Just to clarify though, we (the core team) don’t handle Linux builds (beyond a few experimental binary packages here and there AFAIK, but they’re not really ‘official’) - Linux builds are pretty much entirely managed by the community - there’s just too many Linux configurations to manage with the resources we have )
There are several tickets on GitHub about folks being unable to run the flatpak version already - though for other Linux distributions. It might be useful for you to open up a new ticket for your problem there, paste the full error report from Sonic Pi in, and page someone called @hfiguiere, who has been involved in the flatpak build of Sonic Pi
I just found this thread first when again looking at build info, and wondered a couple of things.
First, the most recent release of SP only seemed available via the sonic-pi.net homepage
Do the releases on github get updated once the release is a final release? (Eg when is 4.5 available via github releases)
Also, how is the winget package managed?
Is this a user/community thing, or can we push an update to that?
With linux builds, is it still community driven?
If so, is it simply a case of building then publishing somewhere, eg if we wanted to help with latest ap versions on Linux and others?
Finally, I wondered if github actions could be used to do the building ( or if that’s too expensive currently)
I build the binary release deb for SP after each tagging which is added to the github releases page. Basically I package the self contained code that you get after building Sonic Pi and running the script linux-release.sh in the build folder, so that it will install under /opt I add a desktop file, icons for that , a simple man file, and a startup script placed in /usr/bin Also a list of packages to be installed for runtime and the required DEBIAN folder. The result gives an installable deb file although it is not standard, as the program is not installed in the usual locations. Also there isn’t a correspending source deb file.
The Raspberry Pi is used because that’s where Sonic Pi started. You have the advantage of fixed hardware an OS. A “proper” deb was developed by Hanno Zulla for an early versioon, but he was not able to maintain it and although was developed up to version 3.2.2 that will not run properly on latest distributions as they move over to pipewire. I think this is maintained by the debian multimedia team.
There is however a flatpak install for 4.5 Sonic Pi | Flathub
I have just tried this on a virtual Ubuntu 23.10 running on my MacBookPro. Installed and ran without a hitch!
)
