Hey Daniel, I attached the log that you requested. "it" did mean pulseaudio, as your assumption guessed. As a heads up, I disabled pulseaudio from automatically starting, so that I wouldn't be trying to have multiple pulseaudio sessions open at once.
** Attachment added: "currentboot.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+attachment/5204020/+files/currentboot.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1798712 Title: [System76 Oryx Pro] No sound (18.10 Cosmic) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-vvvv`, here's what happens: `~$ pulseaudio -vvvv I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp