We're sorry but we don't have the manpower to deal with hardware support problems.
Those problems need to be fixed in the upstream Linux kernel. We regularly import new kernel releases.

Don't buy hardware from suppliers who don't care about their Linux support.

Hi
I used my laptop for more than 7 years and I always used backtrack and kali without problems. My audio stopped to work after I upgraded to Kali 2018.3
In my opinion is not a hardware problem (because I see my audio device) but a pulseaudio/alsa conf problem.
I'm trying to purge pulseaudio but I'm unable to to this without removing other core packages:

The following packages will be REMOVED:
gnome-core gqrx-sdr kali-desktop-gnome libcanberra-pulse pulseaudio pulseaudio-module-bluetooth

Please let me know, thank you

The hardware is certainly not a fault, but it might be kernel driver regression, a problem in pulseaudio, or whatever else.

Unfortunately, we are not the upstream developers of the kernel and of pulseaudio and we don't have the resources to investigate the problem for you. We can handle bug reports that pin-point a problem that we introduced or apply some upstream patches that advanced users have found.

Your request is outside of what we can handle, sorry.

I think it's not a kernel regression bug.
I was able to play audio as root user only doing this:

pulseaudio --kill; pulseaudio --start (as no root user)
mplayer file.mp3 (as root)

When instead I tried to play audio as a no root user I got:

Audio device got stuck! (and no sound)

I followed a partial solution that I found for another Kali audio bug: https://bugs.kali.org/view.php?id=4384 and I got audio also for no-root users:

pulseaudio --kill; pulseaudio -D

So basically you have to restart pulseaudio. pulseaudio is correctly auto-started for root and for non-root.

It doesn't change much from my point of view. We haven't made any change at the pulseaudio level, so either it's a pulseaudio bug or it's a kernel bug (which can be worked-around by restarting pulseaudio).

Now if you really want to go further, you should try to see if rebooting with the former kernel helps. Or if downgrading pulseaudio to a former version helps. Your logs in /var/log/apt should help you to find out what got upgraded and what were the versions before.

No further information has been provided. There's nothing we can do about this issue.