20 comments
@gamingonlinux nope never been there after an update, been there because of other self sabotaging Heh. I ... don't have enough room in my / folder to hold the upgrades anymore and the entire drive is encrypted. I'm not far from having to bite the bullet and Do a reinstall to keep upgrading. 8 years worth of files, writing, collections etc.... Been there and done that. And on an reinstall you hope you got everything you needed to copied to another drive.... @gamingonlinux I don't recall ever having this issue on my Ubuntu daily driver, but my Windows gaming PC that I turn on once a month definitely does this. ๐ฉ EDIT: To be fair, the last time this happened it was because my FreeBSD server needed its samba jail restarted for... some reason. @gamingonlinux only once nearly 20 years ago with an experimental driver @gamingonlinux The worst I ever ran into was a system that, after updating, blinked between a getty login prompt (no gdm) and a black screen. And when the screen was black, it didn't respond to keyboard input. My best guess is that it had fallen back to framebuffer mode, but for some reason the kernel was taking an extremely long time to render anything, which hard locked the kernel until it was done drawing the screen. Reinstalling the latest version of my OS fixed this. โIโm updating my Arch box. Iโll be back in either five minutes or this weekend.โ @gamingonlinux I switched my default shell to fish and it broke KDE completelyโฆ had to set it back to bash. ๐ญ @gamingonlinux I have Ubuntu and Manjaro installed on 2 different drives with shared home folder (parts of) and shared folder with steam games. If one linux dies, I switch to another one. @gamingonlinux 30 years of using Linux on desktop and I can honestly say, only with Arch based distros. Linux, over the years, has given me a lot less trouble than Unix did. But yeah, my scotch consumption tripled working with SysV @gamingonlinux Never been there. However like the video! :BigBlobhajHug: In all honesty, the last time I had a not-working screen was when I was shortly using the Android stock OS before returning to GrapheneOS: seems I made the right choice. :BlobhajHoldSassage: I don't think I've ever been there. Closest I can think of is password cursor freezing and having to switch to TTY to restart sddm. This has happened a lot. @gamingonlinux It ain't Real Broke until you have to drop into the root console and manually mount the boot device |
@gamingonlinux ooof, yep. More like a sinking feeling of dread in my experience.