 So, I have a tendency when something goes wrong on my main Linux machine to immediately assume that I can't fix it and distro hop. Like my solution to any solution that I don't know how to fix is to immediately jump to a different distro or reinstall my distro, nuke and pave and start fresh. It's a lazy man solution to every Linux problem. I will put this right out there. It's the best solution if you're a lazy person, if you don't want to fix anything, if something goes wrong, distro hop or reinstall, the problem will probably go away. That's usually what I've been doing for the last six years. If I can't figure something out, I hop. Now there are two reasons for this, one I already mentioned laziness, but also there's this. This right here is journal CTL. Now I have been spelunking through this all day long. And as you can see, there are some errors here and there are some core dumps. If I go up further enough, you'll see where XOR crashed and you'll see where I've had some Python issues. I've had some network manager issues as well. These aren't those, but yeah, I've had some issues and I've been going through this all day long because I wanted to stop my bad habit of immediately jumping away from my distro and jumping to something else when something goes wrong. I wanted to see if I could go through the logs and fix the problem. And I've spent basically a good solid five or six hours today doing this. This is one of those core dumps. This is a Python core dump. Not sure what's going on there. I'm assuming that this has something to do with the problem and I've done some searching and stuff like that, but it doesn't, none of these things, and this is the point of me making this video, is none of these things here make any, none of this makes sense to me, right? And to any normal user, this doesn't make any sense. So over the course of this channel, I've praised the logging mechanism of Linux. So if you use system D, at least, I'm not sure about the other init systems, but if you use system D, it literally logs everything, every single thing it does on your computer, every process that runs, it logs every action. And all of that stuff is here or in some other log somewhere else. And if you are ambitious enough when something goes wrong, you can at least go search out the logs and attempt to discover what's causing the problem that you're facing. So the theoretical awesomeness of logs cannot be denied. But if you're not a technical user, which I'm like halfway towards a technical user, I know some things just enough to be dangerous. But then I come across this, right? Even if you ignore the core dump, and you go up to your two some of the pipe where pulse issues that are really weird, I'm not no clue what's going on there. And then you have the network errors that I've been seeing, those are further up, you know, so I've been, they're all the syntax here, first of all, is not great. But also, if you don't know what's going on or how to read this, you're kind of like it doesn't actually provide you any value. And that's kind of what I've discovered. So I have that MO of just hopping away from distributions when things go wrong. So my problem here is this. So whenever I walk away from the computer, and it doesn't happen all the time, usually once or twice a day, I will come back away from my breaker, whatever, and I'll find that Xorg has crashed. And at first, I thought it was a program that was killing Xorg or killing Q tile. So I searched here through system TT or journal CTL and saw some of the errors that you're seeing here on screen. And you know, didn't understand a word of it, really. So I went to search through the Q tile logs. Now I have some Q tile errors here from earlier in the day that all have to do as far as I can tell with the bar. This is the CPU module on the bar that is causing all these errors as far as I can tell. It might be the memory because they both use PSU, you tell. But the point is that I'm pretty sure that it's not Q tile, but I've been searching through these logs and I'm trying to figure it out why Xorg crashed. And I looked through the X sessions errors, you know, log, which is in the home directory, there is literally nothing in there, which is surprising because there's always something in there, you know. So I've been trying to fix it. I've been trying to change my habit of moving away from a distro when something goes wrong because I wanted to try to fix it. But the logs are gibberish to me. I don't know what they mean. And even though I can take snippets of them and search through Google or search through Brave or whatever and see if I can find the answer, I'm not sure if the thing that I'm searching for is actually the problem because I have no clue how to parse what's going on there. So the point of my making this video today is twofold. First of all, I'm moving back to Fedora. So as my main distribution, I'm going to be happier on a more stable system than I am on Arch. I'm not sure if they'll fix my problem because if it's a Qtile problem, I may end up having the same problem with Fedora. I don't know if that's what will end up happening. Maybe I'll end up having to abandon Qtile. That'd make me very sad, but we'll see. See, this is not such a problem that has caused me so much issues that it makes me want to hop. That's why I tried to fix it because it only happens like once or twice a day. And it's fine. I can deal with that because it doesn't happen all the time. But it's annoying enough that I wanted to fix it. But the point is, is that it always seems to happen when I'm doing something. So the other day I was using Whisper AI to create the transcript for the podcast. It was literally five minutes away from finishing. Like you probably never used Whisper AI before, but it takes a long time, especially when it's trying to transcribe audio into a transcript of something that's two hours long. Usually takes about six to seven hours to do that, even on a powerful machine. Mine was five minutes away from doing it, finishing that transcription. And when I got up to go do something, and the computer was ex-workhead crash when I came back and there was no transcript. So at that point, I thought it was Whisper that caused the problem, right? Today, no, the other day, the next time, I was rendering a video. I was running a video in Caden Live. And when I came back to check to see how the progress was doing, it had crashed. So I had to render again. So it's always happening when something is happening. So I've spent some time trying to fix it and I'm giving up. Like I'm reverting back to the norm of me just hopping away. And it just seems to be the best solution because I don't know how to fix it in finding the issue. Sometimes you just can't find the issue even though the information is probably there, right? It has something to do with those core dumps. It has something to do with the network manager stuff that's going on. It may have something to do with the PSU util thing that's going on, or the PSU till thing that's going on in Qtile. I don't know, like I have no clue how to parse those errors to get to the answer that I need in order to fix it, right? I need to know what's actually going on. And like I said, the information is there, but it's not in English that I know how to read. So I'm moving back to Fidora. The second and more important thing that I wanted to, you know, the second most important thing that I wanted to talk about in this video in terms of the point is that sometimes despite your effort, sometimes despite the effort of trying to fix the problem on Linux or, you know, on Windows or Mac or whatever, sometimes you just can't. Sometimes nuking and paving, sometimes distro hopping or reinstalling your distro, whatever, is the best solution. And usually that's not even when they're... Usually it's not when your distro is completely broken. Like, say, okay. So usually how I'm trying to figure out the best way to say this and I'm having some issues, as you can tell, speaking is not my forte. Usually when you have a system that's completely broken, the obvious answer is to reinstall. But that's not the only time when that's the obvious answer. The usual... For me, the obvious answer seems to be when you've spent enough time on trying to fix the problem and it no longer provides you value to continue to try to fix it and it makes more sense to spend your time just resetting up your system and getting your work done than trying to continue to fight with the logs, try to fight with every single problem that's going on to fix the issue. So I'm at that point. I no longer want to spend time on this issue. I'm done with it. I've tried to find the issue for many hours now and I've come up with some vague idea of what's going on. But I could very well be wrong and I'm at the point where I'm done. Now, here's the thing. I am a person who owns multiple computers. I spend a lot of my time on the one that's in front of me. It has multiple hard drives on it. It has Debian on the other drive. So I spend some time in Debian every single day because I'm doing a long-term review of it. And the computer behind me is my standing desk where I try to spend some time every hour or so and that's running ArchCraft right now. It has been for a very long time. Actually, that's a very strong or a very stable distro or at least it has been, mostly probably because I don't use it as often as I should. You know, it's only a few hours a day. So I have the luxury when something goes wrong to not even distro hop, I can just pull out of this particular hard drive and go to a different one and use Debian for a little while and get some work done. That's what I've done several times today because I can't trust this one not to just randomly shut down or randomly pop me out back to the display manager. And I have to kind of be able to trust it. And I wanted to fix it. I really desperately wanted to fix this. And I'm sure if I spent another day on this and did some more searching and consulted some people in my Discord server or did some tuning or whatever to the people who are way smarter than me and asked for help, I probably could fix it. But I've spent enough time on it now. It's time to go to a more stable system. So Sayonara Arch Linux, it's been nice knowing you. And the question is, am I gonna miss the AUR? I asked this question the last time I went to Fedora and was very happy for a very long time in Fedora. Didn't miss the AUR at all. In fact, I went so far as to make a video saying that the AUR was overrated. So I guess I'm gonna go to Fedora and see if that's true. Now the question is, do I go immutable or do I not go immutable? That's the question. So, and I'm not gonna answer it. Well, you guys will have to find out later. That's it for this video. If you have thoughts on the mess that is logs and the mess that is sometimes just, you know, fixing Linux, you can leave those in the comment section below. I'd love to hear from you. You can follow me on Massadon or Odyssey. Those links will be in the video description. You can support me on Patreon at patreon.com slash Linuxcast. If you're still watching this and you haven't already dropped a like on the like button, I'd really appreciate it. It really does help the channel. Thanks everybody for watching. Thanks everybody who does support me on Patreon and YouTube. I totally messed that up. Anyways, thanks for everybody who supports me on Patreon and YouTube. You guys are all absolutely amazing. Without you, the channel would not be anywhere near where it is right now. So thank you so very, very much for your support. I truly do appreciate it. Also, I'm only gonna do minimal edits on this video because I'm running out of time to get one up today. So yeah, if the editing wasn't up to my normal, you know, editing is such as it is, I apologize for that. So thanks for watching. I'll see ya next time.