matanui159
commented
2 years ago Can you also grab the logs of the replay-sorcery-kms service?
Open Steccah opened 2 years ago
matanui159
commented
2 years ago Can you also grab the logs of the replay-sorcery-kms service?
Katharta
commented
2 years ago Hello, I believe I'm running into the same thing. I am also running Arch using KDE with Wayland on an AMD 3700X & RX 5700 XT. Here is my replay-sorcery-kms log if it helps.
katharta@ragnarok[~]$ journalctl -fu replay-sorcery-kms
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: Framerate = 60, Device = auto
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: [kmsgrab @ 0x558f43326000] Using plane 65 to locate framebuffers.
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: [kmsgrab @ 0x558f43326000] Template framebuffer is 119: 3440x1440 format 30335241 modifier 200000000801b02 flags 2.
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: [kmsgrab @ 0x558f43326000] Framebuffer pixel format 30335241 is not a known supported format.
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: Unused option: framerate
Aug 08 12:05:09 ragnarok replay-sorcery[278419]: Disconnected: Invalid argument
Steccah
commented
2 years ago I tried reinstalling everything but it still doesn't work
Steccah
commented
2 years ago if it could be of any help i use ffmpeg-amd-full
astroty
commented
1 year ago I can second this. I used to be able to run replay-sorcery properly up until 21-11-2022 but apparently I can't anymore. get same error with same logs pretty much
sylvesterroos
commented
1 year ago Same issue here
Where can I find the logs? 😅 My systemd log is pretty short:
$ journalctl --user -fu replay-sorcery.service
Journal file /var/log/journal/dc540a00cc1f472fb62d44441791e375/user-1000@e5aa7bd2826f491d8c36ca09ba1f0b05-0000000000000000-0000000000000000.journal corrupted, ignoring file.
Dec 29 13:32:47 icarus replay-sorcery[42539]: [AVHWFramesContext @ 0x557857c13b80] [IMGUTILS @ 0x7ffdb6b82da0] Picture size 0x0 is invalid
Dec 29 13:32:47 icarus replay-sorcery[42539]: Failed to init DRM frames context: Invalid argument
Dec 29 13:32:47 icarus replay-sorcery[42539]: Invalid argument
Dec 29 13:32:47 icarus systemd[3538]: replay-sorcery.service: Main process exited, code=exited, status=1/FAILURE
Dec 29 13:32:47 icarus systemd[3538]: replay-sorcery.service: Failed with result 'exit-code'.
Dec 29 13:32:47 icarus systemd[3538]: replay-sorcery.service: Scheduled restart job, restart counter is at 5.
Dec 29 13:32:47 icarus systemd[3538]: Stopped ReplaySorcery: an open-source, instant-replay solution for Linux..
Dec 29 13:32:47 icarus systemd[3538]: replay-sorcery.service: Start request repeated too quickly.
Dec 29 13:32:47 icarus systemd[3538]: replay-sorcery.service: Failed with result 'exit-code'.
Dec 29 13:32:47 icarus systemd[3538]: Failed to start ReplaySorcery: an open-source, instant-replay solution for Linux..
$ journalctl -fu replay-sorcery-kms.service
Journal file /var/log/journal/dc540a00cc1f472fb62d44441791e375/user-1000@e5aa7bd2826f491d8c36ca09ba1f0b05-0000000000000000-0000000000000000.journal corrupted, ignoring file.
Dec 29 13:32:47 icarus replay-sorcery[626]: [kmsgrab @ 0x55c30227e600] Template framebuffer is 111: 1920x1080 format 30335241 modifier 200000004801a01 flags 2.
Dec 29 13:32:47 icarus replay-sorcery[626]: [kmsgrab @ 0x55c30227e600] Framebuffer pixel format 30335241 is not a known supported format.
Dec 29 13:32:47 icarus replay-sorcery[626]: Unused option: framerate
Dec 29 13:32:47 icarus replay-sorcery[626]: Disconnected: Invalid argument
Dec 29 13:32:47 icarus replay-sorcery[626]: Framerate = 60, Device = auto
Dec 29 13:32:47 icarus replay-sorcery[626]: [kmsgrab @ 0x55c30227f600] Using plane 52 to locate framebuffers.
Dec 29 13:32:47 icarus replay-sorcery[626]: [kmsgrab @ 0x55c30227f600] Template framebuffer is 105: 1920x1080 format 30335241 modifier 200000004801a01 flags 2.
Dec 29 13:32:47 icarus replay-sorcery[626]: [kmsgrab @ 0x55c30227f600] Framebuffer pixel format 30335241 is not a known supported format.
Dec 29 13:32:47 icarus replay-sorcery[626]: Unused option: framerate
Dec 29 13:32:47 icarus replay-sorcery[626]: Disconnected: Invalid argument
awsms
commented
1 year ago since this is not going to be fixed, anyone knows a software alternative?
kode54
commented
1 year ago Try kms_service in combination with the replay-sorcery-kms.service daemon. Set the video device string to:
card#:#Where the first number is the DRM device number from /dev/dri/card#, and the second number is the Object ID of the Plane you want to capture. With auto it will pick the first card and the first plane, which may not always be correct.
If replay-sorcery kms-devices doesn't work for you, try the drm_info software package, which may have distribution packaging for you, and look through its output for the correct Plane you wish to capture, referred to by its Object ID number. This number may not be consistent across installs or even reboots, but I've had some luck with it remaining the same with consistent hardware and kernel installs.
toasterofbread
commented
12 months ago For those with issues running replay-sorcery kms-devices:
It fails for me with the error Failed to get DRM framebuffer 120: Invalid argument when running it from within my DE (Hyprland), but works perfectly fine from a fresh TTY. I set videoDevice using the output like @kode54 suggested and everything worked perfectly from there.
Based on lines like Failed to create KMS device: Invalid argument in the original logs above, I'm guessing whatever causes this to fail is also what's causing issues with replay-sorcery itself when not explicitly setting the videoDevice.
toasterofbread
commented
9 months ago Several months later, and the solution I mentioned no longer works for me (presumably due to driver changes).
Now, replay-sorcery kms-devices always prints this and exits with no error or useful output.
Real user ID: 1000
Effective user ID: 1000
Describe the bug Replay sorcery service fails to start
Desktop:
Configuration:
Logs: