30
[Arch/EndeavourOS] Random reboots
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Feb 2026
30 points (96.9% liked)
Linux
62524 readers
107 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
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
-rparameter 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 setFeb 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-24All 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
-rto show the log in reverse order.