Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Linux 5.9 missing speakup modules that were enabled in 5.8
Date: Thu, 12 Nov 2020 19:09:53 +0100	[thread overview]
Message-ID: <20201112180953.E3yi_A_BHe2OBqSX0lgjclVleC7iuTc8KCSU-PtDWxU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26319@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Closed issue by joey-commits on void-packages repository

https://github.com/void-linux/void-packages/issues/26319

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
* package:  Linux 5.9.6_1
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``

### Expected behavior
When the espeakup package is installed, speech should be available when starting its service.
### Actual behavior
No speech is heard. This is because speakup modules moved out of staging in 5.9 to another area of the kernel  (drivers/accessibility) and this was missed in the Void build.
### Steps to reproduce the behavior

1. Start the computer with espeakup service and notice that no speech is heard.

  parent reply	other threads:[~2020-11-12 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 15:12 [ISSUE] " joey-commits
2020-11-12 15:37 ` ericonr
2020-11-12 18:09 ` ericonr
2020-11-12 18:09 ` ericonr [this message]
2020-11-12 18:10 ` ericonr
2020-11-12 22:59 ` joey-commits
2020-11-12 23:32 ` ericonr

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=20201112180953.E3yi_A_BHe2OBqSX0lgjclVleC7iuTc8KCSU-PtDWxU@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).