maybe i am wrong and please let me know if i am, but i would imagin that if there is zero hardware listed in input and output settings i would think that checking if it is muted would not be the correct direction. my thinking is, if there is no hardware listed then what is there to mute?
i would first like to know why zero hardware is listed as in how and why does this happen with a fresh install? then how to get that hardware listed…
Strangely, yes; Some computers have a key built in to fn Mute the sound and in some cases, this causes Linux to not detect it until it is unmuted. A hardware mute is a bit different from a software mute with some manufacturers.
You can read more as well as a slew of other troubleshooting ideas here (I am assuming you are using Zorin Core or Ultimate):
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; auto-connect-localhost = no
; auto-connect-display = no
rm -r ~/.pulse
rm: cannot remove ‘/home/xxxxxxxxx/.pulse’: No such file or directory
rm -r ~/.pulse-cookie
rm: cannot remove ‘/home/leverage/.pulse-cookie’: No such file or directory
rm -r ~/.config/pulse
that command seemed to work
sudo pulseaudio -k
E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied
E: [pulseaudio] main.c: Failed to kill daemon: No such file or directory
Are you the original installer? Are you using a separate user account from the administrative account that installed Zorin?
What we are seeing here ^ above is a permissions issue that is causing Pulseadio to fail to start (therefor, no detected hw, no sound - it cannot access dbus).
Everything else that you posted looked like the files and settings were correct- However, a pulse cookie and file should have been removable by having existed- which they did not as Pulseaudio has never started.
hello,
yes i am the original installer and yes this is the administrative account from the install…
so what is next? just so you know this is a fresh install with out any monkey buisness aka messing around…
In that case, let's assign the permissions, then see if you can start the paulseaudio server. When you set up Zorin, you created a $USER account that you named. For example: let's say you named it lev.
You would enter the following command in terminal:
$ sudo pulseaudio -k
E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied
E: [pulseaudio] main.c: Failed to kill daemon: No such file or directory
Assuming that "lev" was your proper user name- did you get any errors on that at all?
Also- sorry I am a little slow today- You should try Logging out then logging in after changing permissions and then testing pulseaudio.
You understand, I needed to be sure... if you did a chown command for a username that is not yours, it would do you no good at all...
I edited the following in above - I am reposting here just to be sure: