fix(browser): recover stale Chromium profile locks (#62935) (#62935)

Co-authored-by: Peter Steinberger <steipete@gmail.com>
This commit is contained in:
Sean Coley
2026-04-25 17:21:49 +12:00
committed by GitHub
parent f00d65a304
commit a35333abe1
5 changed files with 300 additions and 55 deletions

View File

@@ -25,6 +25,16 @@ chromium-browser is already the newest version (2:1snap1-0ubuntu2).
This is NOT a real browser - it's just a wrapper.
Other common Linux launch failures:
- `The profile appears to be in use by another Chromium process` means Chrome
found stale `Singleton*` lock files in the managed profile directory. OpenClaw
removes those locks and retries once when the lock points at a dead or
different-host process.
- `Missing X server or $DISPLAY` means OpenClaw is trying to launch a visible
browser on a host without a desktop session. Use `browser.headless: true`,
start `Xvfb`, or run OpenClaw in a real desktop session.
### Solution 1: Install Google Chrome (Recommended)
Install the official Google Chrome `.deb` package, which is not sandboxed by snap: