Sonic-pi: Unable to start on Manjaro Linux

Created on 15 Apr 2020 · 9Comments · Source: sonic-pi-net/sonic-pi

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 3.2.2
OS: Manjaro Linux

GUI Log

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

[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -                            
[GUI] - {49ccc59d-1632-4d5c-bee1-05c01d3fb402}
[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: 19052
[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] - 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/ccpplinux/.sonic-pi/log/server-errors.log

JACK is running in realtime mode, but you are not allowed to use realtime scheduling.
Please check your /etc/security/limits.conf for the following line
and correct/add it if necessary:

  @audio          -       rtprio          99

After applying these changes, please re-login in order for them to take effect.

You don't appear to have a sane system configuration. It is very likely that you
encounter xruns. Please apply all the above mentioned changes and start jack again!
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)

JACK is running in realtime mode, but you are not allowed to use realtime scheduling.
Please check your /etc/security/limits.conf for the following line
and correct/add it if necessary:

  @audio          -       rtprio          99

After applying these changes, please re-login in order for them to take effect.

You don't appear to have a sane system configuration. It is very likely that you
encounter xruns. Please apply all the above mentioned changes and start jack again!
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/ccpplinux/.sonic-pi/log/server-output.log

Sonic Pi server booting...
This is version 3.2.0 running on Ruby 2.7.1.
The time is 2020-04-15 16:40:24 +0530
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.125.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

Started [19065] [-] jackd [-] /tmp/sonic-pi-pids/19065
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 [19068] [-] 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/19068

Scsynth Output

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

# Starting SuperCollider 2020-04-15 16:40:27
Found 12 LADSPA plugins
jackd 0.125.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

could not initialize audio.

Process Log

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

Clearing pids: []
No pids to clear :-)
Started [19052] [-] /usr/bin/ruby --enable-frozen-string-literal -E utf-8 /usr/bin/../../usr/lib/sonic-pi/server/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51240 51238 51239 51241 [-] /tmp/sonic-pi-pids/19052
Started [19065] [-] jackd [-] /tmp/sonic-pi-pids/19065
Started [19068] [-] 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/19068

Linux boot jack

Source

ccpplinux

Most helpful comment

@ccpplinux

I had the same issue on Manjaro, and I solved it following these steps

Add your user to audio group
sudo usermod -a -G audio your_username

Create the file or add to /etc/security/limits.d/audio.conf these lines:

@audio - rtprio 99
@audio - memlock unlimited

In my case, I had to install libffado and libcelt with:

pacman -S libffado celt

You also have to install qjackctl

pacman -S qjackctl

Reboot your system, and then open qjackctl and start it. Now, open sonic-pi

urkh on 13 May 2020

👍3 😕1

All 9 comments

I also have the same error.

RobertS6A on 12 May 2020

@ccpplinux

I had the same issue on Manjaro, and I solved it following these steps

Add your user to audio group
sudo usermod -a -G audio your_username

Create the file or add to /etc/security/limits.d/audio.conf these lines:

@audio - rtprio 99
@audio - memlock unlimited

In my case, I had to install libffado and libcelt with:

pacman -S libffado celt

You also have to install qjackctl

pacman -S qjackctl

Reboot your system, and then open qjackctl and start it. Now, open sonic-pi

urkh on 13 May 2020

👍3 😕1

@urkh it helped thanks. Could you please add details on what is causing the error? can this be fixed in the installation itself? I would be willing to contribute if I you could guide me.

vumaasha on 24 Oct 2020

This is a known JACK specific error. Read more https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#Installation

MyIsaak on 7 Nov 2020

@ccpplinux

solved it following these steps

does not work for me. Only way to get the application started is if i first execute:

jackd -R -d alsa -d hw:0,3
But then i have no audio output from sonic-pi

Ryder17z on 1 Dec 2020

Okay just able to make it work....

Open QjackCtl ---> settings --->Advanced
check No memory lock
check your output device and input device are there....

this is after following @urkh

arunkhattri on 7 Dec 2020

I have a similar issue tested on 1) Ubuntu 20.10 with sonic-pi version 2.10 and on 2) Debian unstable with sonic-pi version 3.2.
In both cases I downloaded sonic-pi binaries from the repositories using apt.

Wehzie on 13 Dec 2020

Open QjackCtl ---> settings --->Advanced
check No memory lock
check your output device and input device are there....

What does this option do?
Even with that enabled, i still have issues.

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

ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
no message buffer overruns
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
no message buffer overruns

Ryder17z on 13 Dec 2020

@Wehzie - just want to clarify if you don't already know, that versions of Sonic Pi available in the official repositories of various Linux distributions are entirely community maintained, (since we don't have the resources to manage this ourselves) and as such are often old versions. As such, up-to-date Sonic Pi on Linux is mostly a compile-it-yourself affair - I'd definitely encourage you to have a go at that to get the most recent updates.
It may still encounter issues starting up afterwards (since audio in general on Linux is such a gnarly thing) but we'd be happy to try to at least try to provide advice again if that is the case.
The Linux build instructions in this repo are much better than they used to be, so you're welcome to have a go. There's always plenty of folks over on the community forum (https://in-thread.sonic-pi.net/) that would be willing to help you with advice as well 🙂

@Ryder17z - it might be worth opening up a separate issue so that we can help you troubleshoot your particular issue there without spamming the lovely folks here with unrelated advice - I suspect your issue has a slightly different root cause.