From 9776cc4e7e9037bde5d5ece69f7d1f959da4bfd5 Mon Sep 17 00:00:00 2001 From: dec05eba Date: Sat, 6 Apr 2024 15:08:28 +0200 Subject: Resolve /proc/self/exe fullpath --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 6f18154..a927133 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,14 @@ -This program fixes password prompt spam in GPU Screen Recorder when used from flatpak. +This program fixes password prompt spam in GPU Screen Recorder when used from flatpak and keep removing the password prompt spam even after updating GPU Screen Recorder flatpak. This program is meant to be ran with flatpak-spawn --host. This program is not meant to be run by the user and is automatically launched from GPU Screen Recorder flatpak. When this program is first run, it executes itself with pkexec and in that case it sets CAP_SYS_ADMIN capability on itself after copying self to ~/.local/share/gpu-screen-recorder and launches gsr-kms-server (in flatpak location). When this program is run after that it will check if its run from ~/.local/share/gpu-screen-recorder or launch that and it will see that the program has CAP_SYS_ADMIN capability and will launch gsr-kms-server (in flatpak location). This program also sets CAP_SYS_ADMIN on gsr-kms-server in the flatpak app directory. +Fallbacks are used. For example if it fails to create the file in ~/.local/share/gpu-screen-recorder and set capability on that then the gsr-kms-server is used directly, +which will keep its capabilities until GPU Screen Recorder flatpak is updated. If setting capabilities on gsr-kms-server also fails then gsr-kms-server is launched with pkexec, +so a password prompt will show up. + The reason all of this is needed is because `setcap cap_sys_admin+ep gsr-kms-server` can't be done in the flatpak because of sandboxing so this is only done when you install GPU Screen Recorder from source/aur to workaround that limitation. -- cgit v1.2.3