jackd suddenly stopped working

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,
I am using ubuntu studio 24.04 and it looks like jackd2 has stopped working on a jackd client that I am using:

I used to start normally the jackd session as
$ jackd -dnet -C 4 -P 8

but I've been seeing these messages since last night:
jackdmp 1.9.21
[...]
[W][02502.216661] default      | [       control.c:   67 jackctl_server_create2()] not implemented 0x573493a90ec0 0x573493a91020 0x573493a910f0
[W][02502.216855] default      | [       control.c:  154 jackctl_server_get_parameters()] 0x57349bb68d10: not implemented
[W][02502.216925] default      | [       control.c:  142 jackctl_server_get_drivers_list()] 0x57349bb68d10: not implemented
[W][02502.216966] default      | [       control.c:  225 jackctl_driver_get_name()] 0x57349bb68cf0: not implemented
Unknown driver "net"
[W][02502.217019] default      | [       control.c:   94 jackctl_server_destroy()] 0x57349bb68d10: not implemented

I am mostly worried about this
"unknown driver net" messages, but perhaps the warnings are also relevant.

Indeed something is changed and the backends have vanished:
$ jackd --help
[...]
Available backends:
[W][03817.946848] default      | [       control.c:  233 jackctl_driver_get_type()] 0x5a35d9340cf0: not implemented
[W][03817.946852] default      | [       control.c:  225 jackctl_driver_get_name()] 0x5a35d9340cf0: not implemented
      dummy (slave)

[W][03817.946857] default      | [       control.c:  165 jackctl_server_get_internals_list()] 0x5a35d9340d10: not implemented
Available internals:

[W][03817.946863] default      | [       control.c:   94 jackctl_server_destroy()] 0x5a35d9340d10: not implemented

I found this topic https://linuxmusicians.com/viewtopic.php?t=19590 where reinstalling jack in arch fixed their issue..

I tried the same as
$ dpkg -l | grep jackd
$ sudo apt install --reinstall jackd jackd2 jackd2-firewire libjack-jackd2-0 libjack-jackd2-dev

but the issue persists. I assume some automatic update caused this but I wonder if anyone else has seen this and if you managed to fix it somehow.

Thank you in advance for your help
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux