Why would I care about swaying your opinion? Nobody here responding to you is invested in YOUR opinion on the matter, or cares what you think about it. They are simply correcting your misinformed attitude about some things from what I can see.

If anything they’re concerned you’re running around in the world with misguided opinion, and potentially misinforming others.

You sound new to the ecosystem at large, and I don’t mean that to be condescending, just that you may not have all the context needed to understand why it exists. Any distro that exists right now can flip back to SysV if they want to. They just don’t want to. It may be more flexible to the neckbeards, but it’s massively more comprehensive in scaling and integrating than a set of Init scripts. It has huge benefits to system integrators, OEMs, and especially the people who manage the largest concentration of Linux deployments: Datacenter Ops teams.

The fact that you, a Desktop user takes issue with that is meaningless to the ecosystem at large. I manage thousands of deployed bare metal machines, and I’d never switch back, because it SysV was fucking painful. Sure it was easier to debug in some cases, but was it as useful or reliable? Not even close.

Just go use something else and stop letting it bother you. You’ll feel better in the long run.

It’s Open Source. Nobody needs to use it, and it’s especially not all-inclusive. That being said, it’s also not new at all as it’s been around in most distros for well over a decade. It has its pros and cons like anything.

Your assumption that “freedom” has something to do with Linux writ large is misguided though. You have distros that have communal decision making, and if they find a benefit to systemd, then they’ll use systemd. Don’t use that distro if you don’t like it. There’s your freedom of choice.

The dependency chain for building the entire kernel depends on what you included in the feature set. The reason it probably worked on Ubuntu is because the build-essential package covers the most common deps needed to build the kernel.

Need output to be able to tell you anything. Post the errors.

Regardless, if you’re building something without a purpose, assign it a dedicated purpose instead of just making it some other running machine.

You literally say in your post you’re building another machine.

Make it a single purpose machine that does the thing you need it for.

Separate the use-case here:

1. For your desktop, whatever works. There is no one distro that gives you some leg-up on performance or anything else. You can install the same software on all, and the kernel is largely the same.

2. Just get or build a NAS for hosting media. A Synology or Qnap has a bit of added cost, but the maintenance overhead is reduced by a LOT versus running TrueNAS, OMV, or similar. That being said, choose the right tool for the job, and don’t just run Debian for this purpose because it just adding admin overhead you don’t need. This probably has been solved from your specific angle. What you want is simplicity in maintenance. Being able to hotswap and repair a failed drive means a huge win.

They have a simple bash installer from what I see. You can also install everything via pip as well. Couple quick commands.

That bug report mentions a few versions, so maybe just go back to whatever version was working on your other machine.

This looks like a sandboxing issue. Using the “no-sandbox” flag has never worked on AppImage from what I remember, except for very light runtimes. Running with sudo will throw that error because the root user has no display manager running.

Just try running the installer if you don’t want to mess around with debugging the AppImage. Check the GitHub Issues for related keywords and see if others are running into the same issue, maybe it’s just a specific release, or SELinux causing the problem.

Linux has been the most prolific OS on devices for 25 years, friend.

Not important enough for people to not spend $500-600 on a MacBook instead of sticking with an antique PC they wish to keep running. That’s my point.

Costs less than a phone from the same company.

I feel like I’m insane for having to constantly reassure people on this fact, but…

LINUX IS THE MOST DEPLOYED OS ON THIS PLANET

Desktops are just software on top of Linux. The OS itself is superfluous. It’s in your TV, router, car, toothbrush…etc.

Who uses what for desktop matters very little except to the people making the desktop experience. The only thing on the horizon that is going to make a huge dent in the numbers you see reported on Steam, are Valve’s new hardware.

Meanwhile, many EU government operations are switching to Linux as fast as they can move their little fingers, but you won’t see that reflected on the stats you’re paying attention to.

Go back 20 years. See how many times this prediction has been made 🤣🤣

The only shift now is Microsoft shitting the bed so hard that people don’t want to deal with them. The difference this time is the MacBook Neo.

People would gladly pay Apple $600 for a working machine WITH support and stores everywhere to get help if they have hardware issues. It’s the new iPhone business model. They’ll be taking more desktop market share than people even imagine on the price point alone.

If you’re getting file verification errors, it probably means there are issues with files on one end of the other.

So a few things:

1. What’s this remote machine, and have you checked the filesystem recently?
2. Have you checked the filesystem on your local machines you’re copying files from?
3. Have you tried copying to an empty remote.traget directory and seeing if you still get these errors?
4. If 1 & 2 are fine, and then 3 works without problems, make a short list of some of the files that are throwing errors. Do they happen every single time at these same files? What’s unique about these files?

Versions should be fine. Your options matter though, so send the full command you’re using.

Also try this:

1. Open one terminal window and run a ping at your remote machine and let it keep running
2. Open another term and run your sync. See if ping lags or delay issues start when the rsync issues start in both windows

Kind of sounds like you have a rogue process engage the Wayland API to take exclusive control over something. Maybe you’re running multiple video apps that take input from your camera or streaming device at the same time, like Discord, Zoom, and OBS all running at the same time. One has exclusive access while you stream, but then another engages the same device and takes control for a split second, killing the other apps access.

If you have an Nvidia GPU, run nvidia-smi in your terminal and it will show with prices are engaging the GPU.

For AMD any process monitor should show GPU usage for procs, or there is radeontop for more detailed info.

Have to see it live to be sure, but it sounds like potentially you’re getting an update while the machine is running, and you haven’t rebooted to load the new GPU module.

Jaguar with 4GB of RAM. It’ll do all the normal desktop stuff and games up through maybe PS2 no problem.

Make sure you add at least 4GB of swap though.