Skip to content

Enabling Screen Capture crashes Hyperion - How to enable DRM/KMS screen grabber for Raspi 5? #1979

@ibaon

Description

@ibaon
  • I confirm that this is an issue rather than a question.

Bug report

I have been trying setup Hyperion or some alternatives on my Raspberry Pi 5 for some time now. But due to the way the video signal is being decoded on the Pi 5, it seems like none of the screen capture options so far are working. I just noticed the new release of Hyperion 2.2.0 which supports "a new DRM/KMS screen grabber with plane-based capture". If I understand it correctly, this might be the solution to the problem with the Hyperion on the Raspberry Pi 5?

I installed the newest version of Hyperion (on my Raspberry Pi 5 running RetroPie + Kodi) and confirmed, that I am using Version 2.2.0.

If I try to activate Screen Capture, Hyperion will crash and it takes a few seconds for the web interface to load again. I don't see any option to chose between different types of screen capture. So how can I enable the DRM/KMS screen grabber or what might be causing hyperion to crash?

This is the log after the crash:

sudo journalctl -u hyperion@retropi.service -f
Feb 06 14:20:07 raspberrypi hyperiond[1257]: /lib/aarch64-linux-gnu/libQt6Core.so.6(+0x253688) [0x7ffef96c3688]
Feb 06 14:20:07 raspberrypi hyperiond[1257]: /lib/aarch64-linux-gnu/libc.so.6(+0x82030) [0x7ffef9022030]
Feb 06 14:20:07 raspberrypi hyperiond[1257]: /lib/aarch64-linux-gnu/libc.so.6(+0xebf1c) [0x7ffef908bf1c]
Feb 06 14:20:07 raspberrypi systemd[1]: hyperion@retropi.service: Main process exited, code=killed, status=11/SEGV
Feb 06 14:20:07 raspberrypi systemd[1]: hyperion@retropi.service: Failed with result 'signal'.
Feb 06 14:20:09 raspberrypi systemd[1]: hyperion@retropi.service: Scheduled restart job, restart counter is at 2.
Feb 06 14:20:09 raspberrypi systemd[1]: Stopped hyperion@retropi.service - Hyperion ambient light systemd service for user retropi.
Feb 06 14:20:09 raspberrypi systemd[1]: Started hyperion@retropi.service - Hyperion ambient light systemd service for user retropi.
Feb 06 14:20:09 raspberrypi hyperiond[1279]: No displays found to capture from!
Feb 06 14:20:09 raspberrypi hyperiond[1279]: Grabber disabled, device 'GRABBER-QT' signals error: 'Opening display 0 failed.'

Steps to reproduce

What is expected?

What is actually happening?

System

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions