[Bug]: window10 ./start-chrome-debug.sh failed

Open
#300 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
shell, typescript
Domain
tooling

Research direction

Start by reading start-chrome-debug.sh and trace how it detects Chrome when running under WSL. Check whether the script is expected to find a Windows installation or require a Linux installation. Done means the script handles the intended Windows 10 and WSL setup correctly and reports an actionable error when Chrome cannot be found.

Written by the indexing model from the issue text.

Description

bug
Bug type

Regression (worked before, now fails)

Summary

hyf@MS-KQKVELWFPJEA:/mnt/d/opensource/openclaw-zero-token-main$ ./start-chrome-debug.sh

启动 Chrome 调试模式

系统: wsl
✗ 未找到 Chrome / Chromium,请先安装后重试

hyf@MS-KQKVELWFPJEA:/mnt/d/opensource/openclaw-zero-token-main$

Steps to reproduce

hyf@MS-KQKVELWFPJEA:/mnt/d/opensource/openclaw-zero-token-main$ ./start-chrome-debug.sh

启动 Chrome 调试模式

系统: wsl
✗ 未找到 Chrome / Chromium,请先安装后重试

hyf@MS-KQKVELWFPJEA:/mnt/d/opensource/openclaw-zero-token-main$

Expected behavior

window10中安装了,难道还要在wsl系统中安装?

Actual behavior

运行不了

OpenClaw version

当前开发分支

Operating system

windows11

Install method

No response

Model

还没配置

Provider / routing chain

openclaw

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Dominant language
TypeScript
Stars
5.2k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxhsj/openclaw-zero-token

All issues in linuxhsj/openclaw-zero-token

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.