bug: Computer Use crashes during native accessibility inspection

[rysabh]

The desktop app repeatedly crashes during native Linux Computer Use. One incident occurred when cua.getApp(...) requested the app window’s accessibility tree.

The source calls org.a11y.atspi.Action.GetActions during accessibility-tree inspection and perform_action. Codex identified this as the suspected trigger; the logs did not establish the exact crash cause.

To temporarily avoid this, I had to ask agents to never call org.a11y.atspi.Action.GetActions, directly or through tools such as accessibility-tree inspection or perform_action.

Environment: Ubuntu 22.04.5 LTS, GNOME on X11, amd64. Version 0.11.1, commit 076027fa1a9c, upstream package 26.911.61220, with computer-use-linux enabled.

[ilysenko]

Thank you for the report. We can see that the Linux backend calls AT-SPI GetActions while reading an accessibility tree, but the available evidence does not yet show which process crashed or whether that call caused it.

Could you reproduce this once (preferably with the latest stable ChatGPT Community build) and share:

1. The exact time of the crash, including your time zone; the target application's name and version; the cua.getApp(...) call or other operation that triggered it; and which process/window disappeared (ChatGPT Community, codex-computer-use-linux, or the target app).

2. The relevant lines around that time from these Ubuntu commands, run soon after the crash:

   journalctl --user -b --since "10 minutes ago" -o short-precise
   journalctl -b --since "10 minutes ago" -o short-precise
   coredumpctl --since "10 minutes ago" list

3. If coredumpctl lists a crash, run coredumpctl info <PID> for the relevant PID and include its Executable, Signal, and stack-trace sections. If it lists nothing, please say so. Also tell us whether the same operation crashes consistently and whether it happens with more than one target app.

Please redact account names, paths, window titles, document content, and other private data before posting. Do not upload the raw core dump publicly. These details will let us distinguish a backend crash from a crash in the app being inspected and test whether GetActions is involved.