Date: Mon, 03 Aug 2015 17:25:35 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: maintainer-feedback requested: [Bug 202062] audio/pulseaudio: New audio connection resets "mixer" to 75% volume. Message-ID: <bug-202062-6497-3RysxdgkBP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202062-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-202062-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
ken@pcbsd.org has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to gnome@FreeBSD.org: Bug 202062: audio/pulseaudio: New audio connection resets "mixer" to 75% volume. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202062 --- Description --- 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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202062-6497-3RysxdgkBP>