From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup and beeping constantly...
Date: Wed, 27 Dec 2006 12:58:14 -0700 [thread overview]
Message-ID: <20061227195814.GA8224@localhost.localdomain> (raw)
In-Reply-To: <000f01c729e2$37a4e690$6401a8c0@YOUR3ADE1B78A3>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The reason it does that is because you're apparently running a kernel
with a version of speakup which contained that bug, or maybe I should
call it an unintended feature (smile). Your only solution is to get a
kernel with the latest version of speakup, which fixes the
problem. Someone here a while ago wrote about a way to get around the
beeping bug, but that was back when there was no newer version of
speakup.
Greg
On Wed, Dec 27, 2006 at 11:09:57AM -0700, Keith Hinton wrote:
> Does anyone here know why Speakup beeps all the time when errowing around, backspacing (not just at the shel) but in every program I use?
> How could I quickly turn this off without patching it? Thanks.
>
> Regards, --Keith.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFktBW7s9z/XlyUyARAkoEAKC6r4+ZobxHkwEgLCZ29FPDcIjTPACgyM5c
LFjqN2rqpQx2WgVJZGGOupo=
=Luwu
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Gregory Nowak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061227195814.GA8224@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).