mirror of
https://github.com/lensapp/lens.git
synced 2025-05-20 05:10:56 +00:00
Moving fuzzy bug description into docs FAQ
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
This commit is contained in:
parent
2093e0bc91
commit
b66e2ef12a
@ -43,4 +43,24 @@ Lens will store application logs to following locations depending on your operat
|
||||
|
||||
### How can I see more verbose logs?
|
||||
|
||||
You can start Lens application on debug mode from the command line to see more verbose logs. To start application on debug mode, please provide `DEBUG=true` environment variable and before starting the application, for example: `DEBUG=TRUE /Applications/Lens.app/Contents/MacOS/Lens`
|
||||
You can start Lens application on debug mode from the command line to see more verbose logs. To start application on debug mode, please provide `DEBUG=true` environment variable and before starting the application, for example: `DEBUG=TRUE /Applications/Lens.app/Contents/MacOS/Lens`
|
||||
|
||||
### Why Lens window rendering is broken?
|
||||
|
||||
MacOS users can encouter visual bug with fuzzy lines appeared while [connected to external 4K display](https://www.forbes.com/sites/gordonkelly/2020/06/11/apple-macos-macbook-pro-google-chrome-display-problem/?sh=331ac27967b4). Same thing can happen with any of Electron applications or Chrome itself.
|
||||
|
||||

|
||||
|
||||
As a temporary workaround there is a possibility to disable Chromium GPU acceleration. To do this for Lens, you need to provide `LENS_DISABLE_GPU=true` env variable and relaunch app.
|
||||
|
||||
First, open `.bash_profile` file from your terminal
|
||||
|
||||
```
|
||||
open -a TextEdit.app ~/.bash_profile
|
||||
```
|
||||
|
||||
Then, add this line
|
||||
|
||||
```
|
||||
export LENS_DISABLE_GPU=true
|
||||
```
|
||||
@ -1,23 +0,0 @@
|
||||
# Fuzzy window rendering on external 4K display
|
||||
|
||||
MacOS users can encouter visual bug with fuzzy lines appeared while connected to external 4K display https://www.forbes.com/sites/gordonkelly/2020/06/11/apple-macos-macbook-pro-google-chrome-display-problem/?sh=331ac27967b4. Same thing can happen with any of Electron applications or Chrome itself.
|
||||
|
||||

|
||||
|
||||
As a temporary workaround there is a possibility to disable Chromium GPU acceleration. To do this for Lens, you need to provide `LENS_DISABLE_GPU=true` env variable and relaunch app.
|
||||
|
||||
First, open `.bash_profile` file from your terminal
|
||||
|
||||
```
|
||||
open -a TextEdit.app ~/.bash_profile
|
||||
```
|
||||
|
||||
Then, add this line
|
||||
|
||||
```
|
||||
export LENS_DISABLE_GPU=true
|
||||
```
|
||||
|
||||
Save it and restart Lens.
|
||||
|
||||
*Original bug can be tracked here https://bugs.chromium.org/p/chromium/issues/detail?id=1068170.*
|
||||
Loading…
Reference in New Issue
Block a user