My apologies, its on my end. An extension was blocking it, now I can see the screenshots. Not sure what happened, because that is the first thing I check. Everything fine, I can see the two screenshots too.
I get this sporadically, probably once a week on average. Most of the time it seems to be caused by a specific tab and resolves itself after closing the tab (in my case Slack is the most common culprit).
KDE plasma. From my experience it uses less resources than lxqt and xfce and works out of the box while lxqt and xfce required extra work to get wifi, screen brightness controls and audio working. I can have 10+ tabs in a chromium based browser open without lag on an old laptop with 2GB ram and 1.33 - 1.83GHz 4 core intel atom from 10 years ago.
Its a silly default. Might also be to allow people to edit /etc configs with the app since its a basic editor. With enough dummies complaining about “doesn’t work can’t access files in <directory>” the dev may have set that to reduce negative review bloat (seriously look at the flatpak and snap stores and the number of bad reviews due to people not understanding the permissions system).
I would be turning that off immediately until I knew how trustworthy the app was or not installing it, just saying I can see where that default setting might be coming from.
Flatpak could use a permissions prompting api, so a prompt could be displayed to the user when they try to access a file outside the permissions scope, but that’s probably a lot of work to get in place. Maybe something we’ll see in flatpak in a few years.
Until then I think there needs to be some way to point new users to Flatseal and a summary of what these warnings imply and how to grok them.
A window manager like i3 or Openbox. If you are curious what that’s like, then try out Bunsenlab Linux. (XFWM4 is also a great choice, but it requires some know how to properly rip out the rest of Xfce, like the relatively heavy desktop and the panel)
Is the A6 from 2017/18? Should be fine with anything. My wife’s laptop is from 2010/11. I tried all the DEs because of the lightness claims, I found GNOME worked the best, and it is super peppy running NixOS.
I asked online why GNOME would perform better than what is assumed a lighter DE, and a comouter dude says GNOME goes and gets everything it needs and caches it when you launch something so retrieval is faster in the app, KDE loads stuff on demand as it is asked for so a alow CPU and HDD hinderes KDE for me.
Not for the average/casual user, which is why this post exists.
The average person will look at that and see the ‘!’ in a triangle and became scared of what it can do to their system, even though it has no more permissions than a system package. Alternatively, they will become desensitized and learn to ignore it, resulting in installing flatpacks from untrusted and unverified sources.
Overall, I just think the idea around having to sandbox all flatpaks is not a good idea. To give a concrete example, Librewolf is marked as “potentially unsafe” because it has access to the download folder, but if I want to use it to open a file that isn’t in “downloads” I have to use flatseal to give it extra permissions - it’s the worst of both worlds! Trying so hard to comply with flatpak guidelines that it gets in the way of doing things, and still not being considered safe enough.
I don’t know about this in depth, but from what another user in this thread said, a flatpak can’t ask a portal to have access to two files at once. If I’m understanding correctly, that would explain why Librewolf needs permission to access ~/Downloads, since it can be downloading more than one file at once, and it needs access to all those files in ~/Downloads at the same time.
EDIT: I got a bit mixed up with what you were saying, but nevertheless, if this is true, then Librewofl would still need permission to access ~/Downloads and so be marked as “potentially unsafe”.
I get what you mean. When updating Linux mint, the “This needs to get some additional packages too” window, relatively benign, has a big scary ⚠️/ /! on it.
Felt the need to explain to the person I was installing it for. “That’s totally normal, just look it over first and continue.”
…like, it’s gonna do that almost every time it updates, it doesn’t need to look scary. :|
I don’t know why a journaling app needs full system access and access to system settings, and the permission Flatseal requests is a dangerous one if you pay attention to these things. Looks like they’re doing their job to me.
Xournal seems pretty trustworthy to me, so I assume it’s for code simplicity (or age) or not being made with Flatpak in mind - just ‘open any file/full filesystem access’’ (for basic functions like opening files) and ‘change system settings’ for probably only a few features that change system settings.
I agree the permissions are dangerous and I commend Flatpak for incentivizing developers to use granular permissions.
As others (and you yourself have said), Flatseal’s entire purpose is to edit Flatpak lermissions, so that one shouldn’t be alarming.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.