GNOME Bugzilla – Bug 658533
Error starting Caribou process: /usr/libexec/antler-keyboard exited with status 1
Last modified: 2011-10-09 20:37:07 UTC
I update caribou-0.3.5 to Fredora15 ,i got error as list each boot time or run caribou in terminal : Error starting Caribou process /usr/libexec/antler-keyboard exited with status 1 I update caribou as follow 1.get caribou-0.3.5-2.i586 2.rpm -Uvh caribou-0.3.5-2.i586 3.logout I do not know what root cause is ???
0.3.5 is old. Can you please try 0.3.91 which is the latest development version and report back?
I can confirm with caribou 0.3.91-1 on Fedora 16 x64. $ caribou Gtk-Message: Failed to load module "gail" ** (-c:2575): WARNING **: Invalid object type create except I get a popup with status 139.
I try caribou 0.3.91-1 on Fedora 16 On screen keyboard can not load automatic , then run /usr/bin/caribou in terminal ,i got error message: ERROR:dbus.connection:Unable to set arguments () according to signature u'u': <type 'exceptions.TypeError'>: More items found in D-Bus signature than in Python arguments Traceback (most recent call last):
+ Trace 228391
self._set_entry_location(acc)
self.keyboard_proxy.Show()
**keywords)
message.append(signature=signature, *args)
I see this too, with 0.3.91 in f16
Created attachment 196131 [details] [review] Fix caribou daemon to use new keyboard DBus API.
Could someone please test the patch above?
The patch is good in so far as caribou doesn't crash at startup anymore. But I still don't see a keyboard. As soon as I move the focus to an entry or other text input field, I get: Traceback (most recent call last):
+ Trace 228400
return callback(event)
self.keyboard_proxy.SetCursorLocation(bx, by, bw, bh)
return self._proxy_method(*args, **keywords)
message, timeout)
Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pyatspi/registry.py", line 193, in eventWrapper return callback(event) File "/usr/lib/python2.7/site-packages/caribou/daemon/main.py", line 145, in on_focus self._set_entry_location(acc) File "/usr/lib/python2.7/site-packages/caribou/daemon/main.py", line 127, in _set_entry_location self.keyboard_proxy.SetCursorLocation(bx, by, bw, bh) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Failed: TypeError: this.actor is null Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pyatspi/registry.py", line 193, in eventWrapper return callback(event) File "/usr/lib/python2.7/site-packages/caribou/daemon/main.py", line 145, in on_focus self._set_entry_location(acc) File "/usr/lib/python2.7/site-packages/caribou/daemon/main.py", line 127, in _set_entry_location self.keyboard_proxy.SetCursorLocation(bx, by, bw, bh) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Failed: TypeError: this.actor is null /usr/lib64/python2.7/site-packages/gi/types.py:43: Warning: g_main_loop_quit: assertion `loop != NULL' failed return info.invoke(*args, **kwargs)
Created attachment 196188 [details] [review] add *lib64* to PYTHONPATH in antler script.
It is hard for me to do more research on this until I could reproduce it in F16. In the meantime here is another patch that might remedy this issue. Why doesn't the packager check if the package provides the basic functionality it is supposed to have?
Can anyone launch caribou successfully in fc16 ?
caribou 0.3.92 works for me with Ubuntu 11.10. Thanks!
I test caribou-0.3.92 in f16 , but press Antler Preference button cause caribou to sleep , cannot close the Antler Preference window and cannot take some steps
@user: File a separate new report with exact steps to reproduce (click by click), please.
Marking as invalid for now, since this was a mishmash of issues. Any specific issue should have a new report. Thanks!