Michał Zegan <webczat_200@xxxxxxxxxxxxxx> writes: > Well, if you have pulseaudio installed and running per user, then I > doupt you can get sound working in console without any hacks, definitely > not before you log in to text mode. > In case of system wide pulseaudio you would be using a deprecated > configuration. Pulseaudio in system mode is not deprecated. However it isn't recommended by the pulseaudio devs. I ignore that recommendation. It works well, and it is perfectly performant. You can download my configuration from (https://the-brannons.com/pulse-config.tar.gz). I use that configuration on Void Linux. You may need to tweak it for other distros. You'll also have to enable the pulseaudio service in your init system. The multiseat / multiuser desktop stuff is for big institutional / corporate users. The vast majority of blind people tend to monopolize a Linux machine so it effectively just has one human user. I'm sure this is true of everyone running Linux et al on a laptop or desktop. All of the logind and swarm of per-user autospawning daemons stuff goes against the grain of Unix, as well as making a system unstable and unpredictable. The right way to share a Linux machine among multiple physical users is to have dedicated thin clients AKA X terminals that all have their own dedicated I/O hardware. espeakup and Speech Dispatcher can share a systemwide pulseaudio just fine, even with Speech Dispatcher running per-user. Speaking of Speech Dispatcher, I will be forking speechd-up soon, because it has been effectively unmaintained for years. Announcement forthcoming. Pipewire has a pulseaudio compatibility mode to ease adoption, so why is it particularly relevant here? -- Chris -- Chris Brannon Founder: Blind and Low Vision Unix Users Group (https://blvuug.org/). Personal website: (https://the-brannons.com/) Chat: IRC: teiresias on freenode, XMPP: chris@xxxxxxxxxxxxxxxxx
