Hide Forgot
Description of problem: Sometimes when screen reader is (re)started (Alt+Super+s) it does not start correctly. Orca consumes 100 % CPU and no speech can be heard. Sometimes Orca dies after a while. In other cases it must be killed (SIGKILL). What is the most important - in such a situation the blind user (without the voice output) has practically no chance to find out what happened and to fix it. Version-Release number of selected component (if applicable): orca-3.18.2-1.fc23.noarch speech-dispatcher-0.8.3-2.fc23.x86_64 How reproducible: Sometimes (10 - 30 %) Steps to Reproduce: 1. Log in to Gnome (on X). 2. Start screen reader (Alt+Super+s). 3. Stop screen reader (Alt+Super+s). 4. Wait for some time (min. several seconds, max. 1 hour). 5. Try to start screen reader again (Alt+Super+s). 6. If screen reader starts correctly, go to step 3. Actual results: Ocra is started but does not talk and consumes 100 % CPU. Expected results: Orca should start correctly (talk and not consume 100 % CPU). Additional info: I tried many times but I was not able to find a (more) reliable reproducer. Tested on bare metal and on virtual machine (both x86_64) - same result.
When Orca is started but not talking, can you get into a terminal or console and do a 'pkill -9 speech*'? If so, does that solve it?
Tried on 3 computers after recent updates. One of them fresh installed (new HDD). Now I am unable to reproduce the same behaviour. Sometimes when Orca is restarted soon after it was stopped, it is not started at all. But further restart make it run correctly. When I reproduced the total Orca freeze (before updates), the 'pkill -9 speech*' did NOT solve it. I had to kill Orca and then start it again.
Reproduced again - x86_64 VM, orca-3.18.2-1.fc23. Scenario: - Orca started (alt+super+s) - LO started - OTD opened in Writer - navigation through document (up, down, pgup, pgdown) - waited for some times (cca 20 minutes, screen saver activated) - password entered (to unlock screen) - Orca stopped (alt+super+s) - wait several minutes - Orca started (alt+super+s) Orca does not speak and consumes 100 % CPU. "pkill -9 speech" Orca still does not speak and consumes 100 % CPU. Switching off screen reader also did not help. I had to "pkill -9 orca" and start it again (alt+super+s). "Mission impossible" for regular blind user.
You wrote "speech"; not "speech*". It makes a difference. Could you please verify that you really did use the wildcard with pkill?
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.