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