[Bug]: window10 ./start-chrome-debug.sh failed
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 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxhsj/openclaw-zero-token
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linuxhsj/openclaw-zero-token#302 ·
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
linuxhsj/openclaw-zero-token#301 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linuxhsj/openclaw-zero-token#224 · 2 reactions ·
All issues in linuxhsj/openclaw-zero-token
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AloisSeckar/elrh-cosca#36 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
cursor/community-plugins#572 ·
Maintainers usually reply within 1 day
-
[Plugin] calendarOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MUKE-coder/grit#228 ·
-
bug status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dongdongbh/Mindwtr#1587 ·
Maintainers usually reply within 1 day