You're right; a SIGKILL will not leave any trace. However you also mentioned that happened when you ran it manually so I'm wondering if maybe a different crash is occurring when the daemon is started formally by the system. Hoping anyway.
We need to continue on the assumption that this is a debuggable crash and not caused by SIGKILL. So please complete the steps in comment #4. If you can then find no further information then unfortunately you're left to figure out what is killing the pulseaudio process. My first guess would be maybe the kernel OOM killer, if the system is low on memory. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1783200 Title: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working Status in pulseaudio package in Ubuntu: Incomplete Bug description: I believe this is a pulseaudio regression, as the output of alsa-info (http://www.alsa- project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine as far as I can see. I'm currently running Ubuntu 18.04, and I believe this is a regression as audio used to work under 17.10. Since upgrading (which fixed a good number of other incompatibilities with the machine), I've had no luck getting audio to work at all. I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and 'pulseaudio -vv'. If I can provide any other information, or if there's anything you'd like me to try, I'd be happy to help in any way possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
