#1120386 startx error on Trixie

Package:
general
Source:
general
Submitter:
Kyrylo Orel
Date:
2025-11-16 23:19:01 UTC
Severity:
normal
Tags:
#1120386#5
Date:
2025-11-08 15:52:12 UTC
From:
To:
Dear Debian devs,

I have spotted a bug in Trixie where you have a chance of booting into CLI
mode and typing in startx gives you an error of "No screens found!" even if
I have HDMI plugged in, and the bug is permanent so you're stuck in CLI
forever and this bug annoys me so much and other people too. Maybe it
thinks its in headless mode but it really isn't, and its related to Xorg. I
suggest you use this thing:

hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

in /boot/config.txt.
Hope to get a Trixie update soon.

#1120386#10
Date:
2025-11-10 14:31:19 UTC
From:
To:
All my physical systems (half a dozen different devices) boot into a
Linux virtual terminal from where I run `startx` after logging into
a shell prompt. This works fine on all of them, including ones with
fixed panels as well as those with monitors attached via DisplayPort
or HDMI. I don't manually override detection, just rely on the
default configs.

While I'm running sid instead of trixie everywhere, the versions of
relevant packages now in trixie passed through sid and I never
observed any problems with this configuration, so my guess is that
there's something unusual about your specific hardware causing X not
to see your monitor as connected for some reason. More detail would
be helpful to track it down.

#1120386#15
Date:
2025-11-16 23:17:36 UTC
From:
To:
Control: tag -1 moreinfo

That config file is a Raspberry Pi thing, isn't it?  Where did you get
the Debian image you are using from?

Ben.