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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
