Bug 202062 - audio/pulseaudio: New audio connection resets "mixer" to 75% volume.
Summary: audio/pulseaudio: New audio connection resets "mixer" to 75% volume.
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-03 17:25 UTC by ken
Modified: 2018-12-18 05:50 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (gnome)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ken 2015-08-03 17:25:35 UTC
General Description:
Occasionally when using the system and running a number of different apps (audio/pithos, www/firefox with pulse enabled, others), the audio volume of the system (as shown by the "mixer" utility) will get reset back to 75%. 
In particular, this seems to occur when a new application which uses PA is started and/or a new audio stream/thread/(whatever the terminology is) is created to output a sound from the app.

Example: 
1) Start pithos to listen to music.
2) Start Firefox and sign in to Slack
3) Get a notification on Slack and Firefox plays the little "ping" sound
 - as soon as the notification sound is about to play, the entire system volume drops from 100->75% (as shown by "mixer"). 
However, any future notification sounds from Firefox (at least for the current desktop session) do not modify the overall system volume again. This seems to imply it is an issue with the first-time init routines for a PA stream not taking the current system volume into consideration, but I have not been able to track it down any more than that.

Versions (although this happened with older versions as well): 
pulseaudio: 6.0_2
Firefox: 39.0,1 (with Pulseaudio build option enabled)
Comment 1 Walter Schwarzenfeld freebsd_triage 2018-01-12 22:08:24 UTC
We have firefox 57.0.2 and pulseaudio 11.0. So I think this is overcome by events.
Comment 2 Tobias Kortkamp freebsd_committer freebsd_triage 2018-12-18 05:50:26 UTC
(In reply to w.schwarzenfeld from comment #1)
Closing due to lack of new feedback after comment #1.