this post was submitted on 12 Jan 2026
11 points (86.7% liked)

Linux

14827 readers
348 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

I’ve recently installed Mint on a clean partition, and set up dual booting to always prefer that partition over the Win10 one (on a separate sdd). At the moment I’m trying Mint for the very first time, seeing how I like it. And truth be told, it’s quite good! However I’ve had 2 system crashes in the last 2 days, and some games crash without an error log (old world went straight to desktop while mid-turn, and ghost of Tsushima crashed after I paused the game when pressing start).

I’d love to be more knowledgeable and figure this out by myself, but I can’t find a starting point to determine what went wrong in any of these instances.

Are there execution logs or actual error logs that I can check somewhere?

you are viewing a single comment's thread
view the rest of the comments
[–] kumi@feddit.online 1 points 11 hours ago

Oh, I see now that by "crashes", you mean your whole system freezes?

Normally you might not have kernel logs left after that. In preparation if you think it might happen and want to gather the kernel log, you can put up a shell in the background and let this run: sudo dmesg -Tw | sudo tee -a /var/log/mykernel.log