@vanvugt: there's nothing in /var/crash from pulseaudio, and as noted above, pulse is started in non-daemon mode by Ubuntu. so it's running, but apps can't seem to talk to it. probably because of the failure to start the socket service, as noted above. without the socket, and without it being a daemon, I don't think there's any way for apps to actually reach pulse.
Killing pulse works fine, but it just respawns in the same broken state: $ ps axf | grep pulse 20761 pts/0 S+ 0:00 | | \_ grep --color=auto pulse 15659 ? S<sl 0:00 \_ /usr/bin/pulseaudio --daemonize=no $ pacmd list No PulseAudio daemon running, or not running as session daemon. $ killall -ABRT pulseaudio $ ps axf | grep pulse 22402 pts/0 S+ 0:00 | | \_ grep --color=auto pulse 22248 ? S<sl 0:00 \_ /usr/bin/pulseaudio --daemonize=no $ pacmd list No PulseAudio daemon running, or not running as session daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
