Yes, precisely.

Take this sequence:

    Start up the machine
    Boot to Ubuntu
    Log in
    Open sound input settings (gnome-control-center sound, input tab)
    Play some music

The input indicator moves with the music clearly denoting that the PCM
capture is enabled.  However, alsactl store produces an asound.state
file in which the PCM switch is turned off. Opening up alsamixer also
shows the item as off.  Same with amixer cget. Using alsactl to restore
a "correct" asound.state does NOT fix the problem, but if I turn the
switch on, then off again (via alsamixer, or amixer, regardless),
correct functioning is restored - PCM capture is disabled.

However, if I reboot, the problem shows up again. I haven't tested
logout-login after fixing the problem (i.e. if it causes the issue or
not), but I don't think it does (will test that shortly).

The workaround is now to have a script that runs at login, turning the
switch on, then off, using amixer (new discovery on my part).

However this is only applicable to my case in which I want PCM input to
be turned off at the beginning.  Other users might want it turned on
and/or other input means (microphone, line-in) turned off instead.  The
issue here is that state isn't being properly restored to where it
should - either "something" is altering the card's state post-alsa
initialization and state restore, without alsa's knowledge, or alsa
isn't restoring the state properly.

Hope this info helps.  I'll run the logout-login test shortly and relay
the results.

Cheers! Thanks for the quick reply!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133065

Title:
  Default mixer settings for EMU20K2 enable PCM Input on boot while
  showing it as disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions

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

Reply via email to