Aw Snap errors on version 120

Kelly_McMahon
Contributor

Is anyone else seeing a lot of "Aw Snap" errors on Chrome OS v 120?   Our student devices are on LTS channel

7 REPLIES 7

bethhughes
Contributor

Ohio school's have been chatting about this issue. Dana Lehman, Highland Local Schools, said it was the 312 security patch for 120. She downloaded the 120 recovery image to powerwash and was at 120.0.6099.272. She found that fixed the Aw Snap issue. So, something in the 312 introduced a bug. There are reports that updating to OS v 124 fixed the issue, too. If you are on 120 and have devices set to auto-update, you might want to block updates until there is a patch or you decide on updating to 124. 

Ivan
New Contributor II

We're seeing this as well. Going to latest seems to fix the issue.

In order to update past 120, we would have to switch to the Stable channel.  Would this cause issues if we switch to the Stable channel and then back to LTS?  I am just a bit unsure about this. Does anyone know? Thanks!

Google Support has a good resource that explains moving from LTS, LTC and Stable. It should help you but you can always contact Help in your GAC if you are uncertain.

bethhughes
Contributor

If you are a school who uses Clever to access apps, they have released this info: 

We have identified the error causing users to encounter a SIGSEGV error when access applications through the Clever Portal in Chromebooks. The root cause of the issue is limited to the Google v120 release. Google is aware of the issue and actively working to resolve issue in the coming days. We recommend not upgrading to the newest v120 release at this time until Google has resolved the issue.

As a workaround, you can either roll back to the .310 or .311 of v120 or move to the v124 in the meantime. We will provide status updates as they become available from Google.

bethhughes
Contributor

Clever status update:
Errors when accessing Apps through Clever Portal on Chromebooks
Incident resolved
Google has resolved this issue and is rolling the fix out in stages for impacted customers throughout the day today. For districts using the LTS channel, Super Admins in Google can optionally update to 120.0.6099.313 now to resolve.

Thanks!  Has anyone tested this out, yet?