Hey guys. I’ve been having an ongoing problem with my desktop where, when it goes into suspend, it’ll shut down instead of waking back up. Not a hard shutdown, either, but what appears to be a proper shutdown where everything gets nicely SIGTERM’d and everything.

Now, I’m saying all that just in case it’s related to what happened today. I stepped away from my machine after having it play Youtube videos through the night and came back to it about an hour later to find that it had been shut down. There was no indication of an improper shutdown, either, since the usual “hey, you hard powered off and now your disk needs to be fsck’d” messages weren’t there. The logs stop right before when I assume the shutdown happened, but there’s nothing in them that really sticks out as a possible reason for why it would have happened.

Getting to the point, is there somewhere other than journalctl and dmesg that I should be looking to try and figure out what happened? I’m on Fedora 43, and I’m happy to provide whatever logs are necessary. I’m really hoping it’s not a hardware fault, but I’ve had other problems that seem to indicate the PCIe port on my motherboard starting to go bad such as inexplicable static on one monitor and my GPU disconnecting whenever my cat jumps down from my lap too hard.

  • kumi@feddit.online
    link
    fedilink
    English
    arrow-up
    16
    ·
    edit-2
    2 days ago

    Unless you took a backup I guess it’s not relevant anymore but if it happens again you can narrow down files last changed around some timestamp like so: find /var -mmin +4 -mmin -5

      • kumi@feddit.online
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        1 day ago

        In the offchance that shenanigans are afoot, some malware will fudge mtimes (but not always ctimes) to prevent detection.

        If you get files showing up as changed with -cmin but not modified with -mmin, that’s a bright red one.