+++ This bug was initially created as a clone of Bug #19275 +++ I also get: process 10355: arguments to dbus_message_new_signal() were incorrect, assertion "_dbus_check_is_valid_member (name)" failed in file dbus-message.c line 1163. This is normally a bug in some application using the D-Bus library. process 10355: arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521. This is normally a bug in some application using the D-Bus library. process 10355: arguments to dbus_connection_send() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3100. This is normally a bug in some application using the D-Bus library. process 10355: arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391. This is normally a bug in some application using the D-Bus library. in the registry side though it seems both issues are not correlated . Could you test with rhythmbox or help me find out what s wrong with the atk_dbus_get_object (I am lost as ref2ptr have this acessible inserted in the register or should have).
All mouse and keyboard events were being sent in the incorrect format from the DEC. Git commit for the FIX: commit 95972f3fbce62c1442935212bb6b98b7c8628741 Author: Mark Doffman <mdoff@silver-wind.(none)> Date: Tue Mar 3 15:49:26 2009 +0000 2009-03-03 Mark Doffman <mark.doffman@codethink.co.uk> * pyatspi/* Fix event printing without an accessible source. Fix event deregistration. * registryd/deviceeventcontroller.c Fix the mouse and keyboard events from the DEC.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.