Heads-up: on GNOME/Xwayland, creating an Agent Window can kill Chrome 151 (not extension-specific; nested X server works)

[a5345534]

BrowserSkill informational issue (GitHub, submitted via gh)

Personal data removed: no user name, host name, home path, private URL, token or
extension id.

---

Title: Heads-up: on GNOME/Xwayland, creating an Agent Window can kill Chrome 151 (not extension-specific; nested X server works)

Body

While driving Chrome 151 through this extension on Ubuntu 24.04 with a
GNOME 46 / Wayland session (X clients on Mutter's Xwayland :1), starting a
session reliably aborted the browser process, so bsk session start failed with
browser disconnected before cancellation, and systemd reported
Main process exited, code=dumped, status=5/TRAP (SIGTRAP).

This is not caused by the extension: a plain Chrome with a throwaway profile,
no extensions and no restored windows does the same when asked for a second
window:

tmp=$(mktemp -d)
google-chrome --user-data-dir="$tmp" about:blank &              # first window: fine
google-chrome --user-data-dir="$tmp" --new-window about:blank   # browser traps (5/5)

The same sequence on a plain X server (Xvfb) or a nested X server (Xephyr) opens
windows normally, so the trigger is the Mutter Xwayland display. Reported to
Chromium (see the linked issue) and cross-referenced to Mutter.

Workaround that worked here: run the automation Chrome on a nested X server
(Xephyr :10 -ac -screen 1440x900) instead of the session's Xwayland display.
With that, bsk session start and full session start → navigate → observe → stop
cycles complete with the browser process staying alive. The desktop then shows
the browser inside the nested server's window, and DevTools/CDP behaviour is
unchanged.

Environment: Google Chrome 151.0.7922.137-1, Ubuntu 24.04.4, kernel 7.0.0-30,
GNOME Shell 46.0, Xwayland 23.2.6, extension 0.3.1, bsk 0.3.1.

[a5345534]

Follow-up: this was a Chrome 151 regression. Upgrading to Chrome 154.0.8037.57 resolves it — the same second-window sequence that aborted 5/5 on 151 now survives on the session's Xwayland display, and Agent Window creation works normally again. Chromium 153 was also unaffected. No extension-side change was needed.