Oct 31, 2022

Artifacts in google sheets

Probably after update 107 I have issues with using google sheets on HP x2 Chromebook. Appears some strange artifacts after scrolling a sheet. I found some information about disabling Hardware Acceleration that should fix it, but couldn't find it in Chrome settings. Turning off and on device as well as Chrome browser doesn't work. There is still plenty of storage and memory. Reset settings in Chrome browser ddidn't help too.

Locked
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Recommended Answer
Nov 3, 2022
I had this problem and signed out and used Browse as guest. The problem went away. I signed into an alternate account and the problem did not reappear. Then I signed out and back in with my primary account and the problem did not reappear.

I have no clue why that fixed it, but for me, that worked.
Diamond Product Expert lagagnon recommended this
Helpful?
Recommended Answer
Oct 31, 2022
I mean, does changing the channel to beta requires to powerwash the device?
Silver Product Expert Martin Whitehead recommended this
Helpful?
Recommended Answer
Oct 31, 2022
I have seen this issue with an Acer Enterprise Chromebook on the M105 release. 

The workaround was to move that device temporarily onto Beta channel where the issue did not present itself on the M106 release (Beta channel us usually one release ahead of the Stable channel). I would not recommend using Developer channel as this is more likely to be unstable.

By moving the Chromebook back onto Stable channel it will not roll the version of ChromeOS back but wait until the Stable channel matches the version number on the device. If you want to get the device back to the current Stable release of ChromeOS you can use the Chrome Recovery Utility extension.
Original Poster Adam Kortus marked this as an answer
Kudos awarded by Adam Kortus:
Accurate
Helpful?
All Replies (4)
Oct 31, 2022
Hi Adam Kortus

Please see if disabling hardware acceleration in chrome:flags resolves your issue.

- Mike
Oct 31, 2022
Hi, I cannot find a Hardware Acceleration. Please take a look if it is something from this list.




Recommended Answer
Oct 31, 2022
I have seen this issue with an Acer Enterprise Chromebook on the M105 release. 

The workaround was to move that device temporarily onto Beta channel where the issue did not present itself on the M106 release (Beta channel us usually one release ahead of the Stable channel). I would not recommend using Developer channel as this is more likely to be unstable.

By moving the Chromebook back onto Stable channel it will not roll the version of ChromeOS back but wait until the Stable channel matches the version number on the device. If you want to get the device back to the current Stable release of ChromeOS you can use the Chrome Recovery Utility extension.
Original Poster Adam Kortus marked this as an answer
Kudos awarded by Adam Kortus:
Accurate
Nov 8, 2022
Hi all,

I managed to switch to beta and update to 108 which seemed to fix the issue. I then switched back to stable and its rolled me back to 107.0.5304.92

Is it fine to leave my chromebook in beta, I've never done this before?
Last edited Nov 8, 2022
Nov 8, 2022
It is fine to leave a Chromebook on Beta channel although you have to bear in mind that you are one step ahead of the Stable channel.

On option would be to continue on Beta channel until the Stable channel moves onto M108 then think to move back if the issue is resolved.
Recommended Answer
Nov 3, 2022
I had this problem and signed out and used Browse as guest. The problem went away. I signed into an alternate account and the problem did not reappear. Then I signed out and back in with my primary account and the problem did not reappear.

I have no clue why that fixed it, but for me, that worked.
Diamond Product Expert lagagnon recommended this
Nov 16, 2022
Encountered the same issue on a Lenovo Chromebook Duet 3.
Tinkering with hardware acceleration settings (which was suggested elsewhere) did not help.
Switching to Beta channel seems to have solved the issue.
false
6089391820208066117
true
Search Help Center
true
true
true
true
true
208
false
Search
Clear search
Close search
Main menu