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

Black dropdown and GL error #7289

Closed
superjamie opened this issue Sep 21, 2016 · 5 comments
Closed

Black dropdown and GL error #7289

superjamie opened this issue Sep 21, 2016 · 5 comments
Labels
blocked/need-info ❌ Cannot proceed without more information

Comments

@superjamie
Copy link

  • Electron version: 1.4.0
  • Operating system: Ubuntu 16.04
  • Graphics card: AMD Radeon HD6870 (open source radeon driver)

I am using the PiBakery Electron app. There is a dropdown which displays like so:

Screenshot showing black square

This series of messages is repeated each time I try to open the dropdown:

[26450:0920/230638:ERROR:gles2_cmd_decoder_autogen.h(148)] [.DisplayCompositor-0x23a1abe75e00]GL ERROR :GL_INVALID_ENUM : glBindTexture: target was GL_FALSE
[26450:0920/230638:ERROR:gles2_cmd_decoder_autogen.h(3321)] [.DisplayCompositor-0x23a1abe75e00]GL ERROR :GL_INVALID_ENUM : glTexParameteri: target was GL_FALSE
[26450:0920/230638:ERROR:gles2_cmd_decoder_autogen.h(3321)] [.DisplayCompositor-0x23a1abe75e00]GL ERROR :GL_INVALID_ENUM : glTexParameteri: target was GL_FALSE

This is only a cosmetic bug, I can still select the contents of the dropdown successfully.

This happens with and without a compositor. I tested with compton.

The file in question actually comes from Chromium. I spoke to the #chromium-support community on Freenode. They said there might be relevant GL fixes in the latest Chromium (it looks like Electron is on Chromium 52, but Chromium 53 is out now) or there could be Electron-specific changes to the renderer which cause this.

@kevinsawicki
Copy link
Contributor

They said there might be relevant GL fixes in the latest Chromium (it looks like Electron is on Chromium 52, but Chromium 53 is out now) or there could be Electron-specific changes to the renderer which cause this.

Electron 1.4.0 is running Chromium 53.0.2785.113

@kevinsawicki
Copy link
Contributor

Are you able to test out the HTML from that app directly in Chromium and verify the dropdown does appear correctly there?

@kevinsawicki kevinsawicki added the blocked/need-info ❌ Cannot proceed without more information label Sep 21, 2016
@superjamie
Copy link
Author

superjamie commented Sep 22, 2016

That doesn't work sorry. The application hangs and I cannot bring up the dialog in question. I guess the app needs other stuff which doesn't load when I launch it with either of:

  • chromium-browser app/index.html
  • sudo chromium-browser --user-data-dir=./rootdata/ app/index.html

(the app usually does require root permissions, as it writes to raw sdcard devices)

I tried with Chromium 53.0.2785.89 from the Chromium Build Team PPA.

@KynoYang
Copy link

similar with #4322

@kevinsawicki
Copy link
Contributor

Thanks @KynoYang merging into #4322

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/need-info ❌ Cannot proceed without more information
Projects
None yet
Development

No branches or pull requests

3 participants