On Fri, Nov 23, 2012 at 10:29:47AM +0100, Samuel Thibault wrote:
> > Still could not make gdm3 speak
>
> That's a bug, see
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689559
Yes. Thanks.
Cheers,
Dan
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a s
Daniel Dalton, le Fri 23 Nov 2012 16:15:13 +1100, a écrit :
> On Fri, Nov 23, 2012 at 02:54:41PM +1100, Daniel Dalton wrote:
> > I can no longer access universal accessibility settings either, from the
> > accessibility menu in the top panel.
>
> Redundant now, after reinstalling gnome this works
On Fri, Nov 23, 2012 at 02:54:41PM +1100, Daniel Dalton wrote:
> I can no longer access universal accessibility settings either, from the
> accessibility menu in the top panel.
Redundant now, after reinstalling gnome this works ok.
Still could not make gdm3 speak - perhaps I need to follow your
On Fri, Nov 23, 2012 at 02:41:28AM +0100, Samuel Thibault wrote:
> Daniel Dalton, le Mon 19 Nov 2012 15:50:25 +1100, a écrit :
> > 1. I've followed the instructions here:
> > http://wiki.debian.org/accessibility
> > However, I stil do not get orca coming up at start up. gdm3
> > automatically logs
Daniel Dalton, le Mon 19 Nov 2012 15:50:25 +1100, a écrit :
> 1. I've followed the instructions here:
> http://wiki.debian.org/accessibility
> However, I stil do not get orca coming up at start up. gdm3
> automatically logs me in, but I did run the commands to start
> accessibility and visual acces
Daniel Dalton wrote:
> /etc/asound.conf, actually, sorry my mistake, but I guess you probably
> knew anyway.
Yes.
>
> Seems removing that file for me had no effect, and if anything things
> work marginally better, but I still have pretty much the same problems,
> sigh.
That's unfortunate. I
On Wed, Nov 21, 2012 at 03:26:02PM +1100, Jason White wrote:
> Daniel Dalton wrote:
>
> > Hmm, how does your /etc/asound file look, or ~/.asoundrc file?
>
> There is no /etc/asound file and ~/.asoundrc no longer exists - I deleted it
> after PulseAudio was installed because I no longer needed
Daniel Dalton wrote:
> Hmm, how does your /etc/asound file look, or ~/.asoundrc file?
There is no /etc/asound file and ~/.asoundrc no longer exists - I deleted it
after PulseAudio was installed because I no longer needed the Alsa mixer
configuration that I had put in there.
--
To UNSUBSCRIB
On Wed, Nov 21, 2012 at 01:25:53PM +1100, Jason White wrote:
> Daniel Dalton wrote:
>
> > This bug is still present, and is now extended to speakup which also
> > crashes.
> > eSpeakup is crashing every 30 seconds to the point where it is almost
> > unusable.
>
> I tried it on my laptop and
Daniel Dalton wrote:
> This bug is still present, and is now extended to speakup which also
> crashes.
> eSpeakup is crashing every 30 seconds to the point where it is almost
> unusable.
I tried it on my laptop and it all works fine here with PulseAudio installed -
no words are being broken
On Tue, Nov 20, 2012 at 08:56:01PM +1100, Daniel Dalton wrote:
> This works alright, but I have some remaining problems.
> 1. Applications as root do not work. This means I can not use speakup
> (via espeakup) and brltty sounds do not play.
> Jason, do you run your pulseaudio in system-mode? I di
On Tue, Nov 20, 2012 at 06:19:54PM +1100, Jason White wrote:
> Daniel Dalton wrote:
> > Hmm, sounds like a bit of a tricky one which might require a bit more
> > research into it from me. Is there any disadvantage to use alsa for now?
>
> No, other than the Speech-Dispatcher bug that ought to be
Daniel Dalton wrote:
> Hmm, sounds like a bit of a tricky one which might require a bit more
> research into it from me. Is there any disadvantage to use alsa for now?
No, other than the Speech-Dispatcher bug that ought to be fixed anyway
(assuming that you don't need PulseAudio features such as
Hmm, sounds like a bit of a tricky one which might require a bit more
research into it from me. Is there any disadvantage to use alsa for now?
I get some alsa pcm errors at boot up but that's about the only problems
currently.
Cheers,
Dan
On Tue, Nov 20, 2012 at 08:57:28AM +1100, Jason White wro
Daniel Dalton wrote:
> On Mon, Nov 19, 2012 at 08:27:47PM +1100, Jason White wrote:
> > I'm using PulseAudio under Gnome, hence not seeing the bug.
>
> How to use pulseaudio without everything else breaking?
> I install it just now and although speech-dispatcher works ok with
> pulse, everything
On Mon, Nov 19, 2012 at 08:27:47PM +1100, Jason White wrote:
> I'm using PulseAudio under Gnome, hence not seeing the bug.
How to use pulseaudio without everything else breaking?
I install it just now and although speech-dispatcher works ok with
pulse, everything else is broken due to the device
Daniel Dalton wrote:
> Perhaps as Jason suggested I will contact the speech-dispatcher list.
That's a good idea, and if you can install the speech-dispatcher-dbg package
and obtain a backtrace from a core file, this should help to identify the
cause.
I'm using PulseAudio under Gnome, hence no
Daniel Dalton wrote:
> It doesn't look particularly good to me. Anyway doing what you said
> works, but in the process I've found another issue - I can't use the
> universal accessibility settings.
You should be able to use gsetting from the shell to change the configuration
however. I can't r
On Mon, Nov 19, 2012 at 12:37:55AM -0500, Trevor Saunders wrote:
> > 2. occasionally speech-dispatcher will crash. This requires the
> > speech-dispatcher and orca instance to be killed and orca restarted.
> > I couldn't find anything in the /var/log/speech-dispatcher dir, but I
> > only found thi
On Mon, Nov 19, 2012 at 04:27:39PM +1100, Jason White wrote:
> Daniel Dalton wrote:
>
> > 1. I've followed the instructions here:
> > http://wiki.debian.org/accessibility
> > However, I stil do not get orca coming up at start up. gdm3
> > automatically logs me in, but I did run the commands to s
On Mon, Nov 19, 2012 at 04:45:45PM +1100, Jason White wrote:
> Trevor Saunders wrote:
>
> > There's a known issue with alsa audio playback code in speech
> > dispatcher that this sounds like.
>
> Is there a patch that could be submitted for Debian Wheezy?
afaik nobody has tried to fix it :(
Trevor Saunders wrote:
> There's a known issue with alsa audio playback code in speech
> dispatcher that this sounds like.
Is there a patch that could be submitted for Debian Wheezy?
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe".
> 2. occasionally speech-dispatcher will crash. This requires the
> speech-dispatcher and orca instance to be killed and orca restarted.
> I couldn't find anything in the /var/log/speech-dispatcher dir, but I
> only found this relevant line from my syslog:
> 15:10:26 debian-laptop kernel: [ 224.8
Daniel Dalton wrote:
> 1. I've followed the instructions here:
> http://wiki.debian.org/accessibility
> However, I stil do not get orca coming up at start up. gdm3
> automatically logs me in, but I did run the commands to start
> accessibility and visual accessibility both from gdm and at the us
Hi,
I'm experiencing some problems with orca and speech dispatcher. I'm
running debian wheezy and gnome 3. I'm just using orca out of the apt
repository.
Also, I'm using gnome in fallback mode currently as it seems a little
more accessible to me.
1. I've followed the instructions here:
http://
25 matches
Mail list logo
