This could happen if a specific output name is set in the panel preferences and that output is then unplugged or the panel is run from a nested Wayland compositor. We gracefully handle this situation by just picking the first available monitor rather than refusing to start.