From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: befuddled.reisers.ca; dkim=pass (1024-bit key; unprotected) header.d=rednote.net header.i=@rednote.net header.a=rsa-sha256 header.s=dkim header.b=re3y9SmP; dkim-atps=neutral Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 050B6380B40; Tue, 28 Dec 2021 11:27:02 -0500 (EST) Received: from mail.rednote.net (opera.rednote.net [66.228.34.147]) by befuddled.reisers.ca (Postfix) with ESMTPS id 66556380331 for ; Tue, 28 Dec 2021 11:27:00 -0500 (EST) Received: from opera.rednote.net (localhost [IPv6:::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.rednote.net (Postfix) with ESMTPS id 240D6FA278; Tue, 28 Dec 2021 11:26:56 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rednote.net; s=dkim; t=1640708816; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8b1djYe/pY732bnG8foDmvYF4wXBrTWz+kdfLannDbo=; b=re3y9SmPYJHQLlaEY11Duc/BwCnpyeXXECW4MKlYEnF26w55q4U/6UNGmLDmIhjDVxYANl lqHHakDrh+9LHJ/U9Spco9tdQnowFLHD78qhEetFo/vgpQ08mjZalL4/23UojkKqaHqh0v VQ7gv1m6ITvVNCDmC+S4cbYUEq8D54I= DMARC-Filter: OpenDMARC Filter v1.4.1 mail.rednote.net 240D6FA278 Authentication-Results: mail.rednote.net; dmarc=pass (p=reject dis=none) header.from=rednote.net Authentication-Results: mail.rednote.net; spf=pass smtp.mailfrom=rednote.net Received: (from janina@localhost) by opera.rednote.net (8.17.1/8.16.1/Submit) id 1BSGQurB935925; Tue, 28 Dec 2021 11:26:56 -0500 Date: Tue, 28 Dec 2021 11:26:56 -0500 From: Janina Sajka To: Jason White Cc: speakup@linux-speakup.org Subject: Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade Message-ID: References: <20210609072927.3igbp7jvopq3c6f7@begin> <20210609110828.kpo76f2zmbixjran@begin> <6b4b229d-5e00-22e4-8cf2-33ed7bbd6b93@gmail.com> <3cefe3e6-f95a-ffe9-5995-543d6e4357db@jasonjgw.net> X-BeenThere: speakup@linux-speakup.org Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3cefe3e6-f95a-ffe9-5995-543d6e4357db@jasonjgw.net> X-Operating-System: Linux opera.rednote.net 5.15.8-200.fc35.x86_64 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.5 Very relevant observation, Jason. Indeed, that file I refer to seems to have been deleted by one upgrade or another over the past week--I've run several. So, not sure what's going on under the hood. All I can say is that creating that file, for whatever reason, caused Espeakup to work on the System76 Meerkat system. On my older, 2012 era custom built Linux board, Espeakup-0.80 is still required, but it now works with the latest alsa. No matter what I try, Espeakup-0.90 won't work, even though the espeak command speaks using espeak-ng. So, I downgraded to the latest Espeak, dated on Arch from mid December, and downgraded Espeakup accordingly. Apparently there must be some kind of reason why Espeakup can't be agnostic between espeak and espeak-ng? Best, Janina Jason White writes: > > On 22/12/21 11:38, Janina Sajka wrote: > > What was the fix? > > > > I introduced a file: > > > > /etc/asound.conf > > Interestingly, I don't have that file on my Arch Linux system, but there are > various configuration files under /etc/alsa/conf.d, apparently placed there > by Pipewire packages. > > -- Janina Sajka (she/her/hers) https://linkedin.com/in/jsajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa