Closed due to no response.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
--
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Is this bug still relevant to pulseaudio?
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Incomplete
** Changed in: ayatana-design
Assignee: John Lea (johnlea) => (unassigned)
--
You received this bug notification because you are a member of Unity API
bugs, which is
** Description changed:
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
This bug was fixed in the package gsettings-ubuntu-touch-schemas -
0.0.1+14.04.20140401-0ubuntu1
---
gsettings-ubuntu-touch-schemas (0.0.1+14.04.20140401-0ubuntu1) trusty;
urgency=low
[ Michael Terry ]
* Add Muted and Volume properties for sharing with the greeter. (LP:
** Branch linked: lp:ubuntu/trusty-proposed/indicator-sound
--
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
This bug was fixed in the package indicator-sound -
12.10.2+14.04.20140324-0ubuntu1
---
indicator-sound (12.10.2+14.04.20140324-0ubuntu1) trusty; urgency=low
[ Michael Terry ]
* Sync volume and mute settings with AccountsService. (LP: #840777)
[ Ted Gould ]
* Add an apport
But honestly with both methods, we have a11y issues with shared
machines
Sure, but it's much less with system-wide volume: all a blind user needs
to remember is roughly how long the machine takes to start up. Then if
they haven't heard the drumbeat, they can adjust the volume, and that
volume
- B sits down, switches to their account, greeter switches sound to
muted status
Ah, that's the part I missed. Does that mean if you're using a
screenreader and scrolling through the list of accounts, every user
account name will be read out at a different volume, regardless of the
volume you
Does that mean if you're using a screenreader and scrolling through
the list of accounts, every user account name will be read out at a
different volume, regardless of the volume you set at the greeter?
Yes, and it is an a11y issue. I mentioned this problem in the email
thread, but that thread
Unfortunately the Desired solution here seems to contradict itself.
I agree with Lars and John that volume should be system-wide: changes
made to the volume control in the Unity Greeter should carry through to
the logged in session and vice versa. That's unfortunate if one of your
family is hard
mpt, I think there's some confusion. Lars and you want a system-wide
volume. John wants a per-user volume (i.e. like we have today, just
with the greeter reflecting the user's volume).
With per-user volume, in your example when B logs in, B will have a
muted sound. That's the point of changing
I just discussed this with John. He explained that the motivation for
making it per-user was to avoid the problem where some settings are per-
user and some are system-wide, and users can't predict which is which.
Now, consider the case where you don't log in at all. You turn on your
PC, and at
** Branch linked: lp:~mterry/gsettings-ubuntu-touch-schemas/volume
--
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
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
** Changed in: ayatana-design
Status: Incomplete = Fix Committed
** Changed in: ayatana-design
Assignee: (unassigned) = John Lea (johnlea)
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to The Sound Menu.
Volume is a system-wide setting. I think pulse should store the volume
somewhere outside of the user's session.
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-greeter
Status: Triaged = Invalid
** Changed in: indicator-sound
17 matches
Mail list logo
