[SOLVED] System hangs after shutdown of jack

Discussion of all things Raspberry Pi / Raspberry Pi 2 related

Moderators: MattKingUSA, khz

Post Reply
User avatar
flappix
Established Member
Posts: 50
Joined: Thu Jan 19, 2017 10:39 pm
Location: Germany
Been thanked: 16 times

[SOLVED] System hangs after shutdown of jack

Post by flappix »

Hi @ all,
since the last system update (ArchLinuxARM) I have the problem that the system is really slow / sometimes unresponsive after I stop jack. While jack is running everything is fine. When I stop it I get long delays between typing commands an their execution. I type a character and after 10s up to some minutes I see the character in the console.

I installed the previous version of jack which was installed before the update but it did not change anything. Before the system update I didn't have this issue.

It's really annoying because I have to start/stop it very often.

Would be very cool if someone could help :)
Last edited by flappix on Mon Oct 15, 2018 5:02 pm, edited 1 time in total.
User avatar
khz
Established Member
Posts: 1648
Joined: Thu Apr 17, 2008 6:29 am
Location: German
Has thanked: 42 times
Been thanked: 92 times

Re: System hangs after shutdown of jack

Post by khz »

Is the problem still when you run

Code: Select all

killall -9 jackdbus qjackctl
(or "jackd" or "Cadence") in the console?
If so then start jack (== qjackctl or Cadence) from the console for testing and start/stop it. What does the console say?
. . . FZ - Does humor belongs in Music?
. . GNU/LINUX@AUDIO ~ /Wiki $ Howto.Info && GNU/Linux Debian installing >> Linux Audio Workstation LAW
  • I don't care about the freedom of speech because I have nothing to say.
User avatar
flappix
Established Member
Posts: 50
Joined: Thu Jan 19, 2017 10:39 pm
Location: Germany
Been thanked: 16 times

Re: System hangs after shutdown of jack

Post by flappix »

Hi,
thank you very much!
The problem was not jack itself but mod-host, an application using jack. I quit all applications using jack (and jack itself) in a script. Adding -s KILL to all kill commands solved the problem.
Post Reply