[Bug 926688] [NEW] upstart task alsa-restore has no effect

Jochen Fahrner 926688 at bugs.launchpad.net
Sat Feb 4 14:43:52 UTC 2012


Public bug reported:

There is a upstart task 'alsa-restore' which should restore the alsa
state to the state that was saved with upstart task 'alsa-store'.

This does not work. It looks like there is some other task that
initializes alsamixer to its default state AFTER alsa-restore is run.

There is a help page which recommends running 'alsactl restore' in the users startup applications:
https://help.ubuntu.com/community/MacBook5-1/Natty

This should not be necessary if the upstart task 'alsa-restore' was
working right.

I suggest find the task that is initializing alsamixer to its default
state and eliminate this, or delay alsa-restore until the initialization
was done.

This happens in latest Natty release, but I think this problem also
exits in Oneiric because this problem exists as far as I can remember.

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


** Tags: alsa alsactl restore upstart

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

Title:
  upstart task alsa-restore has no effect

Status in “upstart” package in Ubuntu:
  New

Bug description:
  There is a upstart task 'alsa-restore' which should restore the alsa
  state to the state that was saved with upstart task 'alsa-store'.

  This does not work. It looks like there is some other task that
  initializes alsamixer to its default state AFTER alsa-restore is run.

  There is a help page which recommends running 'alsactl restore' in the users startup applications:
  https://help.ubuntu.com/community/MacBook5-1/Natty

  This should not be necessary if the upstart task 'alsa-restore' was
  working right.

  I suggest find the task that is initializing alsamixer to its default
  state and eliminate this, or delay alsa-restore until the
  initialization was done.

  This happens in latest Natty release, but I think this problem also
  exits in Oneiric because this problem exists as far as I can remember.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/926688/+subscriptions




More information about the foundations-bugs mailing list