From: Steve Holmes <steve@holmesgrown.com>
To: speakup@braille.uwo.ca
Subject: Re: Speakup broken with kernel 3.4.x (ArchLinux users please read)
Date: Sun, 8 Jul 2012 10:19:53 -0700 [thread overview]
Message-ID: <20120708171953.GA2709@lnx3> (raw)
In-Reply-To: <284773AE-D8D3-453D-BF9D-83A50C39CC48@sunbeem.net>
Interesting thing here is if you use the laptop keys on any machine, the thing won't crash. I've had an updated Arch kernel on my laptop for several days now and had no idea there was anything wrong. But then I came home to my old desktop and started using the numpad keys and it kept crashing and I had no idea why. But I just tried doing a shifted caps lock on my laptop and it crashed there two. This is a serious regression and hope it can be fixed soon. Wonder how kernel devs broke this thing.
Thanks Chris for the suggested downgrade options; that can at least keep our heads above the water.
On Fri, Jun 22, 2012 at 06:49:59PM -0400, Austin Seraphin wrote:
> Hey I just had this exact problem. Thanks so much for posting this message. I guess I'll try downgrading. THis happens on Arch with Kernel 3.4.3.
>
> Austin Seraphin
> au@sunbeem.net
>
>
>
>
> On Jun 18, 2012, at 9:01 AM, Chris Brannon wrote:
>
> > Hi all,
> > It seems that Speakup is broken for the new 3.4.x kernels.
> > These are now in the core repository on ArchLinux. If you're running
> > Arch and you haven't upgraded, you might want to hold off on doing the
> > upgrade. Downgrading to a 3.3.x kernel might be an option for people
> > who have already been hit. Also, ArchLinux provides a package called
> > linux-lts. This is an older kernel. Currently, that package is at
> > version 3.0.4. So replacing linux with linux-lts might also be an
> > option for some.
> >
> > Anyway, here's the problem. As soon as you use one of the Speakup
> > review keys, the system locks up hard. This is even the case with
> > numpad 0.
> > I'm going to use git bisect to figure out which change causes the
> > problem. Hopefully, I (or someone) can write a patch in the next few
> > days.
> >
> > -- Chris
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Brannon
` William F. Acker WB2FLW +1 303 722 7209
` Austin Seraphin
` Steve Holmes [this message]
` Steve Holmes
` Janina Sajka
` acollins
` William F. Acker WB2FLW +1 303 722 7209
` Chris Brannon
` Steve Holmes
` Kyle
` Adam Myrow
` William F. Acker WB2FLW +1 303 722 7209
` Steve Holmes
` Kyle
` covici
` William F. Acker WB2FLW +1 303 722 7209
` John G. Heim
` Kyle
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=20120708171953.GA2709@lnx3 \
--to=steve@holmesgrown.com \
--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).