GNOME Bugzilla – Bug 348084
Orca can not start on Solaris_nevada_44/vermillion_45.
Last modified: 2006-07-25 22:24:52 UTC
Please describe the problem: Orca can not start on Solaris_nevada_44/vermillion_45.Both X86 and Sparc Steps to reproduce: 1. Start orca in terminal; 2. The GUI preference is start up; 3. Click "Close" button Actual results: Orca can not be launched and then display traceback in terminal. bash-3.00$ orca GTK Accessibility Module initialized Speech not available. Traceback (most recent call last):
+ Trace 69461
self.prefsDict["speechServerFactory"] = self.factory
raise AttributeError("Widget [" + attribute + "] not found")
Expected results: Orca can start up. Does this happen every time? Yes Other information: -bash-3.00$ orca --version Orca 0.2.6 Below is the stack after step #3 ----------------- lwp# 1 / thread# 1 -------------------- d2649695 pollsys (8896100, 15, 8046c08, 0) d260b3e3 poll (8896100, 15, 30) + 52 d20aab61 g_main_context_iterate (8159128, 1, 1, 813d640) + 399 d20ab19e g_main_loop_run (878ad88) + 1ba cf25f3b2 bonobo_main (83867ec, 8046d94, 84914e4, 8082620, 8046d14, d272f23d) + 5e cefc88b1 _wrap_bonobo_main (0, 0) + 35 d272f23d call_function (8046d94, 0) + 3e9 d272ad68 PyEval_EvalFrame (8491394) + a68 d272f422 fast_function (841495c, 8046ea4, 1, 1, 0) + a6 d272efb9 call_function (8046ea4, 0) + 165 d272ad68 PyEval_EvalFrame (80c0984) + a68 d272f422 fast_function (847e79c, 8046fb4, 1, 1, 0) + a6 d272efb9 call_function (8046fb4, 1) + 165 d272ad68 PyEval_EvalFrame (8120ffc) + a68 d272f422 fast_function (847e924, 80470c4, 0, 0, 0) + a6 d272efb9 call_function (80470c4, 0) + 165 d272ad68 PyEval_EvalFrame (80a10ec) + a68 d272dfae PyEval_EvalCodeEx (8098c20, 8078824, 8078824, 0, 0, 0) + 71e d272a2f9 PyEval_EvalCode (8098c20, 8078824, 8078824) + 25 d2749027 run_node (80613c8, 804743c, 8078824, 8078824, 804729c) + 37 d2748fe3 run_err_node (80613c8, 804743c, 8078824, 8078824, 804729c) + 23 d2748fb5 PyRun_FileExFlags (d2692030, 804743c, 101, 8078824, 8078824, 1) + 61 d274836c PyRun_SimpleFileExFlags (d2692030, 804743c, 1, 804729c) + 274 d2747dbb PyRun_AnyFileExFlags (d2692030, 804743c, 1, 804729c) + 57 d274d93a Py_Main (2, 80472e4) + 792 080506e2 main (2, 80472e4, 80472f0) + 12 08050642 _start (2, 804742c, 804743c, 0, 804744a, 804747e) + 7a ----------------- lwp# 2 / thread# 2 -------------------- d2648bb5 accept (4, ceb8b540, ceb8b650, 1) ceec39c5 sock_accept (811ef60, 0) + 65 d272f23d call_function (ceb8b714, 0) + 3e9 d272ad68 PyEval_EvalFrame (832781c) + a68 d272f422 fast_function (84548b4, ceb8b824, 1, 1, 0) + a6 d272efb9 call_function (ceb8b824, 0) + 165 d272ad68 PyEval_EvalFrame (8114574) + a68 d272f422 fast_function (8473294, ceb8b934, 1, 1, 0) + a6 d272efb9 call_function (ceb8b934, 0) + 165 d272ad68 PyEval_EvalFrame (8433dbc) + a68 d272f422 fast_function (846efb4, ceb8ba44, 1, 1, 0) + a6 d272efb9 call_function (ceb8ba44, 0) + 165 d272ad68 PyEval_EvalFrame (83270bc) + a68 d272f422 fast_function (846ef7c, ceb8bb54, 1, 1, 0) + a6 d272efb9 call_function (ceb8bb54, 0) + 165 d272ad68 PyEval_EvalFrame (83310a4) + a68 d272f422 fast_function (844fed4, ceb8bc64, 1, 1, 0) + a6 d272efb9 call_function (ceb8bc64, 0) + 165 d272ad68 PyEval_EvalFrame (833129c) + a68 d272dfae PyEval_EvalCodeEx (8449b60, 842335c, 0, 80dec78, 1, 0) + 71e d26f2d9a function_call (844f614, 80dec6c, 0) + 162 d26e2812 PyObject_Call (844f614, 80dec6c, 0) + 1e d26e850c instancemethod_call (84097ac, 80dec6c, 0) + b0 d26e2812 PyObject_Call (84097ac, 806102c, 0) + 1e d272ed51 PyEval_CallObjectWithKeywords (84097ac, 806102c, 0) + b5 d274efcf t_bootstrap (84c0440) + 2f d26483b7 _thr_setup (d2422400) + 51 d2648600 _lwp_start (d2422400, 0, 0, 0, 0, 0)
I'd like to provide more information about this bug: After orca gui setting is up, the speech system, speech synthesizer and person combobox are broken, nothing can be selected in speech tab. After orca text setting is up, the keyboard will be locked, we can input nothing with keyboard to answer the orca setting questions. This is a serious bug.
Looks like no speech servers were shipped with Vermillion 45. Can you try verifying this on your machine by running "test-speech"? If it comes back with no servers, then that's the problem. This is a side effect of repackaging the speech drivers in their own packages - it looks like the proper files to say what to include in Vermillion 45 didn't get updated accordingly. I actually verified that this was the case on a fresh install of Vermillion 45 on Nevada 44 and has sent e-mail off to the release team to make sure the gnome-speech driver for FreeTTS speech driver is installed. I'll look into getting rid of the ominous looking stack trace.
Created attachment 69355 [details] [review] Patch to fail gracefully if speech is not available. This patch allows Orca to fail gracefully if speech is not available. Note that it also allows Orca to run in "silent mode" if you set orca.settings.speechServerFactory=None in ~/.orca/user-settings.py. The "silent mode" is of little use to users of Orca, but it is useful for applications developers: they can run orca in the background while testing their applications, which can help flush out more application bugs.
*** Bug 319531 has been marked as a duplicate of this bug. ***