Linux Version

[Hung027558]

I installed Sonic Pi through apt, and when I ran it, this happend:
Sonic Pi Boot Error Report

System Information

• Sonic Pi version: 3.2.2
• OS: Debian GNU/Linux 12 (bookworm)

GUI Log

/home/d/.sonic-pi/log/gui.log

[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {439c420c-2a2f-45eb-9836-03f69df8135c}
[GUI] - Discovering port numbers...
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry osc-midi-out : 51238 : 51238
[GUI] - Port entry osc-midi-in : 51239 : 51239
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51240 : 51240
[GUI] - Port entry websocket : 51241 : 51241
[GUI] - Detecting port numbers...
[GUI] - GUI listen to server port 51236
[GUI] -    port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] -    port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] -    port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Erlang router port 51240
[GUI] -    port: 51240 [OK]
[GUI] - OSC MIDI out port 51238
[GUI] -    port: 51238 [OK]
[GUI] - OSC MIDI in port 51239
[GUI] -    port: 51239 [OK]
[GUI] - Websocket port 51241
[GUI] -    port: 51241 [OK]
[GUI] - All ports OK
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - Ruby server pid registered: 9559
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states 
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
[GUI] - starting UDP OSC Server on port 51236...
[GUI] - UDP OSC Server ready and listening
...............................
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
 ["/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:267:in `boot_and_wait'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:443:in `boot_server_linux'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:151:in `boot'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `new'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `init_scsynth'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:57:in `initialize'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `new'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `block (2 levels) in included'", "/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in `block (2 levels) in included'", "/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `new'", "/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
.............................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..

Server Errors

/home/d/.sonic-pi/log/server-errors.log

Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot use real-time scheduling (RR/10) (1: Operation not permitted)
AcquireSelfRealTime error
Cannot use real-time scheduling (RR/5) (1: Operation not permitted)
JackClient::AcquireSelfRealTime error
jack_port_get_buffer called with an incorrect port 0
jack_port_get_buffer called with an incorrect port 0
jack_port_get_buffer called with an incorrect port 0
jack_port_get_buffer called with an incorrect port 0
jack_port_get_buffer called with an incorrect port 0
JackEngine::XRun: client = SuperCollider was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 18 err = Connection reset by peer
Could not read notification result
ClientNotify fails name = SuperCollider notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 18 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = SuperCollider notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 18 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = SuperCollider notification = 4 val1 = 0 val2 = 0
Cannot write socket fd = 18 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = SuperCollider notification = 3 val1 = 0 val2 = 0
Unknown error...
terminate called after throwing an instance of 'Jack::JackTemporaryException'
  what():  

Server Output

/home/d/.sonic-pi/log/server-output.log

Sonic Pi server booting...
This is version 3.2.0 running on Ruby 3.1.2.
The time is 2025-09-05 18:46:57 +0700
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
  - OK
Scsynth port: 51237
  - OK
Scsynth send port: 51237
  - OK
OSC cues port: 4560
  - OK
Erlang port: 51240
  - OK
OSC MIDI out port: 51238
  - OK
OSC MIDI in port: 51239
  - OK
Websocket port: 51241
  - OK
Opening UDP Server to listen to GUI on port: 51235
Starting Server Runtime
Booting server...


Booting Sonic Pi
----------------

Booting on Linux
Jackd not running on system. Starting...
jackdmp 1.9.21
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2022 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|2048|3|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 2048 frames (46.4 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback
Started [9572] [-] jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100 [-] /tmp/sonic-pi-pids/9572
Boot - Starting the SuperCollider server...
Boot - scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1
Started [9585] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/9585
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Unable to connect to SuperCollider
Failed to start server: Boot - Unable to connect to SuperCollider
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:267:in `boot_and_wait'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:443:in `boot_server_linux'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:151:in `boot'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `init_scsynth'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:57:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `block (2 levels) in included'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in `block (2 levels) in included'
/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `new'
/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `<main>'

Scsynth Output

/home/d/.sonic-pi/log/scsynth.log

# Starting SuperCollider 2025-09-05 18:46:57
Found 0 LADSPA plugins
JackDriver: client name is 'SuperCollider'
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 2048
SuperCollider 3 server ready.

Process Log

/home/d/.sonic-pi/log/processes.log

Clearing pids: ["9383", "9399", "9409"]

Clearing [9383]
  -- command /usr/bin/ruby -E utf-8 /usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241
  -- removing /tmp/sonic-pi-pids/9383
  -- unable to get ProcTable info for: 9383
  -- process: 9383 not running

Clearing [9399]
  -- command jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100
  -- removing /tmp/sonic-pi-pids/9399
  -- unable to get ProcTable info for: 9399
  -- process: 9399 not running

Clearing [9409]
  -- command scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1
  -- removing /tmp/sonic-pi-pids/9409
  -- unable to get ProcTable info for: 9409
  -- process: 9409 not running

Finished clearing pids

Started [9559] [-] /usr/bin/ruby -E utf-8 /usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241 [-] /tmp/sonic-pi-pids/9559
Started [9572] [-] jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100 [-] /tmp/sonic-pi-pids/9572
Started [9585] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/9585

[rbnpi]

3.2.2 is an old version produced by a third party. Info you are using Raspberry Pi which appears to be the case please try the deb file available on
https:/sonic-pi.net/#rp

[Hung027558]

I'm using Debian in an x64 system and can't use your AMD64 version, so I downloaded the x64 version from apt.

[Hung027558]

• not a Raspberry Pi but still want to run in Linux Debian

[rbnpi]

Ok. Would you consider building from source. It is not too difficult. I have built on arm based Debian on a virtual machine but I don’t currently have a machine to build amx based.  The Linux build are pretty good.

[Hung027558]

your official package's not working:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'sonic-pi:arm64' instead of '/media/d/a3bffd91-f3c7-4d83-ab8c-e1755c5c8281/home/d/Downloads/sonic-pi_4.6.0_1_bookworm.arm64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
sonic-pi:arm64 : Depends: libqt6core6:arm64 but it is not installable
Depends: libqt6dbus6:arm64 but it is not installable
Depends: libqt6gui6:arm64 but it is not installable
Depends: libqt6network6:arm64 but it is not installable
Depends: libqt6opengl6:arm64 but it is not installable
Depends: libqt6openglwidgets6:arm64 but it is not installable
Depends: libqt6qml6:arm64 but it is not installable
Depends: libqt6qmlmodels6:arm64 but it is not installable
Depends: libqt6quick6:arm64 but it is not installable
Depends: libqt6waylandclient6:arm64 but it is not installable
Depends: libqt6waylandcompositor6:arm64 but it is not installable
Depends: libqt6waylandeglclienthwintegration6:arm64 but it is not installable
Depends: libqt6waylandeglcompositorhwintegration6:arm64 but it is not installable
Depends: libqt6widgets6:arm64 but it is not installable
Depends: libqt6wlshellintegration6:arm64 but it is not installable
Depends: libqt6xml6:arm64 but it is not installable
Depends: qt6-qpa-plugins:arm64 but it is not installable
Depends: qt6-translations-l10n:arm64 but it is not installable
Depends: qt6-wayland:arm64 but it is not installable
Depends: qt6-gtk-platformtheme:arm64 but it is not installable
Depends: ruby:arm64 but it is not installable
Depends: supercollider-server:arm64 but it is not installable
Depends: sc3-plugins-server:arm64 but it is not installable
Depends: libspa-0.2-jack:arm64 but it is not installable
Depends: pipewire-jack:arm64 but it is not installable
Depends: libkissfft-float131:arm64 but it is not installable
E: Unable to correct problems, you have held broken packages.

[rbnpi]

What were you installing this on? It is only designed to work on raspberry pi OS (debian bookworm base)

I managed to build (very slowly! an emulated amd64 bit debian 12 virtual machine today and to build sonic pi on it.
The whole procedure is quite straightforward and you may like to try this on your debian linux distro
first install these packages in a terminal window

sudo apt-get install -y build-essential git libssl-dev ruby-dev elixir erlang-dev erlang-xmerl qt6-tools-dev qt6-tools-dev-tools libqt6svg6-dev libqt6opengl6-dev supercollider-server sc3-plugins-server alsa-utils  libasound2-dev cmake ninja-build pipewire-jack libspa-0.2-jack qt6-wayland libwayland-dev libxkbcommon-dev libegl1-mesa-dev libx11-dev libxft-dev libxext-dev qpwgraph compton m4 libaubio-dev libpng-dev libboost-all-dev librtmidi-dev

secondly download the sonic pi source to a suitable location. (I created a folder dev in my home folder) and run the build script

mkdir dev
cd dev
git clone https://github.com/sonic-pi-net/sonic-pi

cd sonic-pi/app
./linux-build-all.sh

This will take some time to build, and there are one or two long pauses where files build with no apparent activity.
However it should complete OK. Once finished you can try it out by typing

../bin/sonic-bin

Note you can also get a leaner relocatable folder containing sonic pi by running the script

linux-release.sh

This generates the release in the sonic-pi/app/build/linux_dist folder which you can relocate and rename to a more convenient location

[Hung027558]

Sonic Pi Boot Error Report

System Information

• Sonic Pi version: 3.2.2
• OS: Debian GNU/Linux 12 (bookworm)

GUI Log

/home/d/.sonic-pi/log/gui.log

[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {42e18d58-b417-416c-8a2c-724940edb528}
[GUI] - Discovering port numbers...
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry osc-midi-out : 51238 : 51238
[GUI] - Port entry osc-midi-in : 51239 : 51239
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51240 : 51240
[GUI] - Port entry websocket : 51241 : 51241
[GUI] - Detecting port numbers...
[GUI] - GUI listen to server port 51236
[GUI] -    port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] -    port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] -    port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] -    port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] -    port: 51237 [OK]
[GUI] - Erlang router port 51240
[GUI] -    port: 51240 [OK]
[GUI] - OSC MIDI out port 51238
[GUI] -    port: 51238 [OK]
[GUI] - OSC MIDI in port 51239
[GUI] -    port: 51239 [OK]
[GUI] - Websocket port 51241
[GUI] -    port: 51241 [OK]
[GUI] - All ports OK
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - Ruby server pid registered: 37579
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states 
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
51236...
[GUI] - UDP OSC Server ready and listening
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..
[GUI] - UDP OSC Server no longer listening

Server Errors

/home/d/.sonic-pi/log/server-errors.log

ATTENTION: The playback device "hw:0" is already in use. The following applications  are using your soundcard(s) so you should  check them and stop them as necessary before  trying to start JACK again:

pulseaudio (process ID 1095)

cannot load driver module alsa
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)


ATTENTION: The playback device "hw:0" is already in use. The following applications  are using your soundcard(s) so you should  check them and stop them as necessary before  trying to start JACK again:

pulseaudio (process ID 1095)

cannot load driver module alsa
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
terminate called without an active exception

Server Output

/home/d/.sonic-pi/log/server-output.log

Sonic Pi server booting...
This is version 3.2.0 running on Ruby 3.1.2.
The time is 2025-09-07 09:42:37 +0700
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
  - OK
Scsynth port: 51237
  - OK
Scsynth send port: 51237
  - OK
OSC cues port: 4560
  - OK
Erlang port: 51240
  - OK
OSC MIDI out port: 51238
  - OK
OSC MIDI in port: 51239
  - OK
Websocket port: 51241
  - OK
Opening UDP Server to listen to GUI on port: 51235
Starting Server Runtime
Booting server...


Booting Sonic Pi
----------------

Booting on Linux
Jackd not running on system. Starting...
jackd 0.126.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|2048|3|44100|0|0|nomon|swmeter|-|32bit
Started [37592] [-] jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100 [-] /tmp/sonic-pi-pids/37592
Boot - Starting the SuperCollider server...
Boot - scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1
Started [37602] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/37602
Failed to start server: SIGTERM
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/util.rb:599:in `wait'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/util.rb:599:in `kill_and_deregister_process'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:224:in `rescue in boot_and_wait'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:221:in `boot_and_wait'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:443:in `boot_server_linux'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:151:in `boot'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/scsynthexternal.rb:37:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/server.rb:78:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:192:in `init_scsynth'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/studio.rb:57:in `initialize'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `new'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/sound.rb:89:in `block (2 levels) in included'
/usr/lib/sonic-pi/app/server/ruby/lib/sonicpi/lang/ixi.rb:72:in `block (2 levels) in included'
/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `new'
/usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb:302:in `<main>'

Scsynth Output

/home/d/.sonic-pi/log/scsynth.log

# Starting SuperCollider 2025-09-07 09:42:37
Found 0 LADSPA plugins
jackd 0.126.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
could not initialize audio.

Process Log

/home/d/.sonic-pi/log/processes.log

No pids store found here: /tmp/sonic-pi-pids
Exiting
Creating pids store: /tmp/sonic-pi-pids
Started [37579] [-] /usr/bin/ruby -E utf-8 /usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241 [-] /tmp/sonic-pi-pids/37579
Started [37592] [-] jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100 [-] /tmp/sonic-pi-pids/37592
Started [37602] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/37602


Clearing pids: ["37592", "37579", "37602"]

Clearing [37592]
  -- command jackd -R -T -p 32 -d alsa -n 3 -p 2048 -r 44100
  -- removing /tmp/sonic-pi-pids/37592

Clearing [37579]
  -- command /usr/bin/ruby -E utf-8 /usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241
  -- removing /tmp/sonic-pi-pids/37579
  -- politely killing 37579

This is my builded Sonic Pi, I followed every step of your instructions when building this.
My specific distro is BinsenLabs Boron, which is based on Bookworm.

[ethancrawford]

@Hung027558 - The information at the top of that error report says it was trying to run v3.2.2... were you trying to build that same version? If so, what Robin was getting at when talking about building from source is that you will want to build a more recent version than 3.2.2, as that one does not work nowadays.
The most recent stable release is v4.6.0 - that should be ok for you hopefully.

[idommason]

Hi

I would suggest you have a read through this, which is about building sonic-pi v4.60 on a Debian Bookworm based distro

This thread

#3460

This is for a step I missed, and had to go back to later, so do this before you do all the build steps

#3460 (comment)

Then do the apt-get installs from this post, and follow the rest of it

#3460 (comment)

@samaaron

I'm not sure how you would go about this, but I notice that even the latest Mint version 22.1 (xia) has sonic-pi 3.2.2 as the packaged version, and that is never going to work on a new install of Linux Mint, or Ubuntu - where it is also the packaged version on Ubuntu 24.04

So I am wondering if you could talk to the Debian / Ubuntu packagers and get them to remove that version?