rabdom reboot(?) during profile switch

SIGSEGV

2025112101, first time on my memory in 3 years had a strange incident when switching from one secondary profile back to another - the switching screen hanged for 2 min or so, then grapheneOS logo appeared like on boot, and i was back at locked Owner profile.
I just wonder what might have happened here? was it eve a reboot? I havent seen google logo, or yellow warning screen

Novalissoide

SIGSEGV it might have been the graphic UI that did a soft restart for memory. Check your device with Auditor app, make sure the device is updated.

SIGSEGV

Novalissoide
currently i cannot use auditor as i dont have another device.
but i remembered there is uptime data, and judging from that there was no reboot.
so i assume that was the ui restart, but effectivelly it seem to have stopped all running profiles

libertarian

Do you use a Pixel 10? There are some kernel crashes that are sometimes triggered by switching profiles.

I occasionally get hangs, lockups or launcher crashes on a Pixel 8a, I am assuming it is RAM-related.

Novalissoide

libertarian no, OP is on P6a.

Novalissoide

SIGSEGV currently i cannot use auditor as i dont have another device.

official GrapheneOS verified boot key hash is for the P6a this exact line:

08c860350a9600692d10c8512f7b8e80707757468e8fbfeea2a870c0a83d6031

It should show on first bootscreen. Reboot, pause on that screen by selecting top right gray icon. Verify that the line corresponds.

MetropleX

SIGSEGV currently i cannot use auditor as i dont have another device.

You can use remote attestation:

https://attestation.app

https://attestation.app/about

We also know about this issue, it is upstream.

See: https://github.com/GrapheneOS/os-issue-tracker/issues?q=is%3Aissue%20state%3Aopen%20switch%20user%20crash

Unfortunately when they released AOSP 16 QPR1 it wasn't without it's bugs and a lot of getting it into shape for regular use was done by us but we can't cover everything. Possible some of this may be resolved with QPR2 if they gave it some better attention with it being released on time. Possible QPR1 was released due to being under pressure especially due to department head change etc.

SIGSEGV

Novalissoide yep, that one i check on every boot

SIGSEGV

MetropleX i see, there are indeed some issues seemingly about this very bug, like this one https://github.com/GrapheneOS/os-issue-tracker/issues/6247

sad that upstream is not caring too much about multi profile use

Elis

Same thing happent to me 1h ago. Pixel 7a , flawless since 1 year of GOS

grayway2

I can confirm the issue on Pixel 7. I had screen freezing when I switched to a secondary profile (failed , I was switched back after a few seconds to the owner) and phone becoming totally unresponsive (hard reboot was necessary)

grayway2

I freaked out for a few minutes and really thought that the secondary profile was broken and non recoverable. The last update helped a little and I wait a lit bit to unlock the secondary profile after a reboot.