I previously thought it was a Gala issue, but ever since I disabled autolock it seems not to happen.
The issue - If I have a large chunk of my memory being used, or maybe all of it, the fade-to-lock seems to cause a permenant blackscreen after logging back in, regardless of whether its woken from suspend. The cursor remains fully functional, but apart from that there is not interaction, whether that be trying to change brightness or volume (trying to suspend seems not to work either)
For now it seems to be fine as long as the autolocking is disabled, but that's not really a solution.
meisenzahl
commented
3 years ago
I previously thought it was a Gala issue, but ever since I disabled autolock it seems not to happen.
The issue - If I have a large chunk of my memory being used, or maybe all of it, the fade-to-lock seems to cause a permenant blackscreen after logging back in, regardless of whether its woken from suspend. The cursor remains fully functional, but apart from that there is not interaction, whether that be trying to change brightness or volume (trying to suspend seems not to work either) For now it seems to be fine as long as the autolocking is disabled, but that's not really a solution.
Lenovo ThinkPad X240 (w/ integrated intel graphics, stock Mesa, 4GB of memory) elementary 6 Odin daily
Edit: I seem to be able to replicate it sometimes by manually locking too