~Toughbooktalk~

Wow, a lot been going on in the thread while I have been dealing with work related to the storm, and the miscreants that come show up after the blow. I have been just resetting Alsamixer each time, and that is a bit kludged. Thanks for all your efforts! And Jeff, you are correct there are a HUGE number of people on the whole net that are having this same problem!

Azrial wrote:Wow, a lot been going on in the thread while I have been dealing with work related to the storm, and the miscreants that come show up after the blow. I have been just resetting Alsamixer each time, and that is a bit kludged. Thanks for all your efforts! And Jeff, you are correct there are a HUGE number of people on the whole net that are having this same problem!

Jeff alludes to having found a solution. He's just keeping the suspense going as we're waiting for his report on what ended up working, if such is the case.

I deleted pulse audio...............then found a couple more things to look at.

I'm sure this is a typo/bad command in Ubuntu somewhere....trust me I've looked. I needed to reload Mint and try from scratch before committing.

My start-up file works, alsamixer is hacked but it resets to headset mute when Firefox or Google is launched. That's when I scrapped pulse audio.

It's probably cleaner to disable Pulse Audio (rather than deleting) Trying that on fresh install next.

How commenting out or erasing the in then restart pulse or reboot...

Didn't seem to help. Tried it several times.

Disabling Pulse is work intensive. As I run XFCE things like visible volume control disappear. Tinkering.

I'm ready to scrap this until we find out what Ubuntu 16.04 did. I'll tinker with it from time to time but I would rather unload hay or clean the barn.

Pulseaudio from day 1 has caused me and my friends a lot of grief as it sneaked in through a dist-upgrade in Debian Wheezy and caused all audio to stop working. It seems a bit better now. Just a bit. Now it's hard to get rid of when a lot of useful applications depend on it.

I've resorted to terminal alsamixer and cranking the Headset volume up with UP arrow.

I'll abide by Azrial's warning and avoid Ubuntu 16.04 in whatever flavor.

I wondered if cinnamon would make a difference...so far no.

Meanwhile I run MX-14 on my CF-53's.

Disabling pulse worked but it keeps trying to sneak back in there.

What's your take on "esound"? Some older "fixes" recommended installing esound if pulse was deleted/disabled.

I need a "working" Linux for my spouse. 32 bit necessary for "Webex" (they say) She is ready to try Linux. W7 finally made her mad.

"Working Linux"
Na....I will just let it go.....................

Sadlmkr wrote: What's your take on "esound"? Some older "fixes" recommended installing esound if pulse was deleted/disabled.

Never used it myself so I know very little about it, but there is support for it all the way upstream Debian.

I'm ignoring this subject for now. Needed the hdd for another project.