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.

This is for the client display only, and not the iOS API interface as I’m discussing. It’s not very plainly laid out in the docs, but one would assume any queuing of content into the notification system would be stored or cached if not cleared. There doesn’t seem to be a way to have a client of that system to clear it’s own data once it’s in there, just cancel last notification.

Clever. Not much you can do for this except not subscribe your app to the notifications API, or take extra steps to attempt to clear them, but I don’t remember that being an option on iOS. Going to be an interesting fix.

This guy loves Ayn Rand

If you’re too fucking stupid to realize that your vote ABSOLUTELY DOES FUCKING PREVENT SHIT LIKE WHAT WE ARE DEALING WITH RIGHT NOW, you need to go elsewhere and experience the world. You’re too ignorant to be here and participate.

🤣

My gawd. The hoops you jump through. Just take the L and walk on, slugger.

An example:

Application Payload = 100MB AppImage all inclusive image with deps = 175MB Flatpak App Layer = 101MB Flatpak Deps = 75MB

Now say you’re shipping 1000’s of similar applications with the same general dependency chains in bulk operations to things like end-user devices.

Flatpak wins. That’s the point.

This isn’t a discussion about an average Desktop user saving some disk space.

Lots of people have moved on to more dynamic options that use JIT-style routing and role-,based security.

Netbird, Tailscale/Headscale, ZeroTier and Netmaker are all pretty popular.

Netbird and Netmaker are probably the simplest to get started with, but Headscale server + Tailscale client has been the best performing in my experience.

You asking for a service, or a server to run for yourself?

This has been known for awhile, and this was already accepted to be an issue with PH memory handling. Not weird, rare or otherwise, it will get fixed.

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

My Packard Bell will be so sad

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.

I don’t really get the point of the blog, honestly, because in the first part they are railing against one angle, then reverse and argue FOR it in a sense by saying Flatpak just works. Of course it does. That’s it’s job.

AppImage also just works, but there is a fundamental difference in the delta of what you get as a payload. AppImage has EVERYTHING the image needs to run. Flatpaks only contain the running code and custom dependencies, then it’s manager solves for shared libraries and generics from commonly available layers to download and run to solve for those deps.

Both make sense depending on how you feel you need to tackle the problem.

Where the author kid of goes off the rails is complaining that somehow either camp is somehow responsible for their product being popular enough to survive and be taken up by Valve. In this specific case, Valve is intending to include simple packaging for games and libraries they intend to ship to millions of cross platform devices. Flatpak makes sense from a bandwidth and storage standpoint for end-users.

AppImage does not. No idea why this person is taking issue with that.

Flatpak makes more sense for how Valve will be using it for all their new devices. Simple as that.

They “shit” money into ALL kinds of development that pushed lots of projects forward a decade in maybe a years time, and are doing it again with FEX. Are you taking issue with allmof that, or just this because they have a business use-case?

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