search for: pavu

Hi all, I hope someone could enlighten me... How could I resolve the fact that the volume controls of all the headphones I try on CentOS 7 are not working, they are OK on CentOS 6 but impossible to make them work on my Thinkpad Laptop with an iPhone headphones or a Marshal Monitor plugged with a jack connector... Those 2 headphones work correctly in CentOS 6... What could I do to get the same

...hone headphones or a Marshal Monitor plugged with a jack > connector... > Those 2 headphones work correctly in CentOS 6... > What could I do to get the same behavior on CentOS 7 and this damned > Gnome 3 ? > Thanks for your help... On Centos-7, some apps use PulseAudioVolumeControl (pavucontrol) instead of the one that defaults to the top panel. (I am running Mate, not Gnome--yuck--so YMMV). I wish there was a way to control all from a single place, but AFAICF there isn't. for some things I use the one on the top panel (which is Mate Volume Control) and for others I gotta star...

...shal Monitor plugged with a jack >> connector... >> Those 2 headphones work correctly in CentOS 6... >> What could I do to get the same behavior on CentOS 7 and this damned >> Gnome 3 ? >> Thanks for your help... > On Centos-7, some apps use PulseAudioVolumeControl (pavucontrol) > instead of the one that defaults to the top panel. (I am running > Mate, not Gnome--yuck--so YMMV). > > I wish there was a way to control all from a single place, but AFAICF > there isn't. for some things I use the one on the top panel (which is > Mate Volume Control...

...#39;s only 2 channels I'm not sure how to tell if those are ignorable fixmes or are part of the problem. I have checked through my graphic software management tool (yast) and could not find any parts of pulseaudio installed and I also checked by command line to remove anything pulse*.* and pavu*.* so I do not think there is a pulseaudio conflict lurking on the system. The machine is KDE by default and I have tried to keep it gnome free to avoid conflicts. Google searching showed a similar issue on the game forum which was fixed in windows by renaming the "userpreferences.ini&quot...