Package Details: gpu-screen-recorder r1205.ab5988a-1

Git Clone URL: https://aur.archlinux.org/gpu-screen-recorder.git (read-only, click to copy)
Package Base: gpu-screen-recorder
Description: A shadowplay-like screen recorder for Linux. The fastest screen recorder for Linux
Upstream URL: https://git.dec05eba.com/gpu-screen-recorder
Licenses: GPL-3.0-only
Submitter: DEC05EBA
Maintainer: DEC05EBA
Last Packager: DEC05EBA
Votes: 72
Popularity: 3.70
First Submitted: 2024-11-15 18:38 (UTC)
Last Updated: 2025-11-18 01:52 (UTC)

Dependencies (23)

Sources (1)

Pinned Comments

DEC05EBA commented on 2025-10-05 11:31 (UTC)

Please reinstall (rebuild) gpu-screen-recorder now that ffmpeg 8.0 was released in arch, otherwise gpu-screen-recorder will fail to run (mismatch in ffmpeg library version)

Latest Comments

1 2 3 4 5 6 .. 20 Next › Last »

DEC05EBA commented on 2025-10-05 11:31 (UTC)

Please reinstall (rebuild) gpu-screen-recorder now that ffmpeg 8.0 was released in arch, otherwise gpu-screen-recorder will fail to run (mismatch in ffmpeg library version)

DEC05EBA commented on 2025-09-05 17:08 (UTC)

@Boria138 You report issues by email as explained here: https://git.dec05eba.com/?p=about

But anyways, that error comes from your driver. Something is wrong with vaapi on your system. Try running this command to see if there is any error in the output or missing codecs: vainfo --display drm --device /dev/dri/card1

Maybe its using another device on KDE, you didn't explain if it's KDE X11 or KDE Wayland.

Boria138 commented on 2025-09-05 17:01 (UTC)

I couldn't find where to leave an issue, so I'll leave it here, since the maintainer is also the developer. Sorry if this is the wrong place.

In I3wm, the entry does not start with this erro

gsr-ui info: running command: gpu-screen-recorder --list-capture-options /dev/dri/card1 intel
gsr-ui info: running command: gpu-screen-recorder -w eDP-1 -c mp4 -ac opus -cursor yes -cr limited -fm vfr -k auto -encoder gpu -f 60 -v no -o Video.mp4 -q very_high -a default_output -restore-portal-session yes
gsr-ui info: running command: gsr-notify --text Started recording this monitor --timeout 2.000000 --icon-color 086DB7 --bg-color 086DB7 --icon record --monitor eDP-1
gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
libva error: /usr/lib/dri/iHD_drv_video.so init failed
gsr error: no video encoder was specified and neither h264, hevc nor av1 are supported on your system or you are trying to capture at a resolution higher than your system supports for each codec
Warning: gpu-screen-recorder (104192) exited with exit status 52
gsr-ui info: running command: gsr-notify --text Capture failed. Neither H264, HEVC nor AV1 video codecs are supported
on your system or you are trying to capture at a resolution higher than your
system supports for each video codec. --timeout 10.000000 --icon-color FF0000 --bg-color FF0000 --icon record --monitor eDP-1

However, the same command works in KDE.

DEC05EBA commented on 2025-06-22 17:29 (UTC)

@kiERO fixed

kIERO commented on 2025-06-22 17:23 (UTC)

A dependency change is neeed

linux-firmware: Required to record your screen on Intel Skylake or later iGPUs

Should be changed to linux-firmware-intel

dinkin commented on 2025-05-27 01:20 (UTC)

https://gist.github.com/DINKIN/71b05a5f2d10506efa2a2780a6599e8e

I've never encountered an error like this before

typically I can install your updates without any issues

so I am very confused what I did wrong & how I should proceed to resolve the issue

DEC05EBA commented on 2025-04-12 04:47 (UTC)

@RpxdYTX it's hard to know what the issue could be, you have to make a proper bug report by email as mentioned here: https://git.dec05eba.com/?p=about the video might not actually be black, it could even be that your video player is unable to properly play h264 videos, so you will have to send the file by email as well. If your xorg server/wayland crashes then it could be an bug in your intel driver, did you try if recording works with obs studio when configuring it to use vaapi in video settings? or if recording works with gpu screen recorder -w portal option?

RpxdYTX commented on 2025-04-12 02:29 (UTC)

Ran with gl-debug yes. My GL version is 3.3: gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glBindTexture(target = GL_TEXTURE_EXTERNAL_OES) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glTexParameteri(target) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glTexParameteri(target) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glTexParameterfv(target) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glTexParameteri(target) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glTexParameteri(target) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glBindTexture(target = GL_TEXTURE_EXTERNAL_OES) gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server gsr info: gsr_kms_client_init: waiting for server to connect kms server info: connecting to the client gsr info: gsr_kms_client_init: server connected gsr info: replacing file-backed unix domain socket with socketpair kms server info: connected to the client gsr info: using socketpair [AVHWDeviceContext @ 0x5758b4fe6840] libva: /usr/lib/dri/iHD_drv_video.so init failed gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_COMPUTE_WORK_GROUP_INVOCATIONS) gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glCreateShader(GL_COMPUTE_SHADER) gsr error: load_shader: failed to create shader, error: 1280 gsr error: gsr_color_conversion_init: failed to load Y compute shader gsr info: failed to load one or more compute shaders, run gpu-screen-recorder with the '-gl-debug yes' option to see why. Falling back to slower graphics shader instead gsr info: gl callback: ** GL ERROR ** type = 0x824c, severity = 0x9146, message = GL_INVALID_ENUM in glCreateShader(GL_COMPUTE_SHADER) gsr error: load_shader: failed to create shader, error: 1280 gsr error: gsr_color_conversion_init: failed to load Y compute shader gsr info: failed to load one or more external compute shaders, run gpu-screen-recorder with the '-gl-debug yes' option to see why. Falling back to slower graphics shader instead [h264_vaapi @ 0x5758b4feab00] ignoring invalid SAR: 0/0

RpxdYTX commented on 2025-04-12 02:20 (UTC)

It partially works, i installed the intel related drivers Vainfo yields: ... libva error: /usr/lib/dri/iHD_drv_video.so init failed ... VAProfileH264Main: VAEntryPointVLD

When recording on wayland, a black screen is outputted, and finishing recording closes the wm. Running through xwayland is hardly any useful since the recorded apps run through wayland and after testing with a x app the screen freaked out with glitches and the wm closed

1 2 3 4 5 6 .. 20 Next › Last »