This is my fault. When I designed the loud volume handling, I considered
only the cases where (1) you increase the volume, which produces the
“Increase Volume” alert; or (2) you start or wake the device, which
automatically reduces the volume. <https://wiki.ubuntu.com/Sound#limits>
I did not consider the case where you plug in headphones that have a
loud remembered volume. Ideally an engineer or QA would have realized
that “Increase Volume” doesn’t make sense in this case, but I guess they
didn’t.
To handle this case, we could follow either of the same two approaches:
(1) put up an equivalent alert, with slightly different text and buttons (not
just “OK”);
(2) automatically reduce the volume like we do on startup/wake.
I’m inclined to go with option (2), reducing the volume, because I don’t
know what sensible wording would be for an alert. It would need to say
something like, “Volume was loud last time you used these headphones.
Restore previous volume? ( Reduce ) ( Restore )” But that seems
unpleasantly bureaucratic.
** Changed in: indicator-sound (Ubuntu)
Assignee: (unassigned) => Matthew Paul Thomas (mpt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572343
Title:
Hearing damage warning not intuitive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1572343/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
