It won’t work.

Like every these, repetition is key, and also stepping through each idea to get to an outcome.

Good luck to you though.

It’s not about “Linux Users”, it’s the fact that the issues described are MIS-identified because the operator who claims to be proficient in technology has zero idea what in the hell they are talking about.

Knowing how to navigate the Windows OS is like 2% of what a “technology guru” (this guy said it) needs to be fluent in. Windows in 2026 is more irrelevant than it ever has been since 3.1, and this guy is acting like becau6his fluency is in Windows he’s has some knowledge about computers in general.

He then goes to explain IN DEPTH AND DETAIL how he does not.

Rag on me all you want, but this is not a Linux person being a gatekeeper or withholding. This is a person with little technical knowledge missing the point and misrepresenting themselves.

Fuck this guy.

Hoping this is scripted and a joke.

Dude has zero idea how computers work, and is presenting as a “tech person”?

Use whatever you want, but don’t be an ignorant asshole and put shit like this out of you have no concept of the topic aslt hand.

What a dumbass.

Systemd is fine. Stop getting trolled by antiquated neckbeards.

Unless you find a specific problem with something, don’t go looking for reasons to fix that which is not broken.

In this case you’re just seeing the App image container and it’s subprocess as two different processes. If you kill the AppImage process, it SHOULD kill the subprocess unless there is something whacky going on with how they spawn it.

It may also be different if for some reason sudo is being being used in the mix here.

What a fucking joke. I hope this goes down in flames from the get-go, but I know it’s going to bounce high on the first day, defying all logic.

This company will never make an actual $1 Trillion fucking Dollars.

Kill signals have different priorities in Linux. The default should be to ask it to kill itself and cleanup nicely, which may or may not work. If you want to be absolutely sure it dies every time, you want to use pkill -9 whateverprocess.

List of signals

I did. Which is why I commented. You literally said “there are no wrong answers” 🤣

You’re going to be super disappointed to learn that most people who have been using Linux as daily driver for decades just use whatever works. Linus himself just uses Fedora.

Nobody that has real shit to do wants to worry about things not working or causing issues. Immutable is pointless, Nix is something I use for work, Ubuntu is dead to me…etc.

Or played Metal Gear. WTF.

🤦…here we go again

Somebody’s about to do something fucking horrific again.

Not sure what you even mean, but OP seems to be struggling with just installing Wine.

99% of everything should work right off the bat with any Prefix Manager, and only in RARE cases does tweaking Wine directly ever come into to play.

I think you have it backwards.

Honestly, unless you know exactly what you’re doing, I wouldn’t run Wine directly.

Use a Wine Prefix manager like Proton, Lutris, Heroic …etc. It makes everything pretty dead simple, and keeps all your Wine stuff isolated.

Nix is simply a different distro with a declarative composition for its package management. You won’t be getting different behavior from package selections or anything like that if it’s a bug in the software itself.

Just letting you know.

It’s no hard to break than anything else. I’m not sure you understand what the issue is here…

In what ways to they fail? I’ve used LibreOffice forever and don’t have any specific complaints, but I’m definitely not using any of the more advanced features.

Every modern distro keeps previous kernel boot entries available at boot time. You don’t need to use snapshots to simply not boot a potentially problematic kernel update.

There are literally near zero reasons to ever have to reinstall any Linux install. Moving to a more complex distribution isn’t going to solve your problem here, which is just learning a different workflow. That workflow being more akin to software development workflows: if something fucks up, just revert.

If I get a minute I’ll see if I can replicate, but my initial guesses are:

1. Hardware cursor mismatch: try disabling hardware acceleration on the client OR see if there is a setting for forcing or disabling hardware cursors
2. Check the CLI arguments for cursor specific options and mapping to movement. Sometimes there are movement acceleration tweaks that mess things up

Edit: also maybe give this a shot. https://www.azdanov.dev/articles/2025/how-to-create-a-virtual-display-for-sunshine-on-arch-linux

Not sure what you mean about the mouse cursor not showing up. You mean you can interact with the mouse, but just see a cursor? Or no matter which direction you move the mouse the cursor doesn’t get there?

You sure after setting up the virtual display you’re going through the steps to setup the orientation of monitors?

You can still get GL.inet routers even on Amazon as of right now, and they’re on sale (for obvious reasons).

There’s the OpenWRT One router that is basically just a Banana Pi board.

There’s lots. Just search around.