[pulseaudio-discuss] Sound Volume Setting At Login
tanu.kaskinen at linux.intel.com
Tue Nov 5 15:23:37 CET 2013
On Sat, 2013-11-02 at 16:57 -0400, Mark LaPierre wrote:
> On 10/25/2013 07:19 AM, Arun Raghavan wrote:
> > On Mon, 2013-10-14 at 19:23 -0400, Mark LaPierre wrote:
> >> On 10/12/2013 07:37 PM, Mark LaPierre wrote:
> >>> Hey all,
> >>> When I log on my sound level is set at about 35%. I have to use the
> >>> sound preferences to turn the sound level up every time I log in.
> >>> Other users on this same system do not have this issue. When they log
> >>> in their volume is set at 100%.
> >>> This leads me to believe that there must be something in my local
> >>> settings that is turning down my sound volume settings.
> >>> Does anyone have a clue were the config file might be that is causing
> >>> this to happen to me and not to others? Maybe it's not located in my
> >>> home because I've searched for it but I've come up empty.
> >> It has occured to me that I didn't include any information about my
> >> system. Maybe this will help one of you to find an answer to my problem.
> >> CentOS release 6.4 (Final)
> >> Linux mushroom.patch 2.6.32-358.18.1.el6.i686 #1 SMP Wed Aug 28 14:27:42
> >> UTC 2013 i686 i686 i386 GNU/Linux
> >> [mlapier at mushroom ~]$ rpm -qa | grep -i pulse
> >> alsa-plugins-pulseaudio-1.0.21-3.el6.i686
> >> pulseaudio-utils-0.9.21-14.el6_3.i686
> >> pulseaudio-module-x11-0.9.21-14.el6_3.i686
> >> pulseaudio-libs-zeroconf-0.9.21-14.el6_3.i686
> >> pulseaudio-libs-0.9.21-14.el6_3.i686
> >> pulseaudio-module-gconf-0.9.21-14.el6_3.i686
> >> pulseaudio-libs-devel-0.9.21-14.el6_3.i686
> >> pulseaudio-gdm-hooks-0.9.21-14.el6_3.i686
> >> pulseaudio-libs-glib2-0.9.21-14.el6_3.i686
> >> pulseaudio-0.9.21-14.el6_3.i686
> >> [mlapier at mushroom ~]$
> > Wow, those are old versions of PulseAudio indeed. Don't suppose you can
> > move to something newer?
> > A few options:
> > 1. Enable verbose logging (log-level = debug in /etc/pulse/daemon.conf)
> > and see what is changing the volume
> > 2. Wipe out ~/.pulse (which will remove all your settings) and see if
> > that “fixes” it
> > -- Arun
> I tried the possible solutions suggested by Arun but the effort was not
> I tried to give it a file in my home,
> log-target = /home/mlapier/.pulse/log,
> but it was not happy with that. I left it at log-target = auto. Where
> does the log file live?
The "auto" target uses syslog, when pulseaudio is not run from an
interactive shell (otherwise "auto" uses stderr).
Syslog has the problem that it ignores debug level messages (at least on
some systems, I'd guess it's the default behaviour). Syslog can probably
be configured to not ignore them, but I don't know how to do that.
More information about the pulseaudio-discuss