qubes-issues VS Flatseal

Are you using an Nvidia GPU?

https://github.com/QubesOS/qubes-issues/issues/5104

https://github.com/QubesOS/qubes-issues/issues/7591

If not, try this: https://github.com/QubesOS/qubes-issues/issues/6880#issuecom...

There is no tearing on my Librem laptops.

> The gnome desktop will be important for adoption

Gnome is too opinionated to adjust it for Qubes: https://github.com/QubesOS/qubes-issues/issues/1806#issuecom...

However you can easily install KDE.

Are we still getting a second RC for 4.2? I remember originally we were told that we would because of the new Qubes builder tool, but I see the milestone jumped to 96% since last I checked, are we getting a full release at the 100% github milestone? Or what happens when it hits 100? https://github.com/QubesOS/qubes-issues/milestone/26

This project was never stagnant, a lot of things are always happening here: https://github.com/QubesOS/qubes-issues.

Concerning the certified hardware, few vendors try to make the certification, and also coreboot is required: https://www.qubes-os.org/doc/certified-hardware/#hardware-ce...

Not precisely, but a lot is going on in this direction: https://github.com/QubesOS/qubes-issues/issues/1939.

I read that there is a plan to implement per-VM encryption (https://github.com/QubesOS/qubes-issues/issues/1293)

Looks like a fix might be close at hand: This pull request is linked to the issue "Hardware support: Ryzen 7000 series / Zen 4 / AM5."

This bug report indicates that "kernel-latest" will be in the next official build of the Qubes 4.1 install ISO. Thing is on the mirrors the last release of 4.1 (actually 4.1.1) was July 18th 2022, and thus the title of this post.

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal