public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Alexander Epaneshnikov <aarnaarn2@gmail.com>
To: Samuel Thibault <samuel.thibault@aquilenet.fr>
Cc: Janina Sajka <janina@rednote.net>,
	Kelly Prescott <kprescott@coolip.net>,
	speakup@linux-speakup.org,
	Alexander Epaneshnikov <alex19ep@archlinux.org>
Subject: Re: Archlinux Speakup problems after alsa package upgrade
Date: Fri, 20 Aug 2021 18:26:06 +0300	[thread overview]
Message-ID: <20210820152606.r5nznst2t5532th3@alex-pc> (raw)
In-Reply-To: <20210819205617.l76b7fxume3lrf67@begin>

On Thu, Aug 19, 2021 at 10:56:17PM +0200, Samuel Thibault wrote:
> Hello,
>
> As an additional datapoint: in Debian the upgrade of alsa-lib to 1.2.5.1
> disturbs the espeakup output. Not completely broken, but distorted
> enough that you'll rather reboot to get back normal speech. I could
> capture some warnings, reported on
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992537
> Hopefully they will have ideas.

don't know if it's helpful info. but on arch linux espeakup 0.90 works fine
with: alsa-lib 1.2.5.1-3, pcaudiolib 1.2-2  and espeak-ng 1.50-4

maybe espeakup or espeak-ng should be rebuilt?

> Samuel

--
Sincerely, Alexander

  parent reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kelly Prescott
     [not found] ` <20210609072927.3igbp7jvopq3c6f7@begin>
   ` Kelly Prescott
     ` Janina Sajka
     [not found]     ` <20210609110828.kpo76f2zmbixjran@begin>
       ` Kelly Prescott
         ` Janina Sajka
           ` Alexander Epaneshnikov
     [not found]             ` <YNMr0Pathc/mqx1L@rednote.net>
     [not found]               ` <20210819205617.l76b7fxume3lrf67@begin>
                 ` Alexander Epaneshnikov [this message]
                   ` Janina Sajka
     [not found]                   ` <20210820155212.rlj4addvh726cgbb@begin>
                     ` Janina Sajka
     [not found]                       ` <20210821121814.vbyw4vxysowqf7as@begin>
                         ` Janina Sajka
                           ` Didier Spaier
                             ` Janina Sajka
                               ` Didier Spaier
                                 ` Janina Sajka
     [not found]                           ` <20210821125234.onaxd4ccrrh5oiyq@begin>
                             ` Janina Sajka
               ` Now Fixed: " Janina Sajka
                 ` Jason White
                   ` Janina Sajka
                     ` Janina Sajka
                     ` Didier Spaier
                       ` Janina Sajka
                         ` Didier Spaier
                           ` Didier Spaier
                           ` Alexander Epaneshnikov
                             ` Janina Sajka
                               ` Alexander Epaneshnikov
                                 ` Janina Sajka
           ` captcha revisited, just a little Karen Lewellen
 ` Archlinux Speakup problems after alsa package upgrade Chris Brannon
   ` Kelly Prescott
     ` Jude DaShiell
       ` Jude DaShiell
     ` Chris Brannon

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=20210820152606.r5nznst2t5532th3@alex-pc \
    --to=aarnaarn2@gmail.com \
    --cc=alex19ep@archlinux.org \
    --cc=janina@rednote.net \
    --cc=kprescott@coolip.net \
    --cc=samuel.thibault@aquilenet.fr \
    --cc=speakup@linux-speakup.org \
    /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).