Ubuntu

Muse can't connect to jack (error message)

Reported by Pablo_F on 2011-05-18
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
muse (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: muse

Steps to reproduce it:

Launch qjackctl, start the jack daemon

Muse starts, throwing this message:

"MusE failed to find a Jack audio server.
MusE will continue without audio support (-a switch)!
If this was not intended check that Jack was started. If Jack was started check that it was started as the same user as MusE."

It defaults to dummy audio driver.

$ muse
Denormal protection enabled.
no message buffer overruns
no message buffer overruns
unknown option character l
cannot connect to jack server
cannot create jack client
Trying RTC timer...
fatal error: open /dev/rtc failed: Permiso denegado
hint: check if 'rtc' kernel module is loaded, or used by something else
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 52
starting with default template
  name2route: <alsa_pcm:playback_1> not found
addRoute: invalid dst
  name2route: <alsa_pcm:playback_2> not found
addRoute: invalid dst
Get alsa timer for dummy driver:
AlsaTimer::initTimer(): best available ALSA timer: system timer
AlsaTimer::setTimerTicks(): warning: requested 46 Hz, actual freq is 50 Hz
audio dummy thread _NOT_ running SCHED_FIFO
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max is 250)
  freq stays at 250 Hz
looping waiting for sequencer thread to start
Attempting to auto-start LASH server
lash_dbus_service_connect_handler: Failed to connect to LASH server: The name org.nongnu.LASH was not provided by any .service files
show did you know dialog!!!!

$ jackd --version
jackdmp 1.9.7

muse version:
1.1-0ubuntu3

Workaround:

Install jackd1.

$ jackd --version
jackd version 0.120.1 tmpdir /dev/shm protocol 24

$muse
Denormal protection enabled.
Trying RTC timer...
fatal error: open /dev/rtc failed: Permiso denegado
hint: check if 'rtc' kernel module is loaded, or used by something else
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 54
starting with default template
  name2route: <alsa_pcm:playback_1> not found
addRoute: invalid dst
  name2route: <alsa_pcm:playback_2> not found
addRoute: invalid dst
JACK: buffersize changed 1024
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max is 250)
  freq stays at 250 Hz
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
Attempting to auto-start LASH server
lash_dbus_service_connect_handler: Failed to connect to LASH server: The name org.nongnu.LASH was not provided by any .service files
show did you know dialog!!!!

Disregarding the ugly messages, muse is a jack audio client now:

$jack_lsp
system:capture_1
system:capture_2
system:capture_3
system:capture_4
system:capture_5
system:capture_6
system:capture_7
system:capture_8
system:capture_9
system:capture_10
system:capture_11
system:capture_12
system:playback_1
system:playback_2
system:playback_3
system:playback_4
system:playback_5
system:playback_6
system:playback_7
system:playback_8
system:playback_9
system:playback_10
MusE:Out 1-0
MusE:Out 1-1

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: muse 1.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu May 19 00:54:46 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110416)
ProcEnviron:
 LANGUAGE=es_ES:en
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: muse
UpgradeStatus: No upgrade log present (probably fresh install)

Pablo_F (pablo-fbus) wrote :
Fabrice Coutadeur (fabricesp) wrote :

Hi,

and thanks to take time to make Ubuntu better.
If I understand you correctly, this means that by installing jackd1 instead of jackd2, muse works correctly?

If this is the case, I'll test it and if I can reproduce it, I'll push a SRU to have that change integrated to Natty.

Thanks,
Fabrice

Pablo_F (pablo-fbus) wrote :

"If I understand you correctly, this means that by installing jackd1 instead of jackd2, muse works correctly?"

Yes. Well, I haven't tested thoroughly but at least it is using jack audio for playback. With jackd2, muse does not realise that jackd is started. Normally, jack clients should work with any jackd implementation (1 or 2).

Spencer Jackson (ssjackson71) wrote :

*BUMP*
I haven't installed jackd1 to try but I have the exact same errors.

Rob Davies (megamasha) wrote :

Using kubuntu, same problem, switching to jack1 works as a workaround - but this shouldn't be necessary, and breaks my pulseaudio-jack-sink connection (at least initally, haven't restarted yet)
Does anyone know if this will be fixed in muse 2.0, soon to be released?

Josh Thies (thies-josh) wrote :

Thank you sooo much. This helped me out.

Alf (alfcyber) wrote :

The problem i think, is that the muse in Studio (natty) is compiled without jack support
(e.g. ldd /usr/bin/muse ... and see)
solved this, recompiled muse, but first have to install jackd1,
after all its possible to reinstall jackd2, it should work.

Launchpad Janitor (janitor) wrote :

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

Changed in muse (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers