unity-api-bugs team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

I hear you, mpt.  Startup sounds (drums / orca) are interesting
problems, particularly if a11y is involved.  You almost want an a11y
setting that says "on startup, always use X volume."

I still don't understand your A/B scenario problem.  Using the behavior from the bug description (and my branches), the following will happen:
- A logs out with volume at 100%, greeter shows volume at 100%
- B sits down, switches to their account, greeter switches sound to muted status
- B logs in, gets muted session

You say you talked to John about this, but don't mention if there was a
consensus reached.  The design plan of record is what I described above
and this bug description outline.  I don't have a dog in this race, I
just want to fix this problem one way or the other.

Another point to mention here is SilentMode.  Matthew, you describe
wanting volume/mute to be system wide.  I'm guessing you would like to
make SilentMode that way too?  (harder technically, but seems
semantically related to mute)

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to The Sound Menu.
https://bugs.launchpad.net/bugs/840777

Title:
  Muting sound indicator in Unity Greeter does not mute sound on login

Status in Ayatana Design:
  Fix Committed
Status in Sound Menu:
  Invalid
Status in Unity Greeter:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Triaged
Status in “pulseaudio” source package in Raring:
  New

Bug description:
  I am using beta edition of Ubuntu 11.10,with lightdm 0.9.3-0ubuntu8,and unity 4.12.0-0ubuntu2,
  There is a new feature in Display Manager(well,I didn't notice it in gdm,but it might have been there as well),That you can mute the sound so that login sound wont play(This option exists in the top of the lightdm login page,when you turn on ubuntu and load it)However,Login sound will still play and sound settings will change regardless of what you choose.
  I should add that,this happens only after a reboot or shutdown,boot again,and not when you logout and login again

  Desired solution:
  - Any changes made to the volume control in the Unity Greeter should carry through to the logged in session and vice versa.  
  - For example, if a user changes or mutes the volume in the Unity Greeter, when they are logged in to their session this value should be carried over
  - The other way around is also true, if a user changes or mutes the volume in their session, when they log out this value should be displayed in the greeter.
  - Sound settings are stored individually on a per user account basis.  The sound settings displayed in the greeter should change in line with the currently focused user account.  So for example User A is currently focused and has has volume at 100%. If the focus in the greeter is changed to User B (who has volume muted), the sound indicator should change to display the muted state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/840777/+subscriptions