Once again, my X has stopped from playing any alert sounds at all. It was working this morning, but has been silent for a few hours.

I've seen this in both the Official and Community builds.

Phone seems to work normally, I get audio in both normal and loudspeaker modes in a call. But no alert tones play. Trying to play an mp3 from the file manager is also silent, as is a video from LLsvPlayer.

Tried switching bluetooth off and on in case it was streaming to the car, also tried in and out of flight mode. Also switched ambiences with no effect.

Any of our wise cadre have any other things I can check before I reboot (which always brings it all back).

Not sure what processes I should be looking for or restarting from the console?

Have you changed ambience?

Maybe it's on silent

Tried that. I use a cron job that switches to silent ambience overnight and back in the morning, so that was the first thing I expected it to be.

I think ambiences stick over a reboot too, so rebooting wouldn't fix it, which it always does.

Did you try manually changing by using volume up button whilst on the homescreen? That happened to me once and that solved it.

Yep, I was wary of that after the horror that was ubuntu touch.
Tried setting maximum volume in every way and place I can find.

I haven't changed Ambience at all. This morning, the alarm on my Xperia made no noise. (I was woken by my Jolla, which was set for the same time.) I set a test alarm and it made noise. I wonder if it's related to waking the phone up from inactivity?

I tried settings->utilities->restart network subsystem with no effect.
Then tried settings->utilities->Restart Home screen and the phone crashed.
Once it rebooted, sounds were back as usual.

Lost all sounds again at some point this morning, despite having a cronjob that reboots the phone at 7am.

Could this be part of the X bluetooth problem ? (I received a call in the car on my morning journey, which worked fine) I've never seen it written precisely what the BT problems are in the X.

i had the same problem. it was causd by a system.system owned file in ~/.config/pulse preventing pulse from starting at all.

remedy was `rm /home/nemo/.config/pulse/*` and reboot

Thanks wolke, glad to know I'm not the only one to see this issue.
I didn't find the same thing though, all files in that folder owned by nemo:nemo.

However, it could have been fixed by the recent firmware update? It usually only happens to me a couple of times a month, so I will keep a check on it and report back if I have more problems.

(I deleted the files and let them be recreated just in case)