So it works fine as a keyboard everywhere else in your environment, but as soon as you launch Proton, it stops working? I would also guess this is an input device mapping issue.
As a debug step: try and go into the game settings and try mapping a key with the keyboard. See if it registers.
The keyboard itself is fine if I use regular mappings, however in the wootility software they provide (yes they have an official linux version) you can map controller inputs to your keys. So for example I can map (emulate) controller joystick left input to my A key to emulate the analog signal. These does not seem to register in-game. Other key inputs work fine.
Ah, okay. If that’s the case, then I bet the management software is confusing input mapping. Rather, I’m assuming the management software gets in between the keyboard input, and what proton wants to see. If all other inputs work fine, then it’s the management software with a pesudo-device that is causing the issue.
So it sounds specifically like what I said above, and disabling the analog functions puts everything back to normal working order. So, I guess check with their support folks to find a workaround. I’m sure they have one with proton startup flags or something.
Will update the original post but I solved it. Apparently there’s specific gamepad settings inside of Wootility under Settings > Gamepad. There you have to select what type of controller the software will emulate. I just took the recommended (Xbox Controller) and now it works as expected.
I remember watching an early reality show in the 90s/early 2000s. They had Brits, Yanks, Kiwis, Aussie’s etc. One morning they awoke to find their country’s flag burned.
The USA contestants seemed quite angry and the rest were ‘meh’.
Even if you block an instance, you still see comments from that instance and the instance can also still influence your feed via voting. Which means propaganda or what’s worse can still be pushed to people’s feeds.
Just keep that in mind - defederation is a more effective tool, but obviously it should be used with care.
I just mean if an instance turns bad or malicious in some way (through excessive propaganda or any other reason), that’s a legitimate reason to defederate and blocking cannot stop all malicious acts. Defederation is the only method to actually supress it entirely.
That’s not a bad thing I think. If you switch because you still wanted to connect to that instance, that’s good, because you moved to an instance that more closely aligns with your values (i.e. more closely aligns to what you want to federate/defederate to/from).
HAproxy cannot serve static files directly. You need a webserver behind it for that.
Apache is slow.
Nginx is both a capable, fast reverse-proxy, and a capable, fast webserver. It can do everything HAproxy does, and what Apache does, and more.
I am not saying it is absolutely best for every use-case, but this flexibility is a large part of why I use it in my infra (nad have been using it for a decade).
I might be wrong, but since “saddened” would express a change towards more sadness, “consistently saddened” would mean I get sad (or more sad?) every time I see that kind of thing. However, my intention is to say more that the saddening is consistent - every time I see something happens, consistently. I’m not permanently sad, but the way the language is changing is usually making me sad.
I feel like “constantly” might not be appropriate here, but again, I might just not know English well enough myself. To me, constantly would mean unchangingly, meaning I never stop being saddened. In this context, I feel like that means my mood is continuously descending - but instead those are isolated instances of temporary saddening of varying intensity.
Of course, it’s just a lighthearted comment on a meme, but I’d be happy to learn if my understanding is wrong! And, honestly, I don’t mind this kind of slang and internet speak, but it annoys me to see “literally” lose its meaning and gain the actual opposite meaning, that kind of thing.
kbin.life
Oldest