sudoBash418

> [phoboslab/qoi#71 (comment)](https://github.com/phoboslab/qoi/issues/71#issuecomment-991884414) has some numbers on wrapping with LZ4 instead of Zstd, on the entire test suite. LZ4 seems closer in spirit to QOI (byte-aligned ops, relatively simple format,...

Here are my results, using qoiconv from phoboslab/qoi@2ee2169 (master). Compressors are sorted by total filesize, descending. Compression Results (kB) | | TOTAL | icon_512 | icon_64 | photo_kodak | photo_tecnick...

> So qoi + the top compressors already beat the top optimised PNGs. Arguably the PNGs could be crunched slightly further, but then so can qoi if we go off...

Just tested with 2.4.0, still having the issue (attempting to access a WinApps VM). - Cinnamon 5.0.5 - freerdp 2.4.0 - Arch Linux

> I'm using Pop OS however, I'm not sure if making the key SUBSYSTEMS and ATTRS is what fixes the issue over on Arch. I can confirm that using `SUBSYSTEM`...

I recently ran into this issue as well, but only realized after recording many hours of video. I was able to mostly recover the files by using `ffmpeg` to change...

I'd love to see this implemented, as it can a pretty big security hole in my opinion (depending on use-case). FWIW, I [tried implementing](https://git.sb418.net/sudoBash418/pyinfra/commits/branch/private-temp-directories) a similar feature against pyinfra 2.4...

I think this should be fixed by https://github.com/pyinfra-dev/pyinfra/commit/9b6c214effb75b4c485b3766a135bae26029edbd? (not yet released)

Not sure if this will fix your issue, but I was facing the same error and fixed it with the following udev rule: ``` # CMSIS-DAP for microbit SUBSYSTEMS=="usb", ATTRS{idVendor}=="0d28",...

> I assume this wouldn't apply to hex numbers? I don't think `0xffpx` would be a great idea. Counterpoint: having `0x0123u16` work would be neat.