[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190316093543.w4i6djt5uuqtx5xr@function>
Date: Sat, 16 Mar 2019 10:35:43 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Chris Brannon <chris@...-brannons.com>
Cc: Okash Khawaja <okash.khawaja@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
speakup@...ux-speakup.org, devel@...verdev.osuosl.org,
William Hubbs <w.d.hubbs@...il.com>,
Kirk Reiser <kirk@...sers.ca>, linux-kernel@...r.kernel.org
Subject: Re: Staging status of speakup
Chris Brannon, le ven. 15 mars 2019 18:19:39 -0700, a ecrit:
> Okash Khawaja <okash.khawaja@...il.com> writes:
> > Finally there is an issue where text in output buffer sometimes gets
> > garbled on SMP systems, but we can continue working on it after the
> > driver is moved out of staging, if that's okay. Basically we need a
> > reproducer of this issue.
>
> What kind of reproducer do you need here? It's straightforward to
> reproduce in casual use, at least with a software synthesizer.
The problem is that neither Okash nor I are even casual users of
speakup, so we need a walk-through of the kind of operation that
produces the issue. It does not have to be reproducible each time it is
done. Perhaps (I really don't know what that bug is about actually) it
is a matter of putting text in the selection buffer, and try to paste it
100 times, and once every 10 times it will be garbled, for instance.
Samuel
Powered by blists - more mailing lists