aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authordec05eba <dec05eba@protonmail.com>2023-06-18 20:48:36 +0200
committerdec05eba <dec05eba@protonmail.com>2023-06-18 20:48:36 +0200
commit7f2099b3ca28b140ec8c9eed9a08c83c1e49c241 (patch)
tree7a9223b666f29357d6ee28d5a7e149f62f87f286 /README.md
parentba86d20b2db5cc268a55f1333462217b3c2e9370 (diff)
Update readme
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 17c2d7e..f107aae 100644
--- a/README.md
+++ b/README.md
@@ -16,7 +16,7 @@ GPU Screen Recorder only supports h264 and hevc codecs at the moment which means
### AMD/Intel root permission
When recording a window under AMD/Intel no special user permission is required, however when recording a monitor the program needs root permission (to access KMS).
To make this safer, the part that needs root access has been moved to its own executable (to make it as small as possible) and a GUI sudo prompt is shown to run this executable as root. The executable is called "gsr-kms-server".
-However this doesn't work if you want to start replay at startup for example. To fix this, run: `sudo setcap cap_sys_admin+ep /usr/bin/gsr-kms-server` if you have installed GPU Screen Recorder.
+However this doesn't work if you want to start replay at startup for example. To fix this, run: `sudo setcap cap_sys_admin+ep /usr/bin/gsr-kms-server` if you have installed GPU Screen Recorder from source or AUR.
# Performance
On a system with a i5 4690k CPU and a GTX 1080 GPU:\