Image Effect trigger kills Hyperion #1980
Description
- I confirm that this is an issue rather than a question.
Bug report
I have been using this setup for a year already. Unfortunately after weekly package maintenance it started to crash the hyperion serivce. The following packages were upgraded:
Requested-By: osmc (1000)
Upgrade: hyperion:armhf (2.1.1~bullseye, 2.2.0~bullseye), libasound2:armhf (1.2.4-1.1, 1.2.4-1.1+deb11u1), cloudflared:armhf (2026.1.2, 2026.2.0), libasound2-data:armhf (1.2.4-1.1, 1.2.4-1.1+deb11u1), sudo:armhf (1.9.5p2-3+deb11u2, 1.9.5p2-3+deb11u3)
End-Date: 2026-02-10 06:19:26
Steps to reproduce
- Have a Homeaassistant "Hyperion" integration installed
- Start the "Fire" LED effect through this integration
What is expected?
A Fire effect is being displayed on the ws281x led strip "directly" connected to the Raspberry Pi 3B.
What is actually happening?
Hyperion service is being killed and restarted
In the journalctl I can see the following logs:
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.072 |__| HYPERION-INSTMGR : <INFO> Hyperion instance [0] - 'RPi controlled leds' started.
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.072 |__| NETFORWARDER : <DEBUG> MessageForwarder.cpp:93:connectToInstance() | Forwarder not connecting to instance [0] as it is not the configured one [255]
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.073 |__| FLATBUFSERVER : <INFO> Started on port 19400
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.073 |__| PROTOSERVER : <INFO> Started on port 19445
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.147 |__| EVENTS-CEC : <DEBUG> CECHandler.cpp:54:handleSettingsUpdate() | CEC Event handling is disabled
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.147 |__| EVENTS-CEC : <INFO> CEC handler disabled
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.156 |I0| MUXER : <DEBUG> PriorityMuxer.cpp:469:updatePriorities() | Set visible priority to 1
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.157 |I0| HYPERION : <DEBUG> Hyperion.cpp:692:handleSourceAvailability() | new source available -> LED-Device is enabled, switch LED-device on and resume output processing
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.157 |I0| LEDDEVICE : <DEBUG> LedDevice.cpp:547:switchOn() | Device ws281x is already on. Skipping.
Feb 11 05:59:01 osmc hyperiond[1704]: 2026-02-11T05:59:01.159 |__| WEBSERVER : <DEBUG> WebServer.cpp:102:handleSettingsUpdate() | Apply Webserver settings
Feb 11 06:00:11 osmc hyperiond[1704]: 2026-02-
Feb 11 06:00:11 osmc hyperiond[1704]: Hyperion Daemon caught signal: SIGSEGV
Feb 11 06:00:11 osmc hyperiond[1704]: /lib/arm-linux-gnueabihf/libc.so.6(+0x2acc0) [0x757afcc0]
Feb 11 06:00:11 osmc systemd[1]: hyperion.service: Main process exited, code=killed, status=11/SEGV
Feb 11 06:00:11 osmc systemd[1]: hyperion.service: Failed with result 'signal'.
Feb 11 06:00:11 osmc systemd[1]: hyperion.service: Consumed 1.826s CPU time.
System
Hyperion Server:
- Build: Lord-Grey-e6291e9/da79997-1770056999
- Build time: 2026-02-02 22:49:31
- Build type: Release
- Git Remote: https://github.com/hyperion-project/hyperion.ng
- Version: 2.2.0
- UI Lang: pl (BrowserLang: pl)
- UI Access: default
- Avail Screen Cap.: dispmanx,framebuffer,qt,drm
- Avail Video Cap.: v4l2
- Avail Audio Cap.: audio
- Avail Services: boblight,cec,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
- Config database: /root/.hyperion/db/hyperion.db
- Database: read/write
- Mode: Non-GUI
Hyperion Server OS:
- Distribution: Open Source Media Center
- Architecture: arm
- CPU Model: ARMv7 Processor rev 4 (v7l)
- CPU Type: Raspberry Pi 3 Model B Plus Rev 1.3
- CPU Revision: a020d3
- CPU Hardware: BCM2835
- Kernel: linux (5.15.92-1-osmc (WS: 32))
- Root/Admin: true
- Qt Version: 5.15.2
- Python Version: 3.9.2
- Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36