Hi Jason,
On So, Dez 16, 2012 at 04:49:55 +1100, Jason White wrote:
> Do you still need it if you're running PulseAudio 2.1-2 from experimental?
Yes I see no difference.
I've tested in in my wheezy vm.
Regards
Halim
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with
Hello,
On So, Dez 16, 2012 at 04:41:46 +1100, Daniel Dalton wrote:
> Are you just using speechd-up with speakup, so that it can use
> speech-dispatcher? Or should espeakup actually work as well?
I use sbl at the textconsole.
Espeakup should work as well if it uses alsa in espeak (not sure). I am
Hi,
On So, Dez 16, 2012 at 04:49:55 +1100, Jason White wrote:
> I'm trying to work out why PulseAudio is not blocking the audio device on my
> laptop, even though I haven't changed the configuration from its defaults.
Maybe your audio hardware can mix several audiostreams in hardware?
Or they have
Halim Sahin wrote:
> - place the attached default.pa in ~/.pulse
> The changes are that pulseaudio can't block the audio device.
Thanks for this.
Do you still need it if you're running PulseAudio 2.1-2 from experimental?
I'm trying to work out why PulseAudio is not blocking the audio device on
On Fri, Dec 14, 2012 at 09:23:52PM +0100, Halim Sahin wrote:
> Hi,
> Unfortunately next stable debian' graphical desktop
> will highly depend on pulseaudio.
> aptitude show gnome-core
Certainly
>
> So here are some hints how to deal with this situation:
> - place the attached default.pa i
---
jude
Adobe fiend for failing to Flash
-- Forwarded message --
Date: Fri, 14 Dec 2012 15:23:52
From: Halim Sahin
To: debian-accessibility@lists.debian.org
Subject: hints for pulseaudio in wheezy
Hi,
Unfortunately next stable debian' graphical desktop
will highly depend on pulseaudio.
aptitude show gnome-core
So here are some hints how to deal with this situation:
- place the attached default.pa in ~/.pulse
The changes are that pulseaudio can't block the audio device.
- sudo rm /usr/
Hi. debian's installer with speakup and espeakup is still text only, so the
pulseaudio
problem doesn't happen. Pulseaudio only becomes a problem when you log into
gnome.
If the pulseaudio developer took accessibility issues caused by his app
seriously, then distros wouldn't have to find
work a
So pulseaudio operates in easy install at adequate volume and then goes
silent on boot up. Why couldn't some command be put into rc.local by
the easy install script if sound gets used to adjust pulseaudio's volume
to a proper level? It sounds like the developers of that package need
their hea
Hi. I have no problem fixing things when pulseaudio breaks it. My only reason
for starting this thread
was to get this finally addressed officially in Debian for new users. It won't
look good for Debian to have access to the installer only to loose
it when the new system reboots.
Ke
Kenny Hitt wrote:
> Thanks for the info. I posted to try to find a solution for new users.
> What will happen to someone who does a new Wheezy install? If the solution
> is to do like I did and remove it, can we find an easy way for a speech only
> user to do it without sighted help?
sudo apti
Hi.
On Thu, Sep 29, 2011 at 02:55:34PM +1000, Jason White wrote:
>
> aptitude hold pulseaudio
> should prevent it from being installed in the future. The documentation says
> that "hold" prevents upgrades, but it seems to prevent installation as well.
>
Thanks for the info. I posted to try to fi
Kenny Hitt wrote:
> Hi. My upgrade broke my access to my system again.
> As usual, the problem was pulseaudio. The pulseaudio upgrade added itself to
> my gnome session.
> The result was loss of speech with orca and espeakup.
> My solution was to killall -9 pulseaudio and purge pulseaudio from
Hi. My upgrade broke my access to my system again.
As usual, the problem was pulseaudio. The pulseaudio upgrade added itself to
my gnome session.
The result was loss of speech with orca and espeakup.
My solution was to killall -9 pulseaudio and purge pulseaudio from my system.
Although this fixe
14 matches
Mail list logo
