Screen flickering issue on ChromeOS

[chibuezeanakor]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

When opening the Zed editor (Linux version) on my Chromebook, the app starts flickering, and I don't know how to stop it. Plus, none of the buttons in the app work when this happens, so I can't go into the app to figure out a solution to this. I attached a video to show this issue in action.

Screen recording 2024-07-11 10.07.24 PM.webm

Environment

Computer make and model: Framework Laptop - Chromebook Edition OS: ChromeOS 126 CPU: 12th Gen Intel(R) Core(TM) i5-1240P (16 threads, 3.85GHz) RAM: 32 GB Storage: 1TB

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

Zed.log

[ajorg]

I see the same sort of thing on my Samsung Galaxy Chromebook, only much slower.

[JosephTLyons]

I wonder if this is the same issue as this flickering one:

• https://github.com/zed-industries/zed/issues/14101

[ajorg]

To me it looks very different from that, like it's displaying two different UIs.

[codebird]

Same issue here. Tried some stuff such as enabling gpu for crostini in chrome flags. Low density makes the window bigger but the flickering stays...

[Trombach]

I am seeing the same thing. I think it's switching between the auto update UI and the normal UI. I've opened zed with the --foreground option and I can see there is an error with finding a file. I'll have a look at the source and see if I can figure out what might be missing. Although I'm not entirely sure if that's the root of the problem

[codebird]

I am seeing the same thing. I think it's switching between the auto update UI and the normal UI. I've opened zed with the --foreground option and I can see there is an error with finding a file. I'll have a look at the source and see if I can figure out what might be missing. Although I'm not entirely sure if that's the root of the problem

For me there is no error whatsoever, I tried foreground, and since the beginning I am looking at the logs, in the logs there is a warning that might have to do something with us:

[WARN] Unable to forbid exclusive full screen

[Trombach]

I actually just noticed that I was running 143. After updating to the latest version of zed, the error message has disappeared, but the behaviour is the same. I'm also seeing the [WARN] Unable to forbid exclusive full screen in the logs, but that's all.

[codebird]

Pulled latest version, now I am getting a pop up on launch, saying that the gpu is an emulated software gpu and it is unsupported

[AdjectiveAllison]

Hey, I'm not completely positive if the chromeOS bug is tied to what we were experiencing on raw linux, but I suspect it is. Might be worth looking at what mesa version you're using in your crostini container!

Here is the comment where we figured it out for reference: https://github.com/zed-industries/zed/issues/14101#issuecomment-2254601539

[Trombach]

Hey, I'm not completely positive if the chromeOS bug is tied to what we were experiencing on raw linux, but I suspect it is. Might be worth looking at what mesa version you're using in your crostini container!

Here is the comment where we figured it out for reference: #14101 (comment)

I'm also not sure if it's the same bug. For me this is happening on an AMD GPU and not an intel one. I've checked my mesa version and it's 22.3.6, so much older than the problematic version mentioned in the other issue.

My desktop running Manjaro and mesa 24.1.3, is not affected by this bug (using a dedicated AMD GPU)

Edit: one more hint that this is a different issue is that you can see that in the issue here, the screen switches between checking for updates and the normal view. I have a feeling it gets stuck in an infinite loop of checking for updates for some reason