Qjackctrl won't start

[Doug B]

Qjackctrl won't start and i get the following error message:

"13:00:16.954 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock"

This is using Mint 18.x and the Cinammon desktop.

Any ideas? Thanks.

[MrEen]

I'd suggest opening the Software Manager, type in jackd, and see if Jackd is installed along with either Jackd1 or Jackd2. If you don't have Jackd installed, that's probably the source of your troubles. I also have Jackd2 installed, but that may not be important in your case.

[Flemur]

Qjackct[r]l won't start and i get the following error message:
...

This might help -
viewtopic.php?f=48&t=178481

[phd21]

Hi "Doug B",

I just read your post and the good replies to it. Here are my thoughts on this as well.

It would help to know more about your system setup. If you run "inxi -Fxzd" and "lsusb" from the console terminal prompt, highlight the results, copy and paste them back here, that should provide enough information.

Did you install the "multimedia-jack" meta package from the Software Manager or Synaptic Package Manager (SPM) which may require restarting or at least logging out and back in?

Hope this helps ...

[Doug B]

Here ya go:
~ $ inxi -Fxzd
System: Host: dougshome Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.1 Serena
Machine: Mobo: ASUSTeK model: A68HM-K v: Rev X.0x Bios: American Megatrends v: 1503 date: 03/10/2016
CPU: Quad core AMD A10-7860K Radeon R7 12 Compute Cores 4C+8G (-MCP-) cache: 8192 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 28728
clock speeds: max: 3600 MHz 1: 1900 MHz 2: 2500 MHz 3: 1900 MHz 4: 1400 MHz
Graphics: Card: NVIDIA GK208 [GeForce GT 730] bus-ID: 01:00.0
Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
Resolution: 1680x1050@59.95hz
GLX Renderer: GeForce GT 730/PCIe/SSE2
GLX Version: 4.5.0 NVIDIA 384.111 Direct Rendering: Yes
Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
driver: snd_hda_intel bus-ID: 00:14.2
Card-2 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel bus-ID: 01:00.1
Card-3 DigiTech driver: USB Audio usb-ID: 004-003
Sound: Advanced Linux Sound Architecture v: k4.4.0-53-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 04:00.0
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 250.1GB (12.3% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 250.1GB
Optical: /dev/sr0 model: ASUS DRW-24B1ST j rev: 1.01 dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 48x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 222G used: 22G (11%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 8.53GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 9.0C mobo: N/A gpu: 0.0:38C
Fan Speeds (in rpm): cpu: 0
Info: Processes: 208 Uptime: 1:25 Memory: 1770.5/7927.4MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35

and also:

~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 0e6a:02c0 Megawin Technology Co., Ltd
Bus 004 Device 003: ID 1210:000a DigiTech
Bus 004 Device 002: ID 093a:2532 Pixart Imaging, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Doug B]

I'd suggest opening the Software Manager, type in jackd, and see if Jackd is installed along with either Jackd1 or Jackd2. If you don't have Jackd installed, that's probably the source of your troubles. I also have Jackd2 installed, but that may not be important in your case.

Jackd and jackd2 are installed.

[MrEen]

Hi Doug B.

Add yourself to the audio group with sudo adduser $USER audio and if that doesn't get it working post back the results of cat /etc/security/limits.d/audio.conf

This was mostly in Flemur's link, but I think now the limits needs changing in a new location, and I just want to see what you have before we change it (also creates a record if we need to revert.)

[Prabuddhadg]

So, did QjackCtl start? I have the same problem.

[phd21]

Hi "Doug B",

I do not see anything wrong with the results of the "inxi -Fxzd" console terminal command, so that is a good thing.

qjackctl is running on my Linux Mint KDE 18.3 system

What happens if you try to run this from the console terminal prompt?

Code: Select all

qjackctl

[trytip]

when you run this ulimit in Terminal you should have this output. what do you have?
ulimit -r -l
real-time priority (-r) 99
max locked memory (kbytes, -l) unlimited

[Prabuddhadg]

I have tried a number of times to install Jack, but when I open the QJackCtl application, I get the same message, which I have copied below. What am I doing wrong?

The message:
18:16:50.468 Statistics reset.
18:16:50.475 ALSA connection change.
18:16:50.479 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
18:16:50.680 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
18:16:50.808 ALSA connection graph change.
Sat Sep 29 18:16:50 2018: Starting jack server...
Sat Sep 29 18:16:50 2018: JACK server starting in realtime mode with priority 10
Sat Sep 29 18:16:50 2018: self-connect-mode is "Don't restrict self connect requests"
Sat Sep 29 18:16:50 2018: Acquired audio card Audio0
Sat Sep 29 18:16:50 2018: creating alsa driver ... hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|-|32bit
Sat Sep 29 18:16:50 2018: Using ALSA driver HDA-Intel running on card 0 - HDA Intel HDMI at 0xc1118000 irq 61
Sat Sep 29 18:16:50 2018: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Sat Sep 29 18:16:50 2018: Released audio card Audio0
Sat Sep 29 18:16:50 2018: ERROR: Cannot initialize driver
Sat Sep 29 18:16:50 2018: ERROR: JackServer::Open failed with -1
Sat Sep 29 18:16:50 2018: ERROR: Failed to open server
Sat Sep 29 18:16:52 2018: Saving settings to "/home/prabuddha/.config/jack/conf.xml" ...
18:16:55.340 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

[trytip]

Using ALSA driver HDA-Intel running on card 0 - HDA Intel HDMI at 0xc1118000 irq 61
Sat Sep 29 18:16:50 2018: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode

your problem is not jack or the control but alsa says can't be initialized. start by deleting everything in .config/pulse/ followed by running pulseaudio -k in terminal then run qjackctrl to see what messages you get with clean pulseaudio

[Prabuddhadg]

Using ALSA driver HDA-Intel running on card 0 - HDA Intel HDMI at 0xc1118000 irq 61
Sat Sep 29 18:16:50 2018: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode

your problem is not jack or the control but alsa says can't be initialized. start by deleting everything in .config/pulse/ followed by running pulseaudio -k in terminal then run qjackctrl to see what messages you get with clean pulseaudio

Thank you for your reply.

There were six files in the folder .config/pulse. I deleted all these files. Then running the pulseaudio -k command in the terminal brought those or similar files right back.

When I ran Qjackctl, I had the same problems that I mentioned earlier.

Then I deleted the files in the .config/pulse folder and then opened the Qjackctl. Same problem again. Only now there is only one Cookie file in the .config/pulse folder.

Does that indicate anything to you? I am a newbie anyway.

[trytip]

that indicates that you didn't run pulseaudio -k after deleting files in .config/pulse
something makes alsa not work, try to reload it

Code: Select all

sudo alsa force-reload