this post was submitted on 20 Jan 2025
17 points (94.7% liked)

Linux

49393 readers
1678 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

SOLVED: BananaTrifleViolin's post contains the solution.

Flatseal won't start by itself anymore, which is a known issue. I got it running by running

GSK_RENDERER=gl com.github.tchx84.Flatseal

and inspired by a response in the above linked issue, I wanted to add GSK_RENDERER=gl as a variable in Flatseal so I could open it without having to manually run this in the terminal.

However, I seem to have screwed that up, and written GSK_RENDERER=ng instead, because the application still won't run, and now I get the following output anytime I try to open it by the method above:

(com.github.tchx84.Flatseal:2): Gsk-WARNING **: 22:09:54.997: Unrecognized renderer "ng". Try GSK_RENDERER=help
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:782: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:814: FINISHME: support more multi-planar formats with DRM modifiers
Gdk-Message: 22:09:55.406: Error 71 (Protocol error) dispatching to Wayland display.

However, I can't for the life of me seem to correct this. I've tried running the above command again, I've tried overriding it with flatpak:

flatpak override --env=GSK_RENDERER=gl com.github.tchx84.Flatseal

(which yielded a "permission denied", and nothing happening after running with sudo)

I've reinstalled the applications several times, including removing the config files from ~/.var/app/com.github.tchx84.Flatseal and checked that /var/app/ does not contain any config files.

I just want to reset the user input changes I made to this flatpak and start over, but I'm getting no where...

all 3 comments
sorted by: hot top controversial new old
[–] BananaTrifleViolin@lemmy.world 5 points 1 week ago* (last edited 1 week ago) (1 children)

Sorry I originally posted around permissions as I misunderstood; deleted that. The solution is below:

If it's a user installed flatpak you should find the config files in:

~/.local/share/flatpak/overrides

Edit the document for the flatseal app. Thats where flatseal or the flatpak override tool makes it's config changes for user installed flatpaks (including env overrides). You can also delete the flatseal file (which will be the name of the flatpak - com.github.tchx84.Flatseal) "to set back to default.

There will only be a few files - files are only created when there are overrides set. Anything running default permissions/config won't have an override file.

EDIT: For completeness, for System wide flatpaks all the files are in:

/var/lib/flatpak

Just to explain why they're stored there: you're trying to change the config of the sandbox itself not the app. Flatpak manages the sandbox and it is flatpak that needs to know what permission an app should have. Any files in "~/.var/app/..." pertain to the app itself inside it's sandbox.

[–] cyberwolfie@lemmy.ml 1 points 1 week ago

Thanks! That worked right away :) I have also entered the correct environment variable in Flatseal now, and it opens as expected now from the desktop shortcut.

Just to explain why they’re stored there: you’re trying to change the config of the sandbox itself not the app. Flatpak manages the sandbox and it is flatpak that needs to know what permission an app should have. Any files in “~/.var/app/…” pertain to the app itself inside it’s sandbox.

Thanks for this explanation! I love Linux after having used it for two years now, but the sheer amount of things to know about is quite overwhelming when I don't always have too much time to spend on learning. It doesn't always feel like I'm getting any better (although I know that is not true), but comments such as yours is certainly helping people like me become better users :)