On Thu, May 23, 2013 5:45 pm, Janina Sajka wrote:
I didn't know you could do so many. I wonder what you then do with the
GUI. I don't know what pulse needs to work on a terminal like that. I have
gotten jackd working across several (6 or 7) VTs/ssh terms by using a
script to tie the dbus instance to each login. But they are all one user.
I know pa creates a pseudo alsa device for alsa enabled apps to connect to
and that may not need dbus, but I think apps connecting direct to PA, do
It sounds like you have at least 3 users, so system wide might work best.
Another option that may work just as well is to use "screen" just under
the screen reader. Screen (in case you haven't used it) allows multiple
ttys as well, but because it is only one app you only need one instance of
your screen reader. The tty's under it can be logged in either with ssh
root@localhost or sudo bash --login. They may be a root bash, but the
screen reader would work at the user level that screen is running at.
Actually, screen says it supports multi-users natively.
> Card 0 for Speakup with TTSynth and whatever incidental sound
It doesn't sound impossible... Using VTs just makes it harder :) I found
the best way was to get dbus going on one and save the environment (at
least the dbus parts to a file. Then have each new VT export that to their
environment as they were logged in. If you are doing a GUI, then use the
dbus stuff from there for any VTS logged in as the same user.
Linux-audio-user mailing list