Activity log for bug #1967702

Date Who What changed Old value New value Message
2022-04-04 01:52:17 Tiago M. C. bug added bug
2022-04-04 02:00:08 Ubuntu Kernel Bot linux (Ubuntu): status New Confirmed
2022-04-05 04:18:34 Matthew Ruffell summary Accessibility features have been disabled, modules like speakup_soft and others are missing Enable speakup kernel modules to allow the speakup screen reader to function
2022-04-05 04:18:39 Matthew Ruffell nominated for series Ubuntu Jammy
2022-04-05 04:18:39 Matthew Ruffell bug task added linux (Ubuntu Jammy)
2022-04-05 04:18:47 Matthew Ruffell linux (Ubuntu Jammy): status Confirmed In Progress
2022-04-05 04:18:50 Matthew Ruffell linux (Ubuntu Jammy): importance Undecided High
2022-04-05 04:18:54 Matthew Ruffell linux (Ubuntu Jammy): assignee Matthew Ruffell (mruffell)
2022-04-05 04:19:11 Matthew Ruffell description From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line CONFIG_ACCESSIBILITY=y and the following lines are also missing: # # Speakup console speech # CONFIG_SPEAKUP=m CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m CONFIG_SPEAKUP_SYNTH_DUMMY=m # end of Speakup console speech ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tiago 1259 F.... pulseaudio /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 3 22:05:39 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0KD03P dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules.
2022-04-05 05:04:13 Matthew Ruffell tags amd64 apport-bug jammy amd64 apport-bug jammy seg
2022-04-05 07:00:27 Matthew Ruffell description BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: systemd[1]: Starting Software speech output for Speakup... kernel: input: Speakup as /devices/virtual/input/input5 kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123) kernel: speakup 3.1.6: initialized kernel: synth name on entry is: (null) kernel: synth probe kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122) kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121) systemd[1]: Started Software speech output for Speakup. You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules.
2022-04-19 06:12:07 Matthew Ruffell linux (Ubuntu Jammy): status In Progress Fix Committed
2022-04-28 11:13:57 Ubuntu Kernel Bot tags amd64 apport-bug jammy seg amd64 apport-bug jammy seg verification-needed-jammy
2022-04-30 00:21:33 Tiago M. C. tags amd64 apport-bug jammy seg verification-needed-jammy amd64 apport-bug jammy seg verification-done-jammy
2022-05-13 10:28:06 Ubuntu Kernel Bot tags amd64 apport-bug jammy seg verification-done-jammy amd64 apport-bug jammy seg verification-done-jammy verification-needed-focal
2022-05-13 14:12:03 Tiago M. C. tags amd64 apport-bug jammy seg verification-done-jammy verification-needed-focal amd64 apport-bug jammy seg verification-done-focal verification-done-jammy
2022-06-03 07:50:01 Launchpad Janitor linux (Ubuntu Jammy): status Fix Committed Fix Released
2022-06-03 07:50:01 Launchpad Janitor cve linked 2022-21499
2022-09-02 17:48:00 Launchpad Janitor linux (Ubuntu): status Fix Committed Fix Released