Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jack Wont Start After arch linux System Upgrade. #94

Open
johnaweiss opened this issue Apr 24, 2020 · 5 comments
Open

jack Wont Start After arch linux System Upgrade. #94

johnaweiss opened this issue Apr 24, 2020 · 5 comments

Comments

@johnaweiss
Copy link

johnaweiss commented Apr 24, 2020

Not sure if i'm running jack1 or jack2.
Up to now, it's been running just fine.

I'm running alsa only. Pretty sure i do not have pulse installed.

Here's the error log from qjackctl:

19:10:30.578 Statistics reset.
19:10:30.676 ALSA connection change.
19:10:30.678 D-BUS: Service not available (org.jackaudio.service aka jackdbus).
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
19:10:30.777 ALSA connection graph change.
19:10:33.815 JACK is starting...
19:10:33.815 /usr/bin/jackd -v -dalsa -dhw:H1 -r44100 -p1024 -n2
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
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
19:10:33.844 JACK was started with PID=653.
getting driver descriptor from /usr/lib/jack/jack_net.so
could not open driver .so '/usr/lib/jack/jack_net.so': libcelt0.so.2: cannot open shared object file: No such file or directory
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_alsa_midi.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
getting driver descriptor from /usr/lib/jack/jack_dummy.so
JACK compiled with System V SHM support.
server default' registered registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime loading driver .. start poll on 3 fd's apparent rate = 44100 new client: alsa_pcm, uuid = 8589934593 type 1 @ 0x55ee9276cd60 fd = -1 creating alsa driver ... hw:H1|hw:H1|1024|2|44100|0|0|nomon|swmeter|-|32bit control open "hw:H1" (No such device) ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa starting server engine shutdown server thread back from poll freeing shared port segments stopping server thread last xrun delay: 0.000 usecs max delay reported by backend: 0.000 usecs freeing engine shared memory max usecs: 0.000, engine deleted cleaning up shared memory cleaning up files unregistering server default'
19:10:34.139 JACK was stopped
19:10:35.990 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
19:13:34.652 JACK is starting...
19:13:34.653 /usr/bin/jackd -v -dalsa -dhw:H1 -r44100 -p1024 -n2
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
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
getting driver descriptor from /usr/lib/jack/jack_net.so
could not open driver .so '/usr/lib/jack/jack_net.so': libcelt0.so.2: cannot open shared object file: No such file or directory
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_alsa_midi.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
getting driver descriptor from /usr/lib/jack/jack_dummy.so
JACK compiled with System V SHM support.
server default' registered 19:13:34.719 JACK was started with PID=801. loading driver .. registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime start poll on 3 fd's new client: alsa_pcm, uuid = 8589934593 type 1 @ 0x563caee8bd60 fd = -1 apparent rate = 44100 creating alsa driver ... hw:H1|hw:H1|1024|2|44100|0|0|nomon|swmeter|-|32bit control open "hw:H1" (No such device) ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa starting server engine shutdown freeing shared port segments stopping server thread last xrun delay: 0.000 usecs max delay reported by backend: 0.000 usecs freeing engine shared memory max usecs: 0.000, engine deleted WARNING: 1 message buffer overruns! cleaning up shared memory cleaning up files unregistering server default'
19:13:34.760 JACK was stopped
19:13:36.829 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed

@falkTX
Copy link
Member

falkTX commented Apr 24, 2020

Does not seem an issue with jack, likely you just need to rebuild it.
This message:

libcelt0.so.2: cannot open shared object file: No such file or directory

implies that jack is not part of your system and built manually. so now the system libraries updated and created a mismatch of versions.

@ksralgp
Copy link

ksralgp commented Apr 25, 2020

I also run jack on archlinux and see the messages

could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
could not open driver .so '/usr/lib/jack/jack_net.so': libcelt0.so.2: cannot open shared object file: No such file or directory

I am still able to use jack as my audio driver in programs like Ardour and Hydrogen. So on my machine things work in spite of not having those shared libraries.

I would guess the following diagnostic is pointing to your problem:

open "hw:H1" (No such device) ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card ALSA: Cannot open PCM device alsa_pcm for playback.

I am not familiar with the syntax 'hw:H1'. That does not work on my machine and I see a similar error message. If I instead use 'hw:1' things work.

@johnaweiss
Copy link
Author

@ksralgp Do you mean i should change that string in the source, and recompile?

thx

@ksralgp
Copy link

ksralgp commented May 1, 2020

I have no experience in qjackctl, but poking around it looks like you can set the device name in the "setup" menu. There is an "interface" box. I entered "hw:1" there and was able to start jackd. Alternatively it has a pull-down that shows you the devices it detected. Maybe you need to select something else there?

@johnaweiss
Copy link
Author

Thx, i'll try that. So, the issue is a device is named that jack can't find? Does jack require any devices at all, to start?

However, without doing that (or anything else different), I noticed sometimes jack runs, sometimes it doesn't. Seem intermittent, or only works under just-so conditions or sequence of events (which i can't tell yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants