On Tue, 05.01.10 01:04, Colin Guthrie (gm...@colin.guthr.ie) wrote:
I don't know if the getty system could launch a psuedo session itself so
that ck doesn't specifically need to be aware of idle status - it was
just my way of imagineering how I'd approach the problem which (by the
sounds
On Tue, Jan 5, 2010 at 8:01 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have discussed this with Kay now and he'd very much prefer to do
this with a proper idle session that some tool (maybe some wrapper
around the speakup daemon) registers in CK, instead of patching
udev-acl.
On Tue, 05.01.10 08:48, Bill Cox (waywardg...@gmail.com) wrote:
On Tue, Jan 5, 2010 at 8:01 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have discussed this with Kay now and he'd very much prefer to do
this with a proper idle session that some tool (maybe some wrapper
around
On Tue, Jan 5, 2010 at 9:19 AM, Lennart Poettering
lenn...@poettering.net wrote:
Yes, the speakup daemons need to be modified so that they can be run
as a normal user instead of root, and then can deal with devices (both
audio and those special speakup kernnel devices) being assigned and
taken
'Twas brillig, and Bill Cox at 05/01/10 15:12 did gyre and gimble:
I was wrong. What's going on is that PA does not launch automatically
when I login, and that had me confused. Sessions do seem to be
tracked, and it does seem to know which is active.
That's expected. PA will be launched as
On Tue, 05.01.10 10:12, Bill Cox (waywardg...@gmail.com) wrote:
The whole point of ConsoleKit is to follow who's logged in. Are you
suggesting that if you login on the console ck-list-sessions does not
list that session? If that's the case your really should have a word
with the Ubuntu
ma, 2010-01-04 kello 09:37 +, Colin Guthrie kirjoitti:
As for the next stage I'm not an expert on this but I think you can try
adding:
[Element IEC985 Optical Raw]
switch = mute
switch = mute makes the mixer element state follow pulseaudio's sink
mute state, and I don't think you meant
'Twas brillig, and Tanu Kaskinen at 04/01/10 14:26 did gyre and gimble:
ma, 2010-01-04 kello 09:37 +, Colin Guthrie kirjoitti:
As for the next stage I'm not an expert on this but I think you can try
adding:
[Element IEC985 Optical Raw]
switch = mute
switch = mute makes the mixer
'Twas brillig, and Daniel Chen at 04/01/10 15:04 did gyre and gimble:
On Mon, Jan 4, 2010 at 9:26 AM, Tanu Kaskinen ta...@iki.fi wrote:
switch = mute makes the mixer element state follow pulseaudio's sink
mute state, and I don't think you meant to do that. Use switch = off
to set the element
'Twas brillig, and Colin Guthrie at 04/01/10 15:33 did gyre and gimble:
'Twas brillig, and Daniel Chen at 04/01/10 15:04 did gyre and gimble:
On Mon, Jan 4, 2010 at 9:26 AM, Tanu Kaskinen ta...@iki.fi wrote:
switch = mute makes the mixer element state follow pulseaudio's sink
mute state, and I
On Mon, Jan 4, 2010 at 10:53 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
Actually is this safe to do - i.e. disabling it wholesale? Is it not
used for digital output in some capacity (e.g. if the user picks a
digital profile)? Or is it perfectly safe to just turn it off all the
time? I don't
On Fri, 01.01.10 22:25, Bill Cox (waywardg...@gmail.com) wrote:
On Thu, Dec 17, 2009 at 4:52 AM, Lennart Poettering
lenn...@poettering.net wrote:
I don't see why anyone would want to have audio when changing to root
for admin purposes. Playing music certainly does not fall under admin
On Fri, 01.01.10 22:42, Bill Cox (waywardg...@gmail.com) wrote:
On Wed, Dec 23, 2009 at 6:57 AM, Lennart Poettering
lenn...@poettering.net wrote:
And this is the problem because it works with alsa, simply add every
user you want to give audio access to the audio group and it worked.
On Fri, 01.01.10 23:13, Bill Cox (waywardg...@gmail.com) wrote:
On Wed, Dec 23, 2009 at 9:13 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Halim Sahin at 23/12/09 13:24 did gyre and gimble:
The Problem can be summarized in one sentence:
Pulseaudio currently breaks
On Fri, 01.01.10 23:50, Bill Cox (waywardg...@gmail.com) wrote:
On Fedora at least the screenreader runs as normal process in the gdm
pseudo-session which also happens to run a PA instance. So everything
should be fine here, and I am quite sure this is not only done on
Fedora this way but
On Sat, 02.01.10 16:52, Colin Guthrie (gm...@colin.guthr.ie) wrote:
I'm not quite sure how this works. When a speakup client wants access
to the sound card, it could request access at high priority, and then
plays it's sound. How would it hand back the sound card to the other
user and
'Twas brillig, and Daniel Chen at 04/01/10 17:03 did gyre and gimble:
On Mon, Jan 4, 2010 at 10:53 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
Actually is this safe to do - i.e. disabling it wholesale? Is it not
used for digital output in some capacity (e.g. if the user picks a
digital
Hi, Lennart. The blind run all sorts of GUI-driven applications like
Synaptic, from the System/Administration menu. Howeve, Orca makes
these applications accessible when things are working correctly. I
agree that we don't want people to login through gdm as root. They do
things like su to
'Twas brillig, and Lennart Poettering at 04/01/10 19:06 did gyre and gimble:
I agree.
and that adding hooks to consolekit (if they don't exist) and the
concept of an idle user are probably more practical long term
solutions.
idle user? By that you mean some pseudo user session that the
On Sat, 02.01.10 16:03, Bill Cox (waywardg...@gmail.com) wrote:
Hi, Col. I'm willing to try the aproach you suggest, but I'd like to
debate the implementation some more. If I understand correctly, I can
use CK to determine whenever the sound card permissions are moved to a
new user (which
On Mon, Jan 4, 2010 at 1:35 PM, Lennart Poettering
lenn...@poettering.net wrote:
I dont see why the speech tools should be handled in any way different
from the other acessibility tools we ship: in that they are part of
the session. While I am no accessibility expert I am kinda sure that
on
On Sun, 03.01.10 07:41, Bill Cox (waywardg...@gmail.com) wrote:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the /dev/softsynth device. I see no utility in having multiple copies
of it.
On Sun, 03.01.10 12:29, Gene Heskett (gene.hesk...@gmail.com) wrote:
So, in my simplistic and user-centric point-of-view, I wonder if
speechd-up accepts audio INPUTS? Perhaps it could act as a pulseaudio
sink, with the appropriate modules, of course. It starts before the user
logs in and only
'Twas brillig, and Bill Cox at 04/01/10 19:43 did gyre and gimble:
Colin and Luke have suggested using CK to deal with this, by killing
off speech-dispatcher and speechd-up when the user logs in through
gdm, and restarting it when they log out.
Note that I wasn't really suggesting that it was
On Sun, 03.01.10 21:26, Ng Oon-Ee (ngoo...@gmail.com) wrote:
On Sun, 2010-01-03 at 07:41 -0500, Bill Cox wrote:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the /dev/softsynth device. I see no
Hi, Lennart. I beg you to not work towards eliminating the consoles.
Speakup is not only popular, but easily installed as a module in
Ubuntu, with 'm-a a-i speakup-souce'. Even sighted users prefer to
have those consoles available when X goes nuts, and for the blind,
they need it whenever speech
On Sun, 03.01.10 14:21, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Ng Oon-Ee at 03/01/10 13:26 did gyre and gimble:
So, in my simplistic and user-centric point-of-view, I wonder if
speechd-up accepts audio INPUTS? Perhaps it could act as a pulseaudio
sink, with the
On Mon, Jan 4, 2010 at 2:26 PM, Lennart Poettering
lenn...@poettering.net wrote:
... an alternative could be to fix speakup to
simply watch CK and disable itself as long as long as somebody is
logged in.
Users need to be able to press Ctrl+Alt+F1 at any time and get to a
speeking console. It
On Sun, 03.01.10 16:34, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Bill Cox at 03/01/10 16:23 did gyre and gimble:
Speechd-up isn't the only root level sound source that's out there.
Espeakup is another alternative to speechd-up which is currently much
more popular,
'Twas brillig, and Bill Cox at 04/01/10 20:01 did gyre and gimble:
On Mon, Jan 4, 2010 at 2:26 PM, Lennart Poettering
lenn...@poettering.net wrote:
... an alternative could be to fix speakup to
simply watch CK and disable itself as long as long as somebody is
logged in.
Users need to be
On Mon, Jan 4, 2010 at 2:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Also, the sepakup device access should be handled by udev-acl as
well. That would probably require non-trivial patching in the speakup
tts daemon though.
I'm completely ignorant of udev-acl, but if this is the
On Mon, Jan 4, 2010 at 8:51 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 03.01.10 07:41, Bill Cox (waywardg...@gmail.com) wrote:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the
On Mon, 04.01.10 14:59, Bill Cox (waywardg...@gmail.com) wrote:
Hi, Lennart. I beg you to not work towards eliminating the consoles.
Speakup is not only popular, but easily installed as a module in
Ubuntu, with 'm-a a-i speakup-souce'.
It's not me who is setting the agenda here, its
On Mon, 04.01.10 19:36, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Lennart Poettering at 04/01/10 19:06 did gyre and gimble:
I agree.
and that adding hooks to consolekit (if they don't exist) and the
concept of an idle user are probably more practical long term
On Mon, 04.01.10 21:36, Markus Rechberger (mrechber...@gmail.com) wrote:
Why do you second-guess us, but not them?
In the long run device access for root wont work anyway, for example,
when you acre about more than ALSA kernel devices, such as bluetooth
or other stuff that might need
On Mon, 04.01.10 15:10, Bill Cox (waywardg...@gmail.com) wrote:
On Mon, Jan 4, 2010 at 2:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Also, the sepakup device access should be handled by udev-acl as
well. That would probably require non-trivial patching in the speakup
tts
On Mon, Jan 4, 2010 at 3:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Right. So why not fix orca and make everything work fine in Gnome? I
mean, lets fix things properly, not carry on with kludges.
I'm guessing you're and Emacs user. What's wrong with Vim? Why don't
we simply
On Mon, 04.01.10 14:21, Bill Cox (waywardg...@gmail.com) wrote:
Hi, Lennart. The blind run all sorts of GUI-driven applications like
Synaptic, from the System/Administration menu. Howeve, Orca makes
these applications accessible when things are working correctly. I
agree that we don't
On Mon, Jan 4, 2010 at 3:48 PM, Lennart Poettering
lenn...@poettering.net wrote:
The problem of course is that the tts daemon needs to watch this too
and not choke if the device access to that soft_synth device goes
away.
Ok, so I could modify both espeakup and speechd-up to use udev and
deal
On Mon, 04.01.10 15:52, Bill Cox (waywardg...@gmail.com) wrote:
On Mon, Jan 4, 2010 at 3:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Right. So why not fix orca and make everything work fine in Gnome? I
mean, lets fix things properly, not carry on with kludges.
I'm guessing
On Mon, 04.01.10 15:58, Bill Cox (waywardg...@gmail.com) wrote:
On Mon, Jan 4, 2010 at 3:48 PM, Lennart Poettering
lenn...@poettering.net wrote:
The problem of course is that the tts daemon needs to watch this too
and not choke if the device access to that soft_synth device goes
away.
On Mon, 04.01.10 19:56, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Bill Cox at 04/01/10 19:43 did gyre and gimble:
Colin and Luke have suggested using CK to deal with this, by killing
off speech-dispatcher and speechd-up when the user logs in through
gdm, and
On Mon, Jan 4, 2010 at 4:01 PM, Lennart Poettering
lenn...@poettering.net wrote:
If you feel the need to support multiple alternative solutions for the
same problem and effectively double your maintainance work you are
welcome to do so, but that's your choice, and hence it is *your* job
to
On Mon, Jan 4, 2010 at 4:03 PM, Lennart Poettering
lenn...@poettering.net wrote:
They wouldn't have to link to udev at all. As mentioned they should
simply use inotify() and access() to minitor devices access coming and
going on /dev/soft_synth.
Got it. That makes it clearer.
On Monday 04 January 2010, Tanu Kaskinen wrote:
ma, 2010-01-04 kello 09:37 +, Colin Guthrie kirjoitti:
As for the next stage I'm not an expert on this but I think you can try
adding:
[Element IEC985 Optical Raw]
switch = mute
switch = mute makes the mixer element state follow
'Twas brillig, and Lennart Poettering at 04/01/10 20:39 did gyre and gimble:
On Mon, 04.01.10 19:36, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Lennart Poettering at 04/01/10 19:06 did gyre and gimble:
I agree.
and that adding hooks to consolekit (if they don't exist)
On Sun, 2010-01-03 at 07:41 -0500, Bill Cox wrote:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the /dev/softsynth device. I see no utility in having multiple copies
of it. Speech-dispatcher opens an IP
'Twas brillig, and Bill Cox at 03/01/10 12:41 did gyre and gimble:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the /dev/softsynth device. I see no utility in having multiple copies
of it.
'Twas brillig, and Ng Oon-Ee at 03/01/10 13:26 did gyre and gimble:
So, in my simplistic and user-centric point-of-view, I wonder if
speechd-up accepts audio INPUTS? Perhaps it could act as a pulseaudio
sink, with the appropriate modules, of course. It starts before the user
logs in and only
Hi, Colin. I like your proposal, but I think I'd like to implement it
in two phases. I'd like to skip step 1 for now, and not deal wit CK,
but as you say, make speechd-up headless, and write the PA modules
you suggest to pipe sound from speechd-up. CK isn't working properly
with PA in Ubuntu
'Twas brillig, and Bill Cox at 03/01/10 16:23 did gyre and gimble:
Speechd-up isn't the only root level sound source that's out there.
Espeakup is another alternative to speechd-up which is currently much
more popular, but limited in that it can only use the espeak voice.
From the point of
Hi,
On So, Dez 27, 2009 at 01:34:46 +0100, Lennart Poettering wrote:
On Sat, 26.12.09 08:31, Halim Sahin (halim.sa...@freenet.de) wrote:
Lennart
I believe in his particular use-case he's concerned about the
screenreader prior to the DE starting up (boot messages and the
On Sunday 03 January 2010, Ng Oon-Ee wrote:
On Sun, 2010-01-03 at 07:41 -0500, Bill Cox wrote:
Hi, Colin. I disagree that speech-dispatcher and speechd-up are
broken and need to be fixed. speechd-up is a root daemon attached to
the /dev/softsynth device. I see no utility in having multiple
On Sun, Jan 3, 2010 at 12:39 PM, Halim Sahin halim.sa...@freenet.de wrote:
Here are my thoughts about pulse:
Ok This will my last post in this thread
I can put in a good word for Halim. He's been very helpful in the
last several weeks working out issues with Orca and the back end sound
I've removed gdm from my Lucid system, after Tony Sales
(founder/driver of Vinux) suggested it. I'm already feeling rather
attached to my gdm-less system. It now boots into a very nicely
talking console login prompt. I just login, do whatever I like on the
console, and type 'startx' if I want
On Sun, 2010-01-03 at 12:29 -0500, Gene Heskett wrote:
Regardless, this problem for the visually impaired is one that needs to be
addressed ASAP before we have a whole battalion of lawyers from the ACLU
challenging us all in courts that we don't, by the very nature of linux, have
the
On Sun, 2010-01-03 at 13:57 -0500, Bill Cox wrote:
I've removed gdm from my Lucid system, after Tony Sales
(founder/driver of Vinux) suggested it. I'm already feeling rather
attached to my gdm-less system. It now boots into a very nicely
talking console login prompt. I just login, do
'Twas brillig, and Gene Heskett at 03/01/10 17:48 did gyre and gimble:
And it seem like a doable, sane approach to the problem. A voice of sanity
midst the riot this could become.
:)
But that still leaves PA's biggest problem for this user: It picks the most
obviously wrong choice in
On Sunday 03 January 2010, Colin Guthrie wrote:
'Twas brillig, and Gene Heskett at 03/01/10 17:48 did gyre and gimble:
And it seem like a doable, sane approach to the problem. A voice of
sanity midst the riot this could become.
:)
:
But that still leaves PA's biggest problem for this user:
'Twas brillig, and Gene Heskett at 03/01/10 21:48 did gyre and gimble:
And yesm there are, according to the bus scanning done at bootup, 3 separate
audio systems in this machine.
1. There is an intel-hd or whatever its called, claim from my video card
that has no connection to the
On Sun, Jan 3, 2010 at 4:48 PM, Gene Heskett gene.hesk...@gmail.com wrote:
01:07.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
Subsystem: Creative Labs Device 1001
Flags: bus master, medium devsel, latency 32, IRQ 17
I/O ports at 9c00 [size=64]
On Sunday 03 January 2010, Ng Oon-Ee wrote:
On Sun, 2010-01-03 at 12:29 -0500, Gene Heskett wrote:
Regardless, this problem for the visually impaired is one that needs to
be addressed ASAP before we have a whole battalion of lawyers from the
ACLU challenging us all in courts that we don't, by
On Sunday 03 January 2010, Daniel Chen wrote:
On Sun, Jan 3, 2010 at 4:48 PM, Gene Heskett gene.hesk...@gmail.com wrote:
01:07.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
Subsystem: Creative Labs Device 1001
Flags: bus master, medium devsel, latency 32, IRQ
On Sun, Jan 03, 2010 at 01:08:07AM EST, Colin Guthrie wrote:
'Twas brillig, and Tanu Kaskinen at 02/01/10 05:59 did gyre and gimble:
So that's how I see it should work. I'm not very confident when speaking
about consolekit and boot/login processes, so I have to hope that the
system I
'Twas brillig, and Tanu Kaskinen at 02/01/10 05:59 did gyre and gimble:
So that's how I see it should work. I'm not very confident when speaking
about consolekit and boot/login processes, so I have to hope that the
system I described isn't too different from how things work in reality.
I think
Hi, Col. I'm willing to try the aproach you suggest, but I'd like to
debate the implementation some more. If I understand correctly, I can
use CK to determine whenever the sound card permissions are moved to a
new user (which is basically whenever a user takes over the seat,
except as root), and
This scheme sounds reasonable, though whenever someone says
impossible, I'm naturally inclined to give it a solid try. Why
would it be impossible to add PA hooks I could run when PA gains,
uncorks, corks, or delets a connection to a card? I thought I already
saw a system of hooks being called.
I spent a few hours trying to figure out how well this scheme could
work for Ubuntu/Lucid. Things are in bad shape. Speakup basically is
incompatible with PA on Lucid for now. The problems seem to come from
multiple PA instances not sharing properly. If you switch-user to a
new user on Karmic
Sorry... my laptop has a tendency to accidentally click, and I sent
that last e-mail unfinished.
Anyway, I don't believe I've evern seen multiple copies of PA running
in Ubuntu work properly together, and the open bug about this on
bugs.launchpad.net has had no progress or interest. If I write
(Answer to both Colin and Bill)
Colin Guthrie wrote:
'Twas brillig, and Bill Cox at 02/01/10 15:03 did gyre and gimble:
Hi, David.
On Sat, Jan 2, 2010 at 1:08 AM, David Henningsson
launchpad@epost.diwic.se wrote:
I was just thinking, and this idea is perhaps not 100% thought through,
On Thu, Dec 17, 2009 at 4:52 AM, Lennart Poettering
lenn...@poettering.net wrote:
I don't see why anyone would want to have audio when changing to root
for admin purposes. Playing music certainly does not fall under admin
purposes.
Ever consider what happens when a blind user switches to root,
On Wed, Dec 23, 2009 at 6:57 AM, Lennart Poettering
lenn...@poettering.net wrote:
And this is the problem because it works with alsa, simply add every
user you want to give audio access to the audio group and it worked.
Even with OSS this worked. But PA breaks this behaviour.
First of all, we
On Wed, Dec 23, 2009 at 9:13 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Halim Sahin at 23/12/09 13:24 did gyre and gimble:
The Problem can be summarized in one sentence:
Pulseaudio currently breaks multiuser systems and is only useful for
one-user-desktop.
Actually no,
On Thu, Dec 24, 2009 at 11:14 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 24/12/09 14:02 did gyre and gimble:
I think it's pretty clear what the problem is.
PA does not support multiple users on one system..
I told you if you intend to replace the
On Thu, Dec 24, 2009 at 11:29 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 23.12.09 15:26, Halim Sahin (halim.sa...@freenet.de) wrote:
Hi Col,
1. I gave you some examples what doesn't work as expected.
How should I run my text-to-speech server before login to have
On Thu, Dec 24, 2009 at 12:27 PM, Lennart Poettering
lenn...@poettering.net wrote:
We actually cover that inside of gdm, where you can get access to the
boot messages.
Lennart
Speakup doesn't stop reading when the user logs into Gnome. When we
type Ctrl+Alt+F1, we get a console screen which
On Fri, 2010-01-01 at 23:29 -0500, Bill Cox wrote:
On Thu, Dec 24, 2009 at 11:14 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 24/12/09 14:02 did gyre and gimble:
I think it's pretty clear what the problem is.
PA does not support multiple users on one
pe, 2010-01-01 kello 23:13 -0500, Bill Cox kirjoitti:
IMO, Halim's more important comment was that PulseAudio breaks
accessibility. Speakup is either the #1 or #2 most popular Linux
accessibility program for the blind and visually impaired. It starts
at boot, as it should, so a blind person
Bill Cox wrote:
On Thu, Dec 24, 2009 at 12:27 PM, Lennart Poettering
lenn...@poettering.net wrote:
We actually cover that inside of gdm, where you can get access to the
boot messages.
Lennart
Speakup doesn't stop reading when the user logs into Gnome. When we
type Ctrl+Alt+F1, we get a
On Sat, 26.12.09 18:03, Ng Oon-Ee (ngoo...@gmail.com) wrote:
I've been following these discussions with some (layman-level, I don't
dev for pulse) interest, and I'm wondering whether a simple solution
would be to use alsa-output prior to login and pulseaudio after login. A
bit of
On Sat, 2009-12-26 at 08:31 +0100, Halim Sahin wrote:
Hi,
On Do, Dez 24, 2009 at 06:27:25 +0100, Lennart Poettering wrote:
On Fri, 25.12.09 00:47, Ng Oon-Ee (ngoo...@gmail.com) wrote:
Running PA doesn't mean ALSA is out of the game. PA builds on ALSA and
as such everything you could
Hi,
On Do, Dez 24, 2009 at 06:27:25 +0100, Lennart Poettering wrote:
On Fri, 25.12.09 00:47, Ng Oon-Ee (ngoo...@gmail.com) wrote:
Running PA doesn't mean ALSA is out of the game. PA builds on ALSA and
as such everything you could do with ALSA before stays available with
PA too.
'Twas brillig, and Halim Sahin at 23/12/09 14:26 did gyre and gimble:
Hi Col,
1. I gave you some examples what doesn't work as expected.
How should I run my text-to-speech server before login to have
audiooutput for reading the login screen?
GDM runs under the gdm user and starts it's own
'Twas brillig, and Markus Rechberger at 23/12/09 14:35 did gyre and gimble:
On Wed, Dec 23, 2009 at 3:14 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 13:45 did gyre and gimble:
You're certainly good at ignoring bugreports your way, instead of
On Thu, Dec 24, 2009 at 1:29 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 14:35 did gyre and gimble:
On Wed, Dec 23, 2009 at 3:14 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 13:45 did gyre and
'Twas brillig, and Markus Rechberger at 24/12/09 12:43 did gyre and gimble:
On Thu, Dec 24, 2009 at 1:29 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 14:35 did gyre and gimble:
On Wed, Dec 23, 2009 at 3:14 PM, Colin Guthrie gm...@colin.guthr.ie
On Thu, Dec 24, 2009 at 2:50 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 24/12/09 12:43 did gyre and gimble:
On Thu, Dec 24, 2009 at 1:29 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 14:35 did gyre and
'Twas brillig, and Markus Rechberger at 24/12/09 14:02 did gyre and gimble:
I think it's pretty clear what the problem is.
PA does not support multiple users on one system..
I told you if you intend to replace the existing audio system and
build up compatibility layers
add try to do it right.
On Wed, 23.12.09 15:26, Halim Sahin (halim.sa...@freenet.de) wrote:
Hi Col,
1. I gave you some examples what doesn't work as expected.
How should I run my text-to-speech server before login to have
audiooutput for reading the login screen?
On Fedora at least the screenreader runs as normal
On Thu, 24.12.09 13:43, Markus Rechberger (mrechber...@gmail.com) wrote:
Heh. I think the issue is resolved.
apt-get remove pulseaudio is the preferred way to get audio work again.
I don't see the reason why someone should use a faulty audio system.
Alsa is working well enough for most
On Thu, 24.12.09 15:02, Markus Rechberger (mrechber...@gmail.com) wrote:
All I'm saying is do you expect us to trawl the internet and dig up
problems without any kind of technical detail or debug info attached to
them or do you think we should concentrate on answering and dealing with
On Fri, 25.12.09 00:47, Ng Oon-Ee (ngoo...@gmail.com) wrote:
Running PA doesn't mean ALSA is out of the game. PA builds on ALSA and
as such everything you could do with ALSA before stays available with
PA too.
However input output deamons should definitely be part of the user
On Tue, 22.12.09 17:54, Markus Rechberger (mrechber...@gmail.com) wrote:
Well, but nevertheless an X session is required to allow differend user
accounts to access the audio subsystem at the same time. This is a
drawback for me as I'm used to do a lot of my daily work on a text
console
On Wed, Dec 23, 2009 at 1:16 PM, Markus Rechberger
mrechber...@gmail.com wrote:
On Wed, Dec 23, 2009 at 12:57 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 22.12.09 17:54, Markus Rechberger (mrechber...@gmail.com) wrote:
Well, but nevertheless an X session is required to allow
On Wed, Dec 23, 2009 at 1:49 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 23.12.09 13:16, Markus Rechberger (mrechber...@gmail.com) wrote:
Right. It is innovative to carry on with the brokeness we always had
just because we always had it and not because we would ever think
'Twas brillig, and Halim Sahin at 23/12/09 13:24 did gyre and gimble:
The Problem can be summarized in one sentence:
Pulseaudio currently breaks multiuser systems and is only useful for
one-user-desktop.
Actually no, the exact opposite. PA works very well for multi user
desktops. The vast
'Twas brillig, and Markus Rechberger at 23/12/09 13:45 did gyre and gimble:
You're certainly good at ignoring bugreports your way, instead of
finding solutions
to fix it up.
Can you give links to these bug reports please?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Hi Col,
1. I gave you some examples what doesn't work as expected.
How should I run my text-to-speech server before login to have
audiooutput for reading the login screen?
2. Running daemons worked well under alsa (see my previous post).
I am using every day this setup.
Speechd runs with uid
On Wed, Dec 23, 2009 at 3:14 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 23/12/09 13:45 did gyre and gimble:
You're certainly good at ignoring bugreports your way, instead of
finding solutions
to fix it up.
Can you give links to these bug reports
On Thu, 26.11.09 01:27, David Csercsics (a...@shaw.ca) wrote:
On Thu, Nov 26, 2009 at 04:51:25PM +0800, Markus Rechberger wrote:
Hi,
I've been working quite a while with pulseaudio, one thing that breaks
alsa compatibility is that since PA is user based root is not allowed
to access
1 - 100 of 122 matches
Mail list logo
