RE: Your edit. Votes are public. OP didn’t downvote you. You, however, downvoted OP when they replied to your question. No idea why you’d do that when all they did was answer your question. FWIW I upvoted your comment so it doesn’t get buried, but yeah, people shouldn’t be downvoting posts unless they’re off topic or against the rules IMO. No need to weaponize them.

The biggest red flag here is that someone is trying to derive meaning from Eva, an anime whose religious/philosophical imagery and themes were used “just because they looked and sounded cool” (not a direct quote.) I mean I like it too, but it’s gibberish.

I’ll say this about OSS and the community around it: It’s painfully obvious at times that while the individuals working on these projects (often thanklessly) are brilliant people, they often lack the communication and project leadership skills necessary to make a project thrive. The last few posts I’ve seen on this particular issue have been extremely vague and for whatever reason just won’t come out and say what they mean. They’re verbose, go off on tangents, and beat around the bush. We must first have explained to us the plots of TV shows, movies, and other ancillary things in order to understand what likely boils down to “people with differing viewpoints cannot find common ground.” I see the linked blog post as nothing more than someone trying to work out relatively complex feelings about the time/effort they contributed to a project they no longer have faith in more than an “expose-eh.” Given that people in the comments of previous threads have boiled the issue with NixOS down to a sentence or two, I think this is an accurate view.

See: Soft skills.

deleted by creator

Check out :set url.default_page and :set url.start_pages.

To have this laundry list of negatives get a reply basically saying “yeah, it’s bad, but we need to impress the stakeholders by forcing a Wayland default even if it doesn’t work correctly” is baffling.

I use SDL so this hits a bit closer to home. Hopefully they can arrive at a conclusion that isn’t harmful to us devs. It’s already kind of a tossup whether it’s even worth it to provide a native Linux build when Proton works so well anyway. I can’t imagine this will help.

Tasks.org is great. I use it with a CalDAV server.

I made it a few hours in on 6.7.9 yesterday after this thread inspired me to check. Still persists and I can now tell if the system is going to hang by starting a video on my second monitor and playing a few minutes of Warframe. The system kind of “stumbles” but won’t crash right away. It might even take a few hours to go down, but I know if that happens then the kernel is no good. Happy you got it sorted, though! Lucky for me 6.6 is LTS for a few more years.

It’s not that widespread as far as I can tell. I gave details elsewhere and included a few other places where people were reporting it. Not sure if it’s tied to AMD GPUs, AMD CPUs, etc., but the common thread is that everyone I saw reporting it was using AMD.

Ryzen 5 2600X w/ an RX580.

I detailed the issue here. Very persistent and tricky issue to track since there’s no reproducible steps and it generates no errors. Happens under zero load, full load, after 5 minutes, 2 hours… it’s about as random and as you can get. And yes, RAM is fine.

Need to give this a shot. I’m still stuck on 6.6 since 6.7 introduced some obscure bug that’s freezing AMD systems.

How’s Kagi?

An unfortunate part of the fediverse is that it attracts people who were too obnoxious for even the more annoying parts of Reddit/Twitter/etc. I’ve made plenty of attempts to “get into” Mastodon and can confidently say that’s a miserable experience across the board if you aren’t willing to do the work to curate your feed. Even if you do get a feed that is free of bad actors, conversations rarely veer off-course from Linux, programming, computers, tech, etc., at which point that’s fine, I guess, but it’s hardly diverse. Also, for all the complaining about “techbros” ruining the fediverse, it sure is full of them.

I have more faith in Bluesky currently. If they’re able to achieve their own kind of federation then I’ll gladly jump ship since their userbase is a lot friendlier and more diverse that Mastodon IMO.

I was just listening to a podcast recently where one of the (tech illiterate) hosts somehow stumbled upon ffmpeg and went direct to ChatGPT to get instructions on how to use it. They said after a bunch of time plugging different commands into the terminal they realized ChatGPT’s output was just close enough to look right but was ultimately “complete gibberish” compared to the actual commands they found via some other resource.

I’ve already stumbled upon a few different help posts on various Linux-related forums where people have messed something up after following ChatGPT. I don’t doubt that it can sometimes come up with useful output, but it’s a real roll of the dice.

Check out Normcap.

I had a rock solid AMD RX 580 up until the release of kernel version 6.7. Now I’m lucky to get a system that can remain up for longer than thirty minutes. Sticking to 6.6 has worked for me and definitely something you should try as well, but it’s worth noting that any amount of time spent on the issue tracker for AMD GPU stuff will reveal tons of issues from 6.6 as well.

I did my first BTRFS setup over the weekend. I followed the Arch wiki to set up what I thought was RAID 1 only to find out nearly a TB of copying later that it was splitting the data between the drives, not mirroring them (only the metadata was in R1.) One command later and I’d converted the filesystem to true RAID 1. I feel like any other system would require a total redo of the entire FS, but BTRFS did it flawlessly.

I’m still confused, however, as it seems RAID 1 only works with two drives from what I’ve read. Is that true? Why?

I started doing this after my phone number got into some kind of crazy scam call database. At the height of it I was getting somewhere in the neighborhood of 30 calls a day, basically rendering the phone unusable.

So I started actually picking up and running these jokesters through the ringer. I’m talking 15+ minutes of pointless conversation, false info, tons of backtracking, and general bullshit. I refined my craft over a few months and would time how quickly I could make them scream at me for fucking with them. At the end of it my phone got taken off at least one of the bigger lists because the calls went to down only 10 or so a day. Now it’s one or two a day at the most, probably from me not answering like I used to.

Favorite call was one guy who figured out I was messing with him and it turned into this general question and answer thing about life in the US. Dude wanted to know how easy it was to pick up chicks and whether or not I’d dated a lot/was married. Great guy, really into Counter-Strike.

I’m fresh off ruling out the RAM via memtest. I’ll let it do a longer soak overnight to see if anything fails then, but I’m now on to bisecting the kernel from what I believe is the last release of 6.6 (6.6.13) to hopefully whatever the offending commit is. Been a while since I’ve had to mess around with manually building the kernel without the aid of linux-tkg, but I’m off to learn it anyway. Thanks for the help!

This is what I’ll try next. I do think memory is the problem now that I’ve had a few more hours of research. Kernel 6.7 has issues with elevated RAM usage, so it’s absolutely doing something funky with memory that might be exposing underlying hardware issues. I also realized my stable kernel was a version or two away from 6.6.13 (6.6.10), so I’m running it now to see if the issue was introduced late in the 6.6 release cycle, which would be easier to bisect than 6.7.

Yeah, the qemu idea was brought up earlier in the thread and it’s very interesting. Glad you confirmed you could repro real issues there in the test environment, so it’s at least a little likely I’ll be able to do the same. Makes sense that it would work and is way better than letting the real system crash and burn. My kernel compile time is pretty short so it shouldn’t be too bad to bisect, I’m just not sure how many commits separate my stable kernel from the bugged 6.7. TBH I’m not that familiar with kernel dev., so maybe it’s way simpler than that.