What patch or other do I need to always keep the alsa headphone jack active. If I switch user and return, the headphone jack signal is muted.

I need it on full time. Currently I enable it with
A mixer -c0 set Headphone unmute 100%

See if you have alsamixer installed, set & save settings, hopefully will work for you.

If it worked for me (switch user, and return to myself), I would not post a question.

If you know how to have amixer Headphone jack permenantly unmuted and on, it would be helping me out.

just put it somewhere where it will be run at boot

# alsactl store

Which saves the mixer settings, and should be restored by default at boot. It depends on the distro ofc. Implies root to save it for all users. Although priorities vary depending on setups. BITD debian would check for alsa's settings, then use aumix-ers settings if they didn't exist. Pulseaudio (pavucontrol) might be the route these days. For some chipsets the headphone setting is ONLY available with alsamixer, so that's a good starting point.

Alsamixer wouldn't save my settings (both the headphone and mic were muted) for the first three days after I installed F22. Maybe it was an update, but now the settings are saved on exit. You may just want to try it again to see if anything's changed.

Then why not put that in your start up config, depending on your distro as to where & which file.

Here is the situation

Within /etc/profile.d/leslie.settings I have set

amixer -c0 set Headphone unmute 100 >/dev/null 2>&1

along with some other settings for other applications.

When I log into the system, amixer is correctly setup. (its the global profile setup for all users)

When I invoke Gnome's "switch user", amixer is muted, as it should be.

When I return from "switch user" amixer is not re-established.

So, the question I have is, On a return from "switch user", what are the names of the scripts that are activated?
For example, the profile scripts (.bash_rc /etc/bashrc and contents of /etc/profile.d are not called). What is the name of the script that decides that logic operation? I want to add a line to that script to re-initialize amixer.

I wonder if this question should be cross posted?

With that setup you probably have to logout and login to have those settings take effect and otherwise get re-applied. When you switch to a user who's already logged on, that's probably not happening. Or something like that.

I tend to have scripts that I run as the user that I am. Which is mostly manual for me, but it can be automated in .bashrc and other places. My tendancy towards scripts is that when I move on to another install I can just copy all my scripts, instead of trying to remember what configurations I changed from defaults times however many customizations I did. And I can tarball them and netcat them across computers on the local network without doing much in terms of "extras".

So...

Can you or anyone
tell me the name of a script that is called when I first log into the system, and the name of the script when I return from a switch user, or when I enter virtual terminal mode, and then return to Gnome

as per "Shadow_7" said there is only 2 reasons that can cause a muted anything is when alsa starts up it reads the aslactl store setting and sets them there. so set that. after that it is up to you to learn your tools and how to auto-start programs per operating systems.

As for the second reason you may have a setup in your .asoundrc that can cause that. good luck.

its a GDM thing
i guess you use GDM
ask them and if there isn't, file a bug report

I have learned to have the amixer restarted via my .bash_profile, and via /etc/profile.d/leslie.sh

And when I return from a switch user, I just open a terminal and close it again to restore amixer.

I did notice the following.

The .bash_profile script must finish before amixer is setup because of timings. Therefore.. I have a amixer.sh script that I call from the .bash_profile.
The amixer.sh script is a task, amixer.sh & and within amixer.sh is a 1 second sleep command followed by the amixer -c0 ......

My hardware does not have jack/in /jack out detection for the front headphone jack. (pc is circa 2010). Newer PCs do have it, and that would solve my problem.

I can't see myself buying a new PC, so I will live with what I have for now.