after update Tumbleweed I can't start Jackd Jack Connection Kit

English Install/Boot/Login
21

I use Carla more than anything else, I love all the stuff produced by this Portuguese developer… hats off to him… I respect all the work he puts in with the Calf plugins and all

22

It’s been more than a month now and this issue is not resolved… It has to be something to do with the configuration in Tmbleweed, because even using the latest kernel 4.0.1-1 in 13.2 does not break it, only iwth Tumbleweed is there a problem. I installed Tumbleweed on a blank computer and its the same, same messages as before. jack won’t start

 10:19:22.044 ALSA connection change.
 10:19:22.056 JACK is starting...
 10:19:22.057 /usr/bin/jackd -P89 -m -dalsa -r44100 -p1024 -n3 -Xraw -D -Chw:MID -Phw:io2
 10:19:22.073 ALSA connection graph change.
 10:19:22.094 JACK was started with PID=3819.
 10:19:22.260 ALSA active patchbay scan...
 10:19:24.267 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
 10:19:24.291 JACK is stopping...
 10:19:24.337 JACK was stopped
 10:19:24.337 JACK has crashed.

I’m pretty handy with audio issues and normally never have a problem, as I’ve been doing this job for 20 years. Other people are having the same problem. Nobody I know has gotten Jack to work on Tumbleweed in the last weeks.
This is really a pity. For me using professional audio devices, Jack is an essential feature.
Tumbleweed over the past year (and Factory) has been so stable and solid , even while having to use proprietary NVIDIA drivers, that it’s hard to leave it stand.
Being able to use GNOME 3.16 or have all the very latest apps in an environment that works, and KDE too is so fast makes it hard to go back.
It should be noted that there have been audio improvements in the latest Kernels since 3.16.
BUT guys, not being able to resolve this issue for me is a dealbreaker. I’m leaving Tumbleweed behind for good. Giordano maintains Ardour 3 for openSUSE on OBS and also dropped Tumbleweed. I guess some people here are right. Tumbleweed is experimental and not recommendable in a production environment. A pity. Now to try Arch.

23

Yes, kernel 4.0.1 don’t resolved this issue. I’m waiting for a SSD for my computer. If the problem persists i would install 13.2 and not Thumpleweed in it. Other than this it works great.

24

Hello,

I haven’t seen your bug report on bugzilla.
You can still wait for somebody else to do it, or for the problem to be solved by itself, but you’ll have to wait. Jack is not used by everybody (and not everybody reads the forums).

Regards,

Antoine

25

Bug submitted to bugzilla. My first time. I hope i made it correctly.

26

Yeah, you got my support, mate. I’ve been using kdenlive too for audio edits where it goes back to Final Cut Pro on a MAC… actually, kdenlive is good and it’s impressed many’s a filmmaker I showed it to

27

I know, but I’m screwed for time… I am living in Borneo, it’s eight hours later here and we’re already in the next day when you are having yer lunch :slight_smile: I know, I should’ve but… thanks for doing it guys, I gave the submitter a + up

28

thank you kindly

29

what is the link?

30

https://bugzilla.opensuse.org/show_bug.cgi?id=930015

31

thanks, the rest of us can watch the progress too…:wink:

32

Roberto I’ve been following the dialogue with Takashi Iwai… I don’t have any 3.x kernels left as I’ve had to replace the disk on my production machine. So I’ll try out what he’s saying and see if it works… If 3.16 works with Jack in Tumbleweed, then its clear where the fault is, but looks doubtful that there’ll be any quick fix. This looks a bit ominous.
I’ll let you know what happens in a day or two…

33

Thank you, johnoshock :slight_smile:

34

sorry, for being so late but my HDD failed and I had to replace it… lots of work getting everything back the way it was…
so I tried 3 things:

  1. I installed the 3.16 kernel in my tumbleweed setup and it works fine, but Jack does not… exact same errors as I posted already. i.e. no difference
  2. I installed 13.2 on a machine and tried jack and qjack etc and it worked fine.
  3. I installed 3.19 in the 13.2 setup and it worked fine and JACK worked too, so then I tried 4.0.3-1 and JACK still worked. So it’s got nothing to do with the kernel but more like something in Tumbleweed packaging
35

It seems that the problem might be that realtime scheduling is not implemented, so how can we do this on Tumbleweed?
This was always available before…

jackd -v
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
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
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
36
  • add this to /etc/security/limits.conf:

@audio - rtprio 99
@audio - nice -19
@audio - memlock unlimited

  • add your user to the group audio

Tip:
add “threadirqs” to the kernel commandline (check /etc/sysconfig/bootloader:DEFAULT_APPEND)

that said, try to run jackd explicitly without RT (aka with -r), does the problem persist?
In my case it does, which would mean, that RT-permissions are not the root cause…

37

JACK website faq at How do I configure my linux system to allow JACK to use realtime scheduling? | JACK Audio Connection Kit has this to say about Systems using PAM (see 1. Editing the configuration file):

“Contrary to a lot of misinformation on the web, there is no reason to include a line here that provides enhanced “niceness” control, which is completely irrelevant for realtime scheduling and low latency audio applications.”

Any comment on that?

You may also want to take a look on that page at the link “here” under “This may not work!”…, although I don’t know anything about CGroup configuration.

38

You’re right on that line. It’s a relict several years old, but it doesn’t hurt neither, so it is still there.

Fact is, I do have 3-4 systems with identical configuration where it did work before some update in the last weeks.
They only system where I can compare with a “normally” working jackd is a 13.1 server installation where I installed jackd (1.9.9) today to compare with the other tumbleweed systems…

It doesn’t matter if I try to start as normal user (with audio group) or as root, with RT or withouth. I can even try to start only jackd without any options, it’s always the same, not even the usage-info is shown. :frowning:

39

I don’t use it regularly but have installed and run it successfully on previous openSUSE releases. Obviously have the same problem on TW starting up with qjackctl as the guys here (thanks to them for making the hard yards with bug report).

I also have jack installed and working fine on standard 13.1/KDE system (using pasuspender in qjackctl to start), and the same in a test 13.2 VM with VirtualBox.

40

I had already edited the limits.conf file before AND added myself to the audio group. I even tried creating a realtime group and added myself to it, but all to no avail. However, I hadn’t tried the “threadirqs” thing. Will do that… :wink: