@DEC05EBA I haven't really had the bug happen for a while on it's own but I noticed with pipewire sometimes my desktop audio would be behind for some reason, so I restarted it while GPU-Screen-Recorder was running and I got the same bug where it said waitpid failed.
Search Criteria
Package Details: gpu-screen-recorder r1115.d0a620a-1
Package Actions
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: | 58 |
Popularity: | 4.15 |
First Submitted: | 2024-11-15 18:38 (UTC) |
Last Updated: | 2025-06-10 08:59 (UTC) |
Dependencies (23)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-fullAUR, ffmpeg-headlessAUR, ffmpeg-amd-full-gitAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-obsAUR, ffmpeg-libfdk_aacAUR)
- libcap
- libdrm (libdrm-gitAUR)
- libglvnd (libglvnd-gitAUR)
- libpipewire (libpipewire-full-gitAUR, libpipewire-gitAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libva (libva-gitAUR, libva-headlessAUR, intel-media-stack-binAUR, intel-media-stack-legacy-binAUR)
- libx11 (libx11-gitAUR)
- libxcomposite
- libxdamage
- libxfixes
- libxrandr (libxrandr-gitAUR)
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR)
- meson (meson-gitAUR) (make)
- vulkan-headers (vulkan-headers-gitAUR) (make)
- intel-media-driver (intel-media-driver-gitAUR, intel-media-driver-legacyAUR, intel-media-driver-legacy-binAUR, intel-media-stack-binAUR, intel-media-stack-legacy-binAUR) (optional) – Required to record your screen on Intel Broadwell or later iGPUs or Intel Arc
- libva-intel-driver (libva-intel-driver-gitAUR, libva-intel-driver-hybrid-gitAUR, libva-intel-driver-irqlAUR, libva-intel-driver-hybridAUR) (optional) – Required to record your screen on Intel G45 and HD Graphics family
- libva-mesa-driver (mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-minimal-gitAUR, mesa-fp8-gitAUR, mesa-gitAUR, mesa) (optional) – Required to record your screen on AMD
- libxnvctrl (libxnvctrl-430xxAUR, libxnvctrl-340xxAUR, libxnvctrl-390xxAUR, libxnvctrl-525xxAUR, libxnvctrl-510xxAUR, libxnvctrl-470xxAUR, libxnvctrl-535xxAUR) (optional) – Required when using the -oc option to overclock the NVIDIA GPU to workaround NVIDIA p2 state bug
- linux-firmware (linux-libre-firmwareAUR, linux-firmware-gitAUR, linux-firmware-uncompressedAUR) (optional) – Required to record your screen on Intel Skylake or later iGPUs
- mesa (mesa-wsl2-gitAUR, mesa-amd-bc250AUR, amdonly-gaming-mesa-gitAUR, mesa-minimal-gitAUR, vulkan-terakan-gitAUR, mesa-fp8-gitAUR, mesa-gitAUR, mesa-amber) (optional) – Required to record your screen on AMD/Intel
- nvidia-utils (nvidia-410xx-utilsAUR, nvidia-440xx-utilsAUR, nvidia-430xx-utilsAUR, nvidia-340xx-utilsAUR, nvidia-535xx-utilsAUR, nvidia-470xx-utilsAUR, nvidia-utils-teslaAUR, nvidia-550xx-utilsAUR, nvidia-565xx-utilsAUR, nvidia-525xx-utilsAUR, nvidia-510xx-utilsAUR, nvidia-utils-betaAUR, nvidia-vulkan-utilsAUR, nvidia-390xx-utilsAUR) (optional) – Required to record your screen on NVIDIA
Required by (4)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 19 Next › Last »
creepergd commented on 2023-05-10 18:51 (UTC)
DEC05EBA commented on 2023-05-04 21:41 (UTC)
@creepergd can you try without nvidia overclock?
creepergd commented on 2023-05-04 21:39 (UTC)
@DEC05EBA I had a microphone and desktop audio being merged, 60fps, HEVC video codec, AAC audio codec, ultra quality, Nvidia Overclock applied. My recording area was set to be my monitor.
DEC05EBA commented on 2023-05-04 21:31 (UTC)
@creepergd what record options did you use?
creepergd commented on 2023-05-04 21:24 (UTC)
@DEC05EBA I set 300 replay time which worked fine for a long time (on nvidia btw). This seems to be a relatively recent problem.
DEC05EBA commented on 2023-05-04 21:04 (UTC) (edited on 2023-05-04 21:04 (UTC) by DEC05EBA)
@creepergd how long replay time did you set? maybe it used too much memory and was killed by the operating system? also is this on amd/intel or nvidia?
creepergd commented on 2023-05-04 21:02 (UTC)
@DEC05EBA Yeah that's exactly what happened
DEC05EBA commented on 2023-05-04 20:40 (UTC)
@creepegd that doesn't look like the full error output. Did it just output "update fps: ..." a while and then output waitpid failed ...?
creepergd commented on 2023-05-04 20:29 (UTC)
@DEC05EBA Ok so the bug happened again (it took a while for it to happen again)
the text that generated was waitpid failed: No child processes
Notification: title: GPU Screen Recorder, body: Failed to start replay. Either your graphics card doesn't support GPU Screen Recorder or you don't have enough disk space to record a video
DEC05EBA commented on 2023-05-03 11:17 (UTC) (edited on 2023-05-03 11:30 (UTC) by DEC05EBA)
@creepergd run gpu screen recorder (or gpu screen recorder gtk) from the terminal to see if it says anything in the terminal output. That usually contains more information for the exact reason why it failed. Also is this on nvidia or amd/intel?
Pinned Comments
DEC05EBA commented on 2024-11-26 18:52 (UTC)
The aur package gpu-screen-recorder-git was renamed to gpu-screen-recorder. Install gpu-screen-recorder instead or you may experience issues.