I had a power cut yesterday and it knocked my servers offline. Now one of them is complaining that fsck can't find a UUID and can't boot properly. Guess what? No SSH, no console speech. Thanks, Linux. Now I have no choice but to use AI to fix it or wait between several hours and several days to get a sighted person in. After all, we all have perfect vision and can read the video output which is still functioning. Linux is for everyone, amirite? Grandma's totally gonna be able to figure out wtf udev is when Mint shits the bed after the power goes out during a storm and she'll totally remember to swap the cells out on her UPS every 2 to 3 years
Update: I was able to fix it with a restart. No rescue image needed, but it did complain a lot about being unable to set up my user, so I need to go in and see if anything got borked. Incredibly annoying that, when something went wrong, I just didn't have any of the accessibility tools that I explicitly configured

@PepperTheVixen Yikes. I wish we could come over and help.

It'd be nice if serial terminals were a common feature to have, and some kind of serial TTS device, because I bet that would work during early boot (being designed for debugging and all) but good luck not only getting the hardware for it, but also helping Mint Grandma figure that out...

@PepperTheVixen and this is why many just stick with windows or mac.
@bigpawedbear @PepperTheVixen do BSODs or Mach kernel panics have accessibility features? I’m pretty sure Windows and macOS are just as bad at accessibility if the filesystem is to corrupt to boot