[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-09-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.19.0-15.15

---
linux (5.19.0-15.15) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-15.15 -proposed tracker (LP: #1983335)

  * Miscellaneous Ubuntu changes
- [Config] update annotations to support both gcc-11 and gcc-12

 -- Andrea Righi   Tue, 02 Aug 2022 09:23:01
+0200

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-06-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-35.36

---
linux (5.15.0-35.36) jammy; urgency=medium

  * CVE-2022-21499
- SAUCE: debug: Lock down kgdb

linux (5.15.0-34.35) jammy; urgency=medium

  * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)

  * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources

  * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized

  * config CONFIG_HISI_PMU for  kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m

  * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops

  * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"

  * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead

  * Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on 
EliteBook
  845/865 G9

  * Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360

  * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices

  * Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config

  * Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
- 

[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-05-13 Thread Tiago M. C.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-05-13 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-32.33~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-29 Thread Tiago M. C.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-29 Thread Tiago M. C.
Hi Matthew! Fix that was applied in Linux/5.15.0-28.29 kernel resolved
the issue. Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-28 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-28.29 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-19 Thread Matthew Ruffell
Hi Tiago,

The kernel team have reviewed the patch, and it has received 2x acks [1]
and it has been applied [2] to the Jammy kernel git tree [3].

[1] https://lists.ubuntu.com/archives/kernel-team/2022-April/129208.html
[2] https://lists.ubuntu.com/archives/kernel-team/2022-April/129498.html
[3] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=438e2ff5cbc602384724c217880f216221b93ffc

I am expecting it to be contained in the 2022.04.18 Kernel SRU cycle,
https://kernel.ubuntu.com/, and I will write back with more details once
it has been built and placed into -proposed for verification.

Thanks,
Matthew

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-17 Thread Tiago M. C.
Thank you very much Matthew!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-05 Thread Matthew Ruffell
Hi Tiago,
Thanks for reporting!

I have submitted patches to the Ubuntu kernel mailing list to get this
fixed.

https://lists.ubuntu.com/archives/kernel-team/2022-April/129192.html
https://lists.ubuntu.com/archives/kernel-team/2022-April/129193.html
https://lists.ubuntu.com/archives/kernel-team/2022-April/129194.html

Next step is for the kernel team to review the patches.

Thanks,
Matthew

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug 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:

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-05 Thread Matthew Ruffell
** Description changed:

  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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug 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
  

[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-04 Thread Matthew Ruffell
** Tags added: seg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

2022-04-04 Thread Matthew Ruffell
** Summary changed:

- 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

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

** Description changed:

- 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
+ 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
- and the following lines are also missing:
- #
- # Speakup console speech
- #
  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_DECEXT=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
- 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:
-  USERPID 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.
+ [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