I think you misunderstood the previous comment. Not the devices need to be configured correctly, but the network they're connected to.
fallingcats
ln -sf /bin/nano /bin/vi
Understandable. I don't know how the federation thing is supposed to work, but I do believe Jerboa pulls them from the source when I browse All
, which might be part of the issue.
{"code":"not-found","msg":"No such file or directory (os error 2)"}
What?
They probably only used the sensor while unlatched, now they use it while supposedly latched too.
They didn't even show how well scrolling works. I suppose that's an indication that it's pretty laggy
Many mice can scroll sideways by tilting the scroll wheel. If that's something you use often enough, maybe that's something to consider
Clearly you don't know the first thing about Wayland. If you run an application without a sandbox, of course it can execute commands. That's just common sense. Qt themes are also kind of an application. Now that's where the fault lies, not with the protocol applications use to interact with the compositor (Wayland).
Microsoft announced they'll have a floating panel days or weeks after KDE did it
Firefox has that, but it might not be enabled by default
Really? It was very noticable to me when I didn't have screen tairing anymore