31
Why can't flatpaks just work
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jul 2023
31 points (100.0% liked)
Linux
47380 readers
607 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Tl;dr it's likely that some of your hardware isn't well supported in Linux or have vendors downright hostile to open source (fuck you, Broadcom and Nvidia) and causes you weird issues that almost always get fixed by the community but may not always work "out of the box"
I've been in Linux since 2008 and have asked this question in many ways over the years. To get a real answer I'd dig more into the errors you're encountering. I think that a lot of the "simple fixes" you mention are simply options that some hardware configurations need and some don't.
Flatpak and Linux in general deal with the same huge task as Windows, which is "support any hardware configuration with one universal solution". While Windows is given every advantages by cooperative hardware vendors releasing official drivers, Linux is mostly supported by open source reverse engineered drivers.
This means that no "universal" system is likely to work all the time in every case, but that's ok because it's all open source and the community finds a way.
You mentioned themes and some graphical packages, do you have an Nvidia GPU? I never had anything but trouble on Linux with them.
It has nothing to do with my hardware. Like I said fixing the theme was done with a simple command that basically mapped my user .icons folder to the flatpak one. My point is just that why isn't this done automatically. Why isn't there a system in place that will deal with this.
If it bothers you that much, write one. 85% of Linux was constructed by frustrated nerds deciding to write their own solution to a problem they found. There is no parent company to complain to, just fix it yourself and distribute the solution. Else, you'll need to wait for someone else to do exactly that.
True. I would if I knew C. Maybe it will be a reason for me to learn it.
If feels like there is a system in place that will deal with this if it can be resolved by a simple command. Am I missing something?
Why is the command necessary and why did I have to Google it. It feels like it should be default behavior.
I can't say with any specifics but flatpaks are sandboxed on purpose, when you override something you're giving it more (or less) permissions than the developer thought they'd need. "Automatically giving permissions the developer didn't think they'd need" seems like a crazy thing to try to automate, no?
Check out Flatseal if you haven't already. It's a GUI for flatpak permissions. Might make your life easier in the future.
Yeah I understand the reason why it is the way it is. I think it should be simplified. Just a pop-up box asking the user if it's ok if flatpak gains Access to path x. That's what I have in my mind. Maybe with time it will improve.
How do you propose that they trigger that popup? How would flatpak or the application know to ask if you wanted to add those extra permissions?
I don't know. It's only an idea.
It was mostly rhetorical. There's no way to know that you want the application to have extra access to some folder needed for your theme. That's the exact kind of thing that would be better handled on a user-input level. You applied your theme, you notice that it is broken with the app, you apply the new expanded permissions to get it to work with your theme.