| Summary: | [GTK4] Tooltips often broken | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | alicem, bugs-noreply, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 210100 | ||
|
Description
Michael Catanzaro
2022-03-23 14:20:38 PDT
Interestingly enough, when a tooltip fails, this happens:
```
(MiniBrowser:17): Gdk-CRITICAL **: 05:04:13.942: OPENGL:
Source: API
Type: Error
Severity: High
Message: GL_INVALID_OPERATION in glGetFramebufferAttachmentParameteriv(invalid pname GL_FRAMEBUFFER_ATTACHMENT_RED_SIZE)
(MiniBrowser:17): Gdk-CRITICAL **: 05:04:13.942: OPENGL:
Source: API
Type: Error
Severity: High
Message: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
(MiniBrowser:17): Gdk-CRITICAL **: 05:04:13.942: OPENGL:
Source: API
Type: Error
Severity: High
Message: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays
(MiniBrowser:17): Gdk-CRITICAL **: 05:04:13.942: OPENGL:
Source: API
Type: Error
Severity: High
Message: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays
(MiniBrowser:17): Gdk-CRITICAL **: 05:04:13.942: OPENGL:
Source: API
Type: Error
Severity: High
Message: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays
```
OK, I'm running with G_DEBUG=fatal-criticals now to try to get a backtrace, but sadly the tooltips that were so broken for me yesterday are working just fine today. Let's hope I manage to catch it. Ok, it's GTK. https://gitlab.gnome.org/GNOME/gtk/-/issues/5258 (In reply to Michael Catanzaro from comment #2) > OK, I'm running with G_DEBUG=fatal-criticals now to try to get a backtrace, > but sadly the tooltips that were so broken for me yesterday are working just > fine today. Let's hope I manage to catch it. I had to give up on this due to https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1055. A fix for that issue was just released yesterday, but hasn't hit freedesktop-sdk yet. I think this got mysteriously fixed at some point in the past year. |