Freerdp test? I'm curious.
0x0
joined 1 year ago
Downvotes with no replies explaining why? This is happening a lot.
I use qutebrowser and still show tabs, but this is a very interesting approach. Thanks for the rec.
Interesting. I've been developing a game with SDL2 and think I know the stutter you're referencing. I passed it off as an oversight in my rendering code, but maybe it's as you say. Forcing Wayland does appear to work on my test machine, but integer scaling is broken. Might require some more tinkering or proper support in SDL3, but that's the only thing that didn't work OOTB, so not bad.
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.
What kernel version are you seeing that lockup bug on? I have a similar bug on Ryzen 5 2600x with kernel versions >= 6.7. 6.6 is fine.
More directly: Buy used. Lots of reputable sellers on eBay and their returns policy for defective products is unbeatable.
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.
Not the person you replied to BTW.
Very interesting. Thanks for the detailed explanation! I'll check it out.