On Fri, 01.01.10 16:58, Bill Cox (waywardg...@gmail.com) wrote:
However, even with these changes, there are bugs due to pulseaudio's
user-based structure. Today, in Karmic, if I 'switch user' to another
use, my new gnome session has no sound. That's because there are two
pulseaudio
Le 01/01/2010 22:58, Bill Cox a écrit :
Are there any ways to get pulseaudio to share the sound card?
http://git.0pointer.de/?p=pulseaudio.git;a=blob;f=src/modules/module-console-kit.c;hb=HEAD
PA hooks into ConsoleKit and turns itself off when the active user
changes. So yes, the daemon is
'Twas brillig, and Bill Cox at 01/01/10 21:58 did gyre and gimble:
However, even with these changes, there are bugs due to pulseaudio's
user-based structure. Today, in Karmic, if I 'switch user' to another
use, my new gnome session has no sound. That's because there are two
pulseaudio
'Twas brillig, and Markus Rechberger at 02/01/10 01:56 did gyre and gimble:
Can you point out to a few requests where people had serious issues
with shared audio access during the last 10 years, other unix systems
get along quite fine with shared support. The hacking argument is just
nonsense,
Hi, Colin. Here's what I'm thinking of doing. I think PulseAudio
should support the concept of a global sound source attached to a
card, and whichever pulseaudio system has rights to use the card
should be responsPible for processing the global source. Any
pulseaudio client could declare
Hi, Colin. Sorry about always replying at the top. This is the usual
custom for the blind, as they can't easily skip down to the new stuff.
I'd prefer not to write new PA modules for each accessibility driver.
I think it's very important to make it as easy as possible for
existing accessibility
'Twas brillig, and Bill Cox at 02/01/10 16:04 did gyre and gimble:
Hi, Colin. Sorry about always replying at the top. This is the usual
custom for the blind, as they can't easily skip down to the new stuff.
No problem, exception to bottom posting duely noted :)
I'd prefer not to write new
Thanks, Colin. I can probably modify speech-dispatcher and
speechdup-d to run as gdm on boot. I can probably also modify gdm
code to look for speech-dispatcher and speechd-up as well, and
relaunch them. It definately feels weird mucking about with the login
package, though.
However, even with
On Fri, Jan 1, 2010 at 4:58 PM, Bill Cox waywardg...@gmail.com wrote:
However, even with these changes, there are bugs due to pulseaudio's
user-based structure. Today, in Karmic, if I 'switch user' to another
use, my new gnome session has no sound. That's because there are two
pulseaudio
No, the problem happens when I switch to a new user.
On Fri, Jan 1, 2010 at 5:08 PM, Daniel Chen seven.st...@gmail.com wrote:
On Fri, Jan 1, 2010 at 4:58 PM, Bill Cox waywardg...@gmail.com wrote:
However, even with these changes, there are bugs due to pulseaudio's
user-based structure. Today,
pe, 2010-01-01 kello 16:58 -0500, Bill Cox kirjoitti:
Anyone out there every get hacked because you shared the Alsa back-end
with another user? Anyone?
I don't think anyone is going to get hacked because of this - it's
rather rare that you say your passwords aloud. Instead of hacking issue,
On Sat, Jan 2, 2010 at 2:21 AM, Tanu Kaskinen ta...@iki.fi wrote:
pe, 2010-01-01 kello 16:58 -0500, Bill Cox kirjoitti:
Anyone out there every get hacked because you shared the Alsa back-end
with another user? Anyone?
I don't think anyone is going to get hacked because of this - it's
rather
la, 2010-01-02 kello 02:56 +0100, Markus Rechberger kirjoitti:
On Sat, Jan 2, 2010 at 2:21 AM, Tanu Kaskinen ta...@iki.fi wrote:
pe, 2010-01-01 kello 16:58 -0500, Bill Cox kirjoitti:
Anyone out there every get hacked because you shared the Alsa back-end
with another user? Anyone?
I
I am trying to get Ubuntu/Lucid working well with applications for the
blind and visually impaired. Orca is working quite well now with
pulseaudio. The other critical application is speakup, which reads
text on the Ctrl+Alt+F1-6 consoles. Speakup has issues with
pulseaudio, and I need some
I was able to get to a semi-good state by not having pulseaudio
autospawn in /etc/pulse/client.conf. The computer comes up silent
until I log into gnome, and Orca works. When I switch to a console,
it's silent until I log in and restart speechd-up.
The problem is that there is no audio at the
'Twas brillig, and Bill Cox at 31/12/09 16:07 did gyre and gimble:
The problem is that there is no audio at the console until I log in.
There is also no audio at the gnome login. Grr...
AFAIK, the GDM login relies on autospawning, so turing off auto spawning
will result in no sound at gdm
Thanks for the info. Is there a simple way to kill off the gdm
pulseaduio when the user logs in? Some sort of hook I can tie into?
Thanks,
Bill
On Thu, Dec 31, 2009 at 11:26 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 31/12/09 16:07 did gyre and gimble:
The
'Twas brillig, and Bill Cox at 31/12/09 17:13 did gyre and gimble:
Thanks for the info. Is there a simple way to kill off the gdm
pulseaduio when the user logs in? Some sort of hook I can tie into?
It should all happen automatically: console-kit will hand over the
active session to the user
18 matches
Mail list logo
