com VS gtk3-mushrooms

Flatpak apps can still have access to the host ressources, like the file system. The nice thing is that you can see those permissions beforehand and adjust them if necessary. Flatseal simply has the permission to make those adjustments for other flatpak apps. Take a look at Flatseals manifest file, that should make it obvious.

Protontricks

Look at https://github.com/flathub/com.github.git_cola.git-cola/ which has git as a runtime dependency.

Click the link that says "See details" which leads to this page

Hi all, I've installed the flatpak version of ungoogled chromium on my ubuntu 20.04 machine and it has been working like a charm. However, I need to apply a policy .json file. In deb chromium I would put it in /etc/opt/chromium/policies/managed/. On flatpak version I am not clear on what folder to choose. I obviously tried using /etc/opt/chromium/, /etc/opt/chrome, /etc/chromium, ~/.var/app/com.github.Eloston.UngoogledChromium/, ~/.var/app/com.github.Eloston.UngoogledChromium/config/chromium/ but all without any results - the chrome://policy page in chromium is empty and doesn't show any policy to be set. I found that the flatpak "extensions" are used, but I didn't find any documentation on how to use this. I also tried giving the app access to the whole disk using flatseal but no avail.

Flathub (Linux)

I am not familiar with the process at Flathub. But as far as I understand, the developer of CopyQ has already made an appropriate update (https://github.com/flathub/com.github.hluk.copyq/pull/53). Maybe these updates will be shown at flathub.org only with a time delay.

Now, what I was trying before just setting the version was to use protontricks, you can install it in the software repository in desktop mode. Then follow the flatpack install instructions

There's a script for that here: https://github.com/flathub/com.github.Eloston.UngoogledChromium

GNOME runtime bump to 43 for Haguichi is now merged. Might take a few hours to get published.

It is not about KDE/Breeze, from what I have read, the issue is with GTK(3.) One fix, not 100%, but almost pefect fix is to switch out GTK3 with GTK3-Classic.

GTK3 does indeed suck. That's why I run it with these patches.

Unfortunately they also lost tons of functionality in the process. The fact that typing on a file picker starts a recursive search instead of simply jumping to the file/folder with the prefix you typed, is nothing short of hilarious.

Gtk-classic is the only thing that keeps me sane https://github.com/lah7/gtk3-classic

The KDE Server-Side Decoration is also really powerful, allowing easy Maximize Horizontally/Vertically, window shading/hiding, and moving windows between virtual desktop/workspace, all while being able to be hidden when maximized for that extra screen space when I'm on my old 768p laptop and why I use gtk3-classic to get that SSD. Also, Window Rules -- they're very, very handy to get windows and apps to start and behave in a certain way by default.

I highly recommend gtk3-classic.

It's a bug when it stalls out your computer for 2-3 seconds because the file picker is doing a recursive search through all of your files.

Luckily, the patches that fix this (along with some other bugs and anti-features) are actively maintained by community members, despite being ignored by the GNOME project.

https://github.com/lah7/gtk3-classic

gtk3-classic will move them out of the titlebar, but if you want them completely gone you're better off switching to applications that haven't fully embraced CSDs like Gedit.

The GTK3 filechooser is the reason I switched to gtk3-classic.

Use gtk3-classic.