honestly, you should give less info. what's your hardware? what PSU? drivers? X11, wayland? what's that "running again" business, what was the issue before?
this post was submitted on 11 Feb 2026
31 points (97.0% liked)
Linux
62784 readers
161 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
What do the system logs say? "sudo journalctl -b-1" after a reboot and jump to the end.
Following the advice of @MagnificentSteiner@lemmy.zip, I added -r to the line and got back this:
Feb 13 18:39:31 [user] wireplumber[1081]: wp-event-dispatcher: <WpAsyncEventHook:0x629b62872910> failed:>
This was the very last (or first?) line. If more info is needed, just let me know.
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
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
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?
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.
FYI you can add -r to show the log in reverse order.
I bet you it's a hardware issue.
Run Memtest+ to check the RAM first...
Might be a PSU / heat issue....
Make sure the fan is not full of dust. Clean it out if it is. Most systems shutdown/reboot if it gets overheated.
Make sure your RAM and all other connections are properly seated. I’ve had reboots in the past because a stick of memory wasn’t fully seated, even though the clasps were locked in place.
Is there anything in the journal? If you're not familiar, try something like journalctl -o short-precise -k -b -1 and then look for anything weird.
It show this:
Feb 13 18:40:29.912947 [user] kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=0000:00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
And this:
Feb 13 18:40:34.855192 [user] kernel: nvidia-gpu 0000:24:00.3: i2c timeout error e0000000
Feb 13 18:40:34.855523 [user] kernel: ucsi_ccg 6-0008: i2c_transfer failed -110
Feb 13 18:40:34.856313 [user] kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110
Feb 13 18:40:34.857464 [user] kernel: ucsi_ccg 6-0008: probe with driver ucsi_ccg failed with error -110
Edit: And this:
Feb 13 18:40:34.855192 sam-ms7b93 kernel: nvidia-gpu 0000:24:00.3: i2c timeout error e0000000
Feb 13 18:40:34.855523 sam-ms7b93 kernel: ucsi_ccg 6-0008: i2c_transfer failed -110
Feb 13 18:40:34.857464 sam-ms7b93 kernel: ucsi_ccg 6-0008: probe with driver ucsi_ccg failed with error -110
Feb 13 18:40:35.256841 sam-ms7b93 kernel: iwlwifi 0000:28:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1
Feb 13 18:40:37.136726 sam-ms7b93 systemd-journald[596]: File /var/log/journal/347a826f389a4d8f832a34bd1283f6a3/ user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 13 18:40:37.774864 sam-ms7b93 kernel: nvme nvme0: using unchecked data buffer
Feb 13 18:40:40.538835 sam-ms7b93 kernel: wlan0: VHT information is missing, disabling VHT
Feb 13 18:40:40.542833 sam-ms7b93 kernel: wlan0: authenticate with 54:be:f7:d3:d0:98 (local address=ac:67:5d:fd:29:d8)
Feb 13 18:40:40.542853 sam-ms7b93 kernel: wlan0: send auth to 54:be:f7:d3:d0:98 (try 1/3)
Feb 13 18:40:40.610840 sam-ms7b93 kernel: warning: kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211`
Feb 13 18:40:40.672835 sam-ms7b93 kernel: wlan0: send auth to 54:be:f7:d3:d0:98 (try 2/3)
Feb 13 18:40:40.675837 sam-ms7b93 kernel: wlan0: authenticated
Feb 13 18:40:40.675864 sam-ms7b93 kernel: wlan0: associate with 54:be:f7:d3:d0:98 (try 1/3)
Feb 13 18:40:40.696831 sam-ms7b93 kernel: wlan0: RX AssocResp from 54:be:f7:d3:d0:98 (capab=0x411 status=0 aid=1)
Feb 13 18:40:40.700846 sam-ms7b93 kernel: wlan0: associated
Feb 13 18:40:40.749843 sam-ms7b93 kernel: wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by 54:be:f7:d3:d0:98
Feb 13 18:41:18.320172 sam-ms7b93 kernel: ntfs3: Enabled Linux POSIX ACLs support
Feb 13 18:41:18.320369 sam-ms7b93 kernel: ntfs3: Read-only LZX/Xpress compression included
Feb 13 18:41:19.837143 sam-ms7b93 kernel: ntfs3(nvme1n1p2): It is recommened to use chkdsk.
Feb 13 18:41:19.839148 sam-ms7b93 kernel: ntfs3(nvme1n1p2): volume is dirty and "force" flag is not set!
lines 1327-1350/1350 (END)
Huh, nothing super jumps out to me as an obvious tell, but the last bit is talking about some weird stuff with NTFS. Do you have a drive with Windows or formatted by Windows mounted maybe? Something could be up with that drive, or if you're using it for something important to the system that could be a problem. You can just follow the recommendation in the log and use chkdsk on it but that could potentially be destructive to the data on the drive so be careful and make backups if needed.
Up and running again suggests it wasn't running before. Why not and what did you do?