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

Tooltip is sometime broken #23946

Closed
jeremy447 opened this issue Apr 5, 2017 · 12 comments
Closed

Tooltip is sometime broken #23946

jeremy447 opened this issue Apr 5, 2017 · 12 comments
Assignees
Labels
electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@jeremy447
Copy link

Hello,

The tooltip is sometime broken. Maybe it's related to this chromium issue ?

screenshot from 2017-04-05 19-05-12

https://bugs.chromium.org/p/chromium/issues/detail?id=442111

  • VSCode Version: 1.10.2
  • OS Version: Fedora 25

Thanks !

@bpasero
Copy link
Member

bpasero commented Apr 5, 2017

Yeah could be.

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Apr 5, 2017
@bpasero bpasero added this to the Backlog milestone Apr 5, 2017
@jeremy447
Copy link
Author

Some other way the tooltip is broken

screenshot from 2017-04-09 10-12-04

screenshot from 2017-04-09 10-12-57

@bpasero bpasero removed the bug Issue identified by VS Code Team member as probable bug label Apr 10, 2017
@bpasero
Copy link
Member

bpasero commented May 15, 2017

@Paviluf do you still see this in 1.12?

@jeremy447
Copy link
Author

It still happening. I think that will happen until the bug is fixed in Chromium
https://bugs.chromium.org/p/chromium/issues/detail?id=442111

@ghost
Copy link

ghost commented May 15, 2017

Have you tried that mesa patch, just in case? If you try, remember to set LIBGL_DRI3_DISABLE=1 before starting your program, else patch has no effect with dri3.

@jeremy447
Copy link
Author

I didn't tried that patch and I won't be able to do so due to lack of time.
The fix could come from mesa too indeed
https://bugs.freedesktop.org/show_bug.cgi?id=90264

@falaca
Copy link

falaca commented Jun 12, 2017

If you guys are looking for a workaround, you could use LIBGL_ALWAYS_SOFTWARE=1 to disable hardware acceleration. Not an ideal solution, but might not be too bad for a tool like this which isn't really graphics-heavy.

@jeremy447
Copy link
Author

It seem that will be "fixed" soon in chromium. They will disable compositing for tooltips on Linux.
https://bugs.chromium.org/p/chromium/issues/detail?id=442111

@ghost
Copy link

ghost commented Aug 13, 2017

they say:

This CL is to fix the elusive bug 442111, which only occurs on intel
hardware.

that is not true, happens on AMD hardware too; however they seem to be disabling it on both anyway, if I'm reading this right: https://chromium.googlesource.com/chromium/src.git/+/1721ffa7da2ce55c0c4fdb8bd363eafbe71c23d6%5E%21/

@jeremy447
Copy link
Author

Fixed in Chromium 62.

@bpasero bpasero added electron Issues and items related to Electron and removed workbench labels Nov 13, 2017
@bpasero bpasero removed this from the Backlog milestone Nov 16, 2017
@RuBAN-GT
Copy link

I have this bug with VSCode 1.20.1 and ArchLinux with Gnome 3.26.2.

@bpasero
Copy link
Member

bpasero commented Jan 25, 2019

Closing this issue given that we plan to release VSCode stable early February with Electron 3.x. If you want to benefit from the fix already, consider to use our insiders version that already contains the fix: https://code.visualstudio.com/insiders/

@bpasero bpasero closed this as completed Jan 25, 2019
@bpasero bpasero added this to the December/January 2019 milestone Jan 25, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

4 participants