JACK won't start

Please try adding yourself to the 'audio' group.

In terminal:

sudo adduser <username> audio

On Tue, Mar 5, 2013 at 12:05 PM, Dražen Lučanin
<email address hidden>wrote:

> Public bug reported:
>
> A fresh install of Ardour, which as a prereq. has QjackCtl and I select
> "start" in QjackCtl to start up a JACK daemon. It doesn't work.
>
> Error pop-up (shows up 2 times, btw, making testing various settings
> harder):
>
> D-BUS: JACK server could not be started.
>
> Sorry
>
> The Messages / Status window output:
>
> http://paste.ubuntu.com/5588375/
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: qjackctl 0.3.9-2
> ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
> Uname: Linux 3.7.0-7-generic x86_64
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: amd64
> Date: Tue Mar 5 18:57:54 2013
> InstallationDate: Installed on 2013-01-20 (44 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: qjackctl
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: qjackctl (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 apport-bug quantal third-party-packages
>
> --
> You received this bug notification because you are a member of Ubuntu
> Studio Bugs, which is subscribed to qjackctl in Ubuntu.
> Matching subscriptions: ubuntustudio-bugs: qjackctl
> https://bugs.launchpad.net/bugs/1147405
>
> Title:
> JACK won't start
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1147405/+subscriptions
>

Thanks for the suggestion. Already tried that after reading some forum
post, but unfortunately it didn't work. (also, if this is necessary,
couldn't the installation script add me to the audio group
automatically?)

On Tue, Mar 5, 2013 at 10:22 PM, Scott Lavender
<email address hidden> wrote:
> Please try adding yourself to the 'audio' group.
>
> In terminal:
>
> sudo adduser <username> audio
>
>
> On Tue, Mar 5, 2013 at 12:05 PM, Dražen Lučanin
> <email address hidden>wrote:
>
>> Public bug reported:
>>
>> A fresh install of Ardour, which as a prereq. has QjackCtl and I select
>> "start" in QjackCtl to start up a JACK daemon. It doesn't work.
>>
>> Error pop-up (shows up 2 times, btw, making testing various settings
>> harder):
>>
>> D-BUS: JACK server could not be started.
>>
>> Sorry
>>
>> The Messages / Status window output:
>>
>> http://paste.ubuntu.com/5588375/
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 12.10
>> Package: qjackctl 0.3.9-2
>> ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
>> Uname: Linux 3.7.0-7-generic x86_64
>> ApportVersion: 2.6.1-0ubuntu10
>> Architecture: amd64
>> Date: Tue Mar 5 18:57:54 2013
>> InstallationDate: Installed on 2013-01-20 (44 days ago)
>> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
>> (20121017.5)
>> MarkForUpload: True
>> ProcEnviron:
>> TERM=xterm
>> PATH=(custom, no user)
>> XDG_RUNTIME_DIR=<set>
>> LANG=en_US.UTF-8
>> SHELL=/bin/bash
>> SourcePackage: qjackctl
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> ** Affects: qjackctl (Ubuntu)
>> Importance: Undecided
>> Status: New
>>
>>
>> ** Tags: amd64 apport-bug quantal third-party-packages
>>
>> --
>> You received this bug notification because you are a member of Ubuntu
>> Studio Bugs, which is subscribed to qjackctl in Ubuntu.
>> Matching subscriptions: ubuntustudio-bugs: qjackctl
>> https://bugs.launchpad.net/bugs/1147405
>>
>> Title:
>> JACK won't start
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1147405/+subscriptions
>>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1147405
>
> Title:
> JACK won't start
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/1147405/+subscriptions

At this point I'm not at all convinced that this is a bug. There are a couple of bugs that may be causing problems for you. To find out, please do the following.

Do a reboot, so we know it's a fresh session. Do not open any other applications than maybe a browser with this page only, a terminal, and qjackctl.

To find out how many audio devices you have, and what they hw id's are, do:

cat /proc/asound/cards

Should look something like:

 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfe8fc000 irq 45

I only have one device, and the hw ID is 0.

Now, to see if you can start jack on the device you want to try (in this case hw:0), do this in a terminal:

pasuspender -- jackd -d alsa -d hw:0

If that works, there may be three reasons to your problems:

1. you are using bad settings
2. jackdbus had crashed previously ( LP bug: #956438 ) and is now frozen. To kill it, do: killall -9 jackdbus
3. pulseaudio is using the same device you are attempting to start jack with, and PA(pulseaudio) is not letting go (known bug, fixed in pulseaudio3).

Let us know how things worked out.

Actually, you didn't need to open qjackctl at all for doing this practical debug.

Well, be it a bug or not - Ardour (that is, QJackCtl) doesn't start
using all default settings in Ubuntu, while e.g. Audacity works
perfectly fine from the first try on the same hardware. I'm just
reporting what I'm experiencing.

I followed your instructions. My sound cards:

 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xe4804000 irq 47
 1 [U0x46d0x8da ]: USB-Audio - USB Device 0x46d:0x8da
                      USB Device 0x46d:0x8da at usb-0000:00:1d.2-1, full speed

(0 is my laptop's sound card and 1 is a usb webcam that also has a microphone)

After a restart and before I open anything (except Firefox), when I
start JACK using either QJackCtl (without touching any settings, so
the device is still set to "(default)") or your terminal command, it
works in both cases.

$ pasuspender -- jackd -d alsa -d hw:0
jackdmp 1.9.9
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
JACK server starting in realtime mode with priority 10
control device hw:0
control device hw:0
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback

I can start Ardour afterwards and record and listen to sound normally.
I cannot, however, listen to music in other applications - like
Rhythmbox. Even after I close the JACK session. To get music to play
in other apps, I have to kill -9 jackdbus like you said and pkill
pulseaudio (to get it to restart). After I do this, Rhythmbox is
singing, but JACK won't start with the old symptoms. This is what the
terminal starting method throws:

$ pasuspender -- jackd -d alsa -d hw:0
jackdmp 1.9.9
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
JACK server starting in realtime mode with priority 10
control device hw:0
control device hw:0
audio_reservation_init
Failed to acquire device name : Audio0 error : Device or resource busy
Audio device hw:0 cannot be acquired...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
(s)kermit@hocus-pocus:~$

I am running the default pulseaudio 2.1-0ubuntu4. I guess this is a
duplicate of that bug you mentioned that got fixed in version 3. Hope
the fix reaches me in Raring. Thanks for the help!

On Wed, Mar 6, 2013 at 2:58 PM, Kaj Ailomaa <email address hidden> wrote:
> Actually, you didn't need to open qjackctl at all for doing this
> practical debug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1147405
>
> Title:
> JACK ...

I too had the same issue. jackd doesn't start with the default settings in qjackctl.
and finally , I get it working.

The problem was because of ,
*) periods/buffer == 2
*) disable dbus interface
*) do not use realtime ( Until you have granted required permissions )
*) use correct interface name (cmdline param '-d' )

I've recommended Ubuntu Studio for my son who works on audio production, but it's a little hard to get things running, I can't understand it. I install, open the apps and it doesn't work.
It should have a tutorial for get things running.

I have similar issue qjackctl

pasuspender -- jackd -d alsa -d hw:0

ATTENTION: The playback device "hw:0" is already in use. Please stop the application using it and run JACK again

my user is in groups audio, pulse, ...
several reboots

Hunted down any program that could run audio and kill them
still not working
This happened after following troubleshooting
https://help.ubuntu.com/community/SoundTroubleshootingProcedure

alsa info sh

http://alsa-project.org/db/?f=9a8410ea124a25e1830f39bca4fbd4c363a701ca

see also my question
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/701319

Status changed to 'Confirmed' because the bug affects multiple users.