Public bug reported:

Binary package hint: pulseaudio

This bug report being filed per request by one of the bug team (dtchen).
In simple terms, upon an initial boot and login, ALSA will not pass MIDI
data from a supported interface until it is forcibly restarted without
pulseaudio respawning.

This is being seen under a clean install of Ubuntu Studio 9.10 i386. The
MIDI interface is a TASCAM US-122L which is newly supported in the
official (realtime) kernel.

pulseaudio version information: 
  Installed: 1:0.9.19-0ubuntu4
  Candidate: 1:0.9.19-0ubuntu4
  Version table:
 *** 1:0.9.19-0ubuntu4 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

alsa-base version information:
  Installed: 1.0.20+dfsg-1ubuntu5
  Candidate: 1.0.20+dfsg-1ubuntu5
  Version table:
 *** 1.0.20+dfsg-1ubuntu5 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Upon initial login following a full reboot, JACK displays the MIDI
interface as an available input and output, but connecting to even a
basic synth app (in this case for testing, ZynAddSubFX) as a controller
will not pass data. This is true for both the alsa_pcm and JACK's MIDI
interfaces.

Errors seen in /var/log/syslog: 
Nov 14 17:29:07 quark pulseaudio[3084]: module-alsa-card.c: Failed to find a
working profile.
Nov 14 17:29:07 quark pulseaudio[3084]: module.c: Failed to load  module 
"module-alsa-card" (argument: "device_id="1" 
name="usb-TASCAM_US-122L_no_serial_number-01" 
card_name="alsa_card.usb-TASCAM_US-122L_no_serial_number-01" tsched=yes 
ignore_dB=no card_properties="module-udev-detect.discovered=1""):
initialization failed.

The steps which provide a workaround are as follows:

 - exit JACK and all audio apps
 - create ~/.pulse/client.conf with "autospawn = no" to avoid respawn
 - sudo alsa reload, which returns the warning "/sbin/alsa: Warning: Processes 
using sound devices: 3084(pulseaudio)".

If other apps (LMMS, for example) have been started, even if the
application has been exited, it is possible but not guaranteed that they
will also be listed in the warning message and must be killed with a
SIGKILL (kill -9) before the alsa reload will be effective. Again, this
definitely not always the case.

It is also important to note that this seems to only be an issue at
first login; once the problem has been resolved, the user can log out
and in without encountering any problems routing the MIDI interface.

For reference, here is the output from an alsa reload:

quark% sudo alsa reload
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/markh/.gvfs
      Output information may be incomplete.
/sbin/alsa: Warning: Processes using sound devices: 2949(timidity). 
Unloading ALSA sound driver modules: snd-hda-codec-realtek snd-hda-intel 
snd-hda-codec snd-pcm-oss snd-mixer-oss snd-pcm snd-usb-us122l snd-usb-lib 
snd-hwdep snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event 
snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: 
snd-hda-codec-realtek snd-hda-codec snd-pcm snd-hwdep snd-seq snd-timer 
snd-seq-device snd-page-alloc).
Loading ALSA sound driver modules: snd-hda-codec-realtek snd-hda-intel 
snd-hda-codec snd-pcm-oss snd-mixer-oss snd-pcm snd-usb-us122l snd-usb-lib 
snd-hwdep snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event 
snd-seq snd-timer snd-seq-device snd-page-alloc.

The apport information was collected before the above successful alsa
reload. The attached pulseverbose.log was attached *after* the alsa
reload event, to show both initial state and the effect of the reload.

ProblemType: Bug
Architecture: i386
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name   : 'Realtek ALC888'
   Components   : 'HDA:10ec0888,10438260,00100001'
   Controls      : 35
   Simple ctrls  : 20
Card1.Amixer.info:
 Card hw:1 'US122L'/'TASCAM US-122L (644:800e if 0 at 002/005)'
   Mixer name   : ''
   Components   : ''
   Controls      : 0
   Simple ctrls  : 0
Card1.Amixer.values:
 
Date: Sat Nov 14 17:58:55 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: pulseaudio 1:0.9.19-0ubuntu4
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: pulseaudio
Uname: Linux 2.6.31-9-rt i686
XsessionErrors:
 (gnome-settings-daemon:3069): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (gnome-settings-daemon:3069): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (nautilus:3164): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:3186): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

** Affects: pulseaudio (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: alsa apport-bug i386 midi pulseaudio

-- 
Pulse audio and ALSA failing to provide transport for MIDI interface
https://bugs.launchpad.net/bugs/482902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to