I haven’t noticed any dropped inputs or anything myself (also bazzite, though I rarely use big picture mode).
To pair the on screen instructions said to connect the controller with a cable separate from the puck. Just connecting it to the puck didn’t work.
(Also I don’t really see the issue with needing to confirm on the device. Surely you had a way to control it before this controller arrived?)
If the package id and signature are still the same this used to be the case. But even back then, an F-droid release would usually at least have a different signature, maybe a different package id as well.
No I totally understand. This is why I use podman personally. You can use the same images as you would with docker, even its compose is pretty much exactly the same I think.
Docker automatically opens ports your containers need through iptables. Because of this, it bypasses rules set by ufw, which is great.
Podman does not do this afaik, and since it only runs rootless it’s a lot less risky as well.
I don’t believe Solaar can change RGB settings, but OpenRGB seems to support quite a few Logitech mice.
Jesse what the fuck are you talking about
The reason is very simple, performance. If a value doesn’t need to be changed, don’t declare it as mutable. This isn’t just a front-end thing btw.
In that case the full thing would be const fun = () => {}
I just reinstalled linux and this time for some reason it paired by just connecting the puck. Previously, the instructions explicitly told me to plug the controller in with a separate USB cable.