Bug 26040 - 'Fake' events for application adding are not properly constructed.
Summary: 'Fake' events for application adding are not properly constructed.
Alias: None
Product: at-spi2
Classification: Unclassified
Component: atk (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Mark Doffman
QA Contact:
Depends on:
Reported: 2010-01-14 04:31 UTC by Mark Doffman
Modified: 2010-01-24 07:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Mark Doffman 2010-01-14 04:31:45 UTC
The events send 
the following problem ocoured after starting orca:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/pyatspi/busutils/bus.py", line 74, in _event_dispatch
    func (*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/pyatspi/appevent.py", line 166, in handler_wrapper
    return event_handler(event)
  File "/usr/local/lib/python2.6/dist-packages/orca/focus_tracking_presenter.py", line 801, in _enqueueEvent
    if not event.source:
  File "/usr/lib/python2.6/dist-packages/pyatspi/appevent.py", line 288, in source
  File "/usr/lib/python2.6/dist-packages/pyatspi/factory.py", line 78, in __call__
    dbus_object = self._connection.get_object (name, path)
  File "/usr/lib/python2.6/dist-packages/pyatspi/busutils/bus.py", line 86, in get_object
    return _connection.ProxyObject (self, name, path, introspect=False)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 232, in __init__
TypeError: validate_bus_name() argument 1 must be string, not dbus.Struct
Comment 1 Mark Doffman 2010-01-24 07:42:38 UTC
Changes have been introduced to fix this issues.

Fake events are no longer generated within pyatspi, but emitted by the desktop object located within the registry daemon.

Commits containing fix:

89422700d5b03cac05ba - at-spi2-atk
90d1f73334703ea89a2b - pyatspi
061b2101b6b1aeadd2   - at-spi2-core

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.