Opened 3 months ago

Closed 3 months ago

#22712 closed defect (fixed)

AT-SPI: Could not obtain desktop path or name

Reported by: cypherpunks Owned by: yawning
Priority: Medium Milestone:
Component: Applications/Tor Browser Sandbox Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

First time I got this error when launching tor-browser-sandbox

** (sandboxed-tor-browser:6214): WARNING **: AT-SPI: Could not obtain desktop path or name

Child Tickets

Change History (6)

comment:1 Changed 3 months ago by cypherpunks

Additional first time I've ever seen errors:

** (sandboxed-tor-browser:6545): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature

** (sandboxed-tor-browser:6545): WARNING **: atk-bridge: get_device_events_reply: unknown signature

** (sandboxed-tor-browser:6545): WARNING **: atk-bridge: get_device_events_reply: unknown signature

sandbox v.0.0.7 FWIW.

comment:2 Changed 3 months ago by yawning

Resolution: wontfix
Status: newclosed

It's related to https://wiki.gnome.org/Accessibility

It also will never work.

comment:3 Changed 3 months ago by yawning

Just 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.

comment:4 Changed 3 months ago by cypherpunks

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.

comment:5 Changed 3 months ago by yawning

Resolution: wontfix
Status: closedreopened

After rethinking this, I'll suppress the error if it's that easy to do.

Note: See TracTickets for help on using tickets.