hmmm. I tried that, but no dice for me. pulse starts in a terminal, but nothing in my session sees a sound device still. for the one started in a terminal, it doesn't respond to kill signals, and needs to be kill -9d.
I suspect the "/usr/bin/pulseaudio --daemonize=no" process is just grabbing the soundcard and so running the second one does nothing useful. running the X11 wrapper script errors out: $ start-pulseaudio-x11 Connection failure: Connection refused pa_context_connect() failed: Connection refused Given that pacmd explicitly complains about there being no daemon running, the fact that systemd is running pulseaudio with --daemonize=no is probably a bad thing. -- 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/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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
