Raspberry Pi 2 and Pi 3 wait for a display instead of crash-looping

With no screen connected at boot, or a TV that is slow to wake up, the viewer on a Raspberry Pi 2 or 3 now waits and starts on its own once a display appears.

From Anthias 2026.05.2, a Raspberry Pi 2 or Pi 3 that boots without a working display waits for one, and starts the viewer by itself once a screen is connected or switched on, with no restart. That covers a panel that's powered off, a TV switched on after the Pi, and a TV that's slow to bring up HDMI.

Before, the viewer couldn't start in that situation. It logged Unable to figure out framebuffer device and no screens available, crashed with malloc(): unaligned tcache chunk detected, and the container restarted in a loop.

While it waits, the viewer logs no framebuffer (/dev/fb0) yet once, then a reminder every minute.

Put Screenly on your screens

Book a demo and we will walk you and your IT team through it, or start a free trial on a screen you already have.