3 ms·
If the same thing happened in X trying to render an i3 background, for example, the way you'd recover is starting a new session - which you've proactively setup
by OJFord 6y ago
If the same thing happened in X trying to render an i3 background, for example, the way you'd recover is starting a new session - which you've proactively setup to not launch X automatically - and inspecting logs and configs to see what went wrong.
It's basically the same thing here, but without some physical keys bound to 'switch to new session'. And maybe you can do that over adb anyway, which is about as (not) normal user friendly.