Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): orca 3.2.1 How reproducible: first time Steps to Reproduce: 1. Boot to failover GNOME session 2. Start Applications -> accesibility -> screen reader Orca 3. Process initial configuration Actual results: There's a crash in gnome-terminal first time. Another time the application won't start at all. After reboot application starts skipping the terminal based configuration. Expected results: Orca gets configured and started. Additional info: Message 'Gtk-Message: Failed to load module "pk-gtk-module"' appears on startup of this application.
After reproducing this, process speech-dispatcher started to eat all my cpu time on background.
I just tested running Orca on my day-to-day F16 desktop and it seemed to work, though i'm not sure what you mean by 'process initial configuration'. but it didn't crash, didn't cause high CPU use, and read out things on the screen. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I can reproduce this in fallback mode after a VM install, though.
The gnome-terminal crash seems either unreliable or dependent on what options you pick in the config. I reproduced the issue on my laptop in Shell mode, and saw the CPU-thrashing speech-dispatcher processes; but after kill -9ing them I ran Orca again, it seemed to cause the Shell to restart, but then it worked. somewhat odd. I did get gdb traces from the speech-dispatcher processes, which I'll attach. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Behaviour seems similar in the VM I first reproduced in: after a reboot, orca seems to start working.
I don't think there is anything specific to fallback mode here. Accessibility just doesn't work reliably. To say anything more, we need a stacktrace.
oh, sorry, forgot to attach them. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.