Arch Linux User Repository

The aur package gpu-screen-recorder-git was renamed to gpu-screen-recorder. Install gpu-screen-recorder instead or you may experience issues.

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

@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?

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

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

@RpxdYTX You likely haven't installed the intel vaapi driver needed for your intel gpu. Look at the list of optional dependencies and install the one that fits your gpu. You can run this command to see if vaapi is working: vainfo --display drm --device /dev/dri/renderD128

vainfo is available in the package called libva-utils. The command will list VAProfileH264Main with VAEntrypointEncSlice beside it it's working.

Got this error when running through gpu-screen-recorder-ui:

gsr-ui info: running command: gpu-screen-recorder --list-capture-options /dev/dri/card1 intel gsr error: gsr_dbus_call_screencast_method: failed with error: The name is not activatable gsr error: gsr_dbus_screencast_create_session: failed to setup ScreenCast session. Make sure you have a desktop portal running with support for the ScreenCast interface and that the desktop portal matches the Wayland compositor you are running. gsr-ui info: running command: gpu-screen-recorder -w LVDS-1 -c mp4 -ac opus -cursor yes -cr limited -fm vfr -k auto -encoder gpu -f 60 -v no -o /home/rpxdytx/Videos/Video_2025-04-11_17-48-23.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 LVDS-1 Info: using h264 encoder because a codec was not specified libva error: /usr/lib/dri/iHD_drv_video.so init failed gsr error: gsr_get_supported_video_codecs_vaapi: vaInitialize failed gsr error: gsr_get_supported_video_codecs_vaapi: failed to query supported video codecs for device /dev/dri/renderD128 Error: failed to query for supported video codecs Warning: gpu-screen-recorder (36527) exited with exit status 11 gsr-ui info: running command: gsr-notify --text Failed to start/save recording. Verify if settings are correct --timeout 2.000000 --icon-color FF0000 --bg-color FF0000 --icon record --monitor LVDS-1

Some changes have been made to improve performance (especially on amd). Report if there is an issue with the image that didn't happen before or if there are performance issues that you didn't have before (mainly on amd or intel).

@kopywastaken Nvidia gpus dont support vp8/vp9 encoding. Gpu screen recorder only shows the video encoding options that your gpu can use, so unfortunately you cant use vp9.

With davinci resolve you could use av1 in the free version but that's only available in nvidia gpus starting from the 4000 series so it's not an option for you. The options for you are to either buy davinci resolve (to get h264/hevc support), to transcode the video from h264/hevc to vp8/vp9 (with ffmpeg) or use another video editor such as kdenlive which supports more video codecs (including h264 and hevc).

Thanks for making this tool, it's very useful especially now that I am pretty much able to ditch Windows for everything now. QQ though, I'm not seeing an option for allowing VP9 encoding (I have a RTX 3080ti and updated drivers), but that's the only one of the encoding options supported by this tool that's usable in Davinci Resolve (non-studio). Is there any additional requirements that are needed to allow VP9 encoding?

@suero nah I dont like chats/social media and I dont want to get distracted from working. If somebody has a question they have to email me instead and if its a common question i'll add it under FAQ in the about page for the software.