I couldn't find that under the topics he has created, could it be it was a reply to another's post?
Yes, I was searching too and just found one that mentions it (there are several):
Flatseal. Now I will try to remember it.
Yes, I have used Flatseal on the Zorin environment to grant apps permissions filesystem=home or filesystem=host (I am unsure which of the 2 is the best to use). That is what made most of them work with the Zorin theme.
That, unfortunately does not extend to i3. They all start up with the default Adwaita theme. I don't know if I am supposed to start some gnome daemon when logging in or if I must do something else.
I am sorry; my ignorance of Flatpak usage and workarounds is very apparent here.
It may be that the i3 window manager is what we need to look at.
Is it just the window borders that are in Adwaita, or the entire themed window?
When I created the tutorial, nobody took it seriously. This is very apparent by the responses I got, and I am still not OK with that, when everybody else's tutorials got likes and respect. This is part of why its hard to find, cause its buried in the forum from lack of views and respect I think.
https://forum.zorin.com/t/how-to-setup-external-drives-with-steam-flatpak/8233/13
But yes, Flatseal is how I did it guys.
Yes, I get it, Flatpack is not popular among some folks around here. But you know what, some people use Flatpack cause they have to. So Flatpack related issues are just as important as APT package related issues or whatever.
This is what they look. On the right is the Flatpak app. Left is not Flatpak, but I get some huge borders on some "system" apps Like gedit, Nautilus, Settings, etc.
I also get the impression that they are being pushed, by some, as eventual replacements for how apps are distributed in distros.
1 Like
I freely admit that is most certainly the case in POP OS especially. POP OS makes up for about 40-installed packages on my system. If you were to remove all the FLATPAK APPS on my POP OS system, POP OS would be broken, since the OS structure itself, relies heavily on them.
Still though, the majority of normal packages is 3100 rightr from DPKG's, I don't know, thats one of the reasons why I post these screenshots, that way I can show the evidence, instead of it just being, my word against another's or whatever.
1 Like
These are the CSD (Client Side Decoration) apps that do not use the Window Manager to make the borders.
Why do they show up? Can they be turned off?
In Gnome Desktop, they cannot be turned off. However, they can be turned off for the Home User on other Desktop Environments. If you are a Zorin OS Lite user, then you can disable the wayward CSD's on applications that cause them to not match the rest of the D.E.
This is done using gtk3-nocsd package.
sudo apt install gtk3-nocsd
That's it. No need to do anything else. After restarting and logging into Cinnamon or XFCE or whatever non-Gnome D.E. you are using, the CSD's are gone and all applications use the Proper Window Borders.
I am on the Core version. Will this work there as well?
It will not.
The package gtk3-nocsd is for Window Managed Desktops. Gnome is not one; it dumps window management on the Client, instead.
So is there no solution for core then?
Not on the Sidetopic we were just engaged in. But I think the current actual issue was the two apps not following the same theme.
And I just finally had my wee little brain percolate a thought...
Is that other app a QT app?
QT apps do not follow gtk theme--- But they can be Made To Do so.
If you could please check if the apps in question are QT based and not GTK based, that would answer the question and point us toward the solution.
1 Like
It is GTK based. The same happens to all Flatpaks.
I wonder if I am supposed to execute some program when starting i3wm or something. Currently I run this: exec --no-startup-id gnome-settings-daemon
But again, to get Flatpaks to display themes properly on the Gnome env on my machine (I believe it wasn't this bad in Z15.3) I had to manually give them permission in Flatseal, so I am not sure.
1 Like
Yes... It may well be due to using i3 Desktop. Which I have personally never used. I am ignorant about its ins and outs.
I thought that having Zorin themes available as Flatpaks were precisely so issues like this (at least on the Gnome side, that is) wouldn't happen. So users didn't have to manually turn on sketchy permissions in an app (Flatseal) that is not baked in.
Prob not the cause, but could this have anything to do with it? I was a beta tester.
We would recommend users of Zorin OS 16 Beta to perform a clean install upgrade to Zorin OS 16 in order to run the latest and most stable software.
Me too, actually.
No, I am sorry to say that is not the cause. Beta really did update right into being the same as core.
It is wiser for the ZorinGroup to advice a fresh install than it is for them to contend with users blaming them if Beta Breaks in some way.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.