You need to be on a rolling or upstream adjacent distro that has the most recent and untested version of everything available. Sounds like you would break things though, as you’re unfamiliar with the how/why of package management in general.
Mesa is a base library for much larger systems at work. Your example of Windows just letting install something like this isn’t exactly possible. Seems you think Mesa is like a driver or similar. It is not.
Can you explain a bit more on how this is a benefit?
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.
You can do this much simpler with the HA app registering back with your network when home or BT proximity to a location.
🤣
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.
Can you give more specifics about device drops? Have you looked at the mesh layout in HA to see what connections are being made between devices?
You may not have a distance issue that a new adapter will fix. You might just need a repeater/router.
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?
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.
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.
Fedora 44’s DTB implementation actually makes the Snapdragon SoCs work pretty well. I’d give it a look.
Valve also has the Frame running on Snapdragon’s, so that means full SoC performance and GPU implementation. How whatever they got working trickles down to the community remains to be seen.
AMD is launching their ARM chips this year.
Nvidia keeps pushing theirs back because the first gen was horrible, and the 2nd is already sounding problematic.
Zone aware networked alarms exist for a reason. This sounds kind of sketchy to me…