I’ve recently got my PC up and running again but today it’s rebooted randomly twice. What could this be a sign of? All advice is welcomed and appreciated. Thanks in advance.

  • Broadfern@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    3 days ago

    How new are you to Linux?* /gen

    Have you checked the output of, say, “journalctl -b -2”? This would give you a system log of messages that go back to two boot sessions ago and normally show you what happened just before that first shutdown.

    This could be drivers, background processes, hardware, no way to know without starting by looking at logs. Hell, I’ve had a monitor crash out my system multiple times and I wouldn’t have ever guessed if I didn’t check my logs and dmesg output.

    * to get a better sense of how to help you

    • SpiceDealer@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      24 hours ago

      First, sorry of the late response.

      Second, running that command with the -r parameter it returns this:

      Feb 13 17:24:45 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:24:45 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:24:45 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:24:45 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:24:33 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:24:33 [user]rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:23:31 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:23:31 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:22:46 [user] wpa_supplicant[957]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=999>

      Feb 13 17:22:34 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:22:34 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:22:08 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:22:08 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:21:24 [user] flatpak[9501]: (17:21:24) INFO: [Gog]: GOG presence set

      Feb 13 17:21:23 [user] flatpak[9501]: (17:21:23) INFO: [Gog]: Running command: GOGDL_CON>

      Feb 13 17:21:20 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:21:20 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:59 [user] wireplumber[1097]: wp-event-dispatcher: <WpAsyncEventHook:0x5be0f8feaff0> failed:>

      Feb 13 17:20:34 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:34 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:23 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:23 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:23 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users.

      Feb 13 17:20:23 [user] rtkit-daemon[1064]: Supervising 10 threads of 6 processes of 1 users. lines 1-24

      • Broadfern@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        23 hours ago

        All good. From my non-professional perspective so far it mostly looks like real-time-kit is pretty active, which seems to be primarily for enabling audio.

        Are you having issues with audio? Or are you maybe having trouble with GOG after you start it?

        • SpiceDealer@lemmy.dbzer0.comOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          21 hours ago

          Kinda of. About 6 months ago, my speakers stopped outputting sound from their proper port on the I/O. Speakers themselves still worked as connecting them to the headphone port produced sound. When I put my PC back together about two weeks ago the sound problem persisted but this time switching sound profiles in the sound setting then switching back to the default, strangely, fixed the problem. It came at the caveat that I have to do it every time at reboot.