AT-SPI: Could not obtain desktop path or name
First time I got this error when launching tor-browser-sandbox
** (sandboxed-tor-[6214):](6214):) WARNING **: AT-SPI: Could not obtain desktop path or name
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Author
Additional first time I've ever seen errors:
** (sandboxed-tor-[6545):](6545):) WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature ** (sandboxed-tor-[6545):](6545):) WARNING **: atk-bridge: get_device_events_reply: unknown signature ** (sandboxed-tor-[6545):](6545):) WARNING **: atk-bridge: get_device_events_reply: unknown signature
sandbox v.0.0.7 FWIW.
It's related to https://wiki.gnome.org/Accessibility
It also will never work.
Trac:
Resolution: N/A to wontfix
Status: new to closedJust for added clarity, the reason this happens is because that component expects there to be a service running on D-Bus, and the host system's D-Bus is not, and likely never will be allowed into the sandbox.
If this results in fatal errors, it's worth fixing, but otherwise it's an indication that the sandbox is doing some of what it should be doing.
- Author
FWIW i remember having similar warnings with Evince which were solved by defining the
NO_AT_BRIDGE
environment variable. See https://wiki.gnome.org/Accessibility/Documentation/GNOME2/Mechanics#GTK.2B-_and_Accessibility. After rethinking this, I'll suppress the error if it's that easy to do.
Trac:
Status: closed to reopened
Resolution: wontfix to N/ATrac:
Resolution: N/A to fixed
Status: reopened to closed- Trac closed
closed