Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: cannot open chrome://gpu on Linux #39535

Closed
3 tasks done
brjsp opened this issue Aug 16, 2023 · 0 comments · Fixed by #39556
Closed
3 tasks done

[Bug]: cannot open chrome://gpu on Linux #39535

brjsp opened this issue Aug 16, 2023 · 0 comments · Fixed by #39556
Assignees
Labels
25-x-y 26-x-y 27-x-y bug 🪲 chromium platform/all status/confirmed A maintainer reproduced the bug or agreed with the feature

Comments

@brjsp
Copy link
Contributor

brjsp commented Aug 16, 2023

Preflight Checklist

Electron Version

25.5.0

What operating system are you using?

Other Linux

Operating System Version

openSUSE Tumbleweed

What arch are you using?

x64

Last Known Working Electron version

24.7.1

Expected Behavior

When running electron chrome://gpu a page of system diagnostics should open.

Actual Behavior

Instead a blank window opens and (node:14996) electron: Failed to load URL: chrome://gpu/ with error: ERR_FAILED gets printed to console.

Testcase Gist URL

No response

Additional Information

This issue happens with electron 25 and 26. It was fine in electron 24.

@brjsp brjsp added the bug 🪲 label Aug 16, 2023
@codebytere codebytere added platform/all status/confirmed A maintainer reproduced the bug or agreed with the feature 25-x-y labels Aug 16, 2023
@codebytere codebytere self-assigned this Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
25-x-y 26-x-y 27-x-y bug 🪲 chromium platform/all status/confirmed A maintainer reproduced the bug or agreed with the feature
Projects
No open projects
Status: Unsorted Items
Status: 🛠 Fixed for Next Release
Status: 🛠️ Fixed for Next Release
Development

Successfully merging a pull request may close this issue.

2 participants