Crash Explanation:
Your box crashed with a SIGSEGV when entering the CI (Common Interface) menu and pressing OK while no valid CAM/slot was detected. The crash signature indicates a NULL pointer dereference in the CI handling path (calling `getSlotID()` on a missing slot). Additional `gAccel alloc failed` messages point to OSD/GPU surface allocation pressure (heavy skin + active transcoding), which likely *contributed to instability* but did not directly cause the segfault.
This is the order it seems::
Boot: Enigma2 starts; TranscodingSetup enables two encoders (H.264, ~2 Mbps, 50 fps, 480p).
Navigation: You open --> Main Menu --> Setup --> CI (“CiSelection” screen).
Kernel notes earlier: cannot recognize card --> the CI slot could not recognize a CAM/PC-Card.
While drawing screens, multiple gAccel / gSurface accelAlloc failed messages occur (OSD memory pressure).
On OK in the CI screen, Enigma2 crashes with SIGSEGV in the CI stack (`eDVBCISlot::getSlotID --> eDVBCIInterfaces::reset`). Fault Address 0x0000000c is a classic NULL deref (offset 0xC from NULL).
Possible causes:
(1) CI code path does not guard against absent/undetected CAM and dereferences a NULL slot pointer when handling OK in the CI screen.
(2) OSD memory pressure from a heavy skin and concurrent dual transcoding (two encoders) produced accelerated-surface allocation failures and made the UI more brittle.
(3) CI+ helper plugin (Ciplushelper) warning at startup; generally harmless, but worth disabling during tests to remove variables.
1. Cold reboot (power cycle).
2. If using a CAM, reseat it, and/or try the other CI slot; boot with the CAM already inserted.
3. Verify detection.
There are other tests and evaluations you may do, but choosing a skin that is lighter along with making sure your device is properly seated might help. Also see if the same problem exists when you swap slots.
IMO, the vuduo4kse is a helluva box to handle all that you are throwing at it. But everything has its limits. Best of luck with finding a permanent solution. I wonder if the slot is going bad?...Carefully check the slot hardware!