rotopenguin
If you're RDPing from a malicious client, how do you know what you're seeing is real? How do you know that your viewer didn't show the same screen for just a little too long while the host popped up a cmd, curl, run, close, continue in the background? How do you know that closing your session isn't "forwarding it to someone else for a bit, but they'll close it when they're done"? One time you start a session, verify it with your phone, waiting waiting waiting, an error occurred try again. Did it fail, or did it go to someone else?
There's another patient who didn't get the toe amputation, and gangrene spread to where he lost the entire leg and 80% of his kidney function. This one did not thank acupuncture for his outcome.
This one very famous case of a guy who got very lucky, and ended up alive and uncrippled and didn't have to take time off from perpetual dialysis treatments to smile for magazine covers maybe doesn't represent what generally happens to people in his situation.
Tim Cook reads every single LOC submitted to his OS.
Use Trixie instead of Sid. With Sid you're getting new packages right as they come out of the oven. If Sid users don't get burned too badly, the packages go into Trixie two weeks later.
pv. It's just cat, with a progress meter.
I believe h.265 has particular handling for "film grain". And it has hardware decoding on just about every chip out there. And you probably already have a hardware encoder, so you can do something like QSV in a reasonable time frame.
300MB for a half-hour is a pretty reasonable bitrate, for one and a half hours it is quite dire.
sl is the single best utility, hands down
The fix is to make it a Ctrl key.
Kinda wish that Valve would just make hall-effect the stock part. My left stick only lasted about a year, while the Gulikit shows no signs of stopping.
First, it never hurts to reboot. There could be some dumb state going on in your display server. Or kernel DRM. Or in some little bs microcontroller in the video card.
Next, read the arch wiki on hardware video acceleration. Contemplate the note(2) at the very bottom of the page and boggle at all the PPANAPAPPI acronyms bouncing around in there.
VLC has two major sides to its video settings, the (Video)output method and the (Input/Codecs)hardware-acceleration. You are on the VDPAU acceleration API, so give VAAPI a try for a bit. Remember you have to restart VLC before any change takes. VLC should be smart about choosing a good Automatic option, but it can't do much about "looks like an API's there, but it's broke".
Try mpv. Try VLC, but from Flatpak (which brings its own version of a lot of the acceleration libraries).
Do the sysreq sometime when your system isn't hung. If it isn't enabled, welp you have to enable it harder.
Having ssh set up would be a way in when the whole graphics stack falls over (but the kernel is still alive in there). On intel there are /sys entries to dump GPU state, ATI probably has something similar. You have a reproducible bug, if you can get in and grab data while the gpu is in la-la-land, you might be able to submit a valuable bug report.