Bug#1041407: (EE) modeset(0): Failed to set CTM property: -13. (EE) modeset(0): failed to set mode: No such file or directory.

[AlMa]

Package: gdm3
Version: 43.0-3
Control: affects -1 xorg

In the journal I discovered the following errors (EE) that had been 
issued during boot:

/usr/libexec/gdm-x-session[992]: (EE) modeset(0): Failed to set CTM 
property: -13
/usr/libexec/gdm-x-session[992]: (EE) modeset(0): failed to set mode: No 
such file or directory

The parts “(EE) modeset(0): Failed to set CTM property: -13” and “(EE) 
modeset(0): failed to set mode: No such file or directory” are shown in 
yellow. Here's what immediately preceded the error:

…
Jul 18 14:52:50 AnonymizedMachineName gdm-password][2074]: gkr-pam: 
unlocked login keyring
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2129 of process 2129 owned by '1000' high priority at nice 
level -11.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 7 
threads of 4 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2132 of process 2132 owned by '1000' high priority at nice 
level -11.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 8 
threads of 5 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2127 of process 2127 owned by '1000' high priority at nice 
level -11.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 9 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 9 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 9 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 9 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 9 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2180 of process 2129 owned by '1000' RT at priority 20.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 10 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 10 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 10 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2182 of process 2127 owned by '1000' RT at priority 20.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 11 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName wireplumber[2129]: Failed to set 
scheduler settings: Die Operation ist nicht erlaubt
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Successfully 
made thread 2184 of process 2132 owned by '1000' RT at priority 20.
Jul 18 14:52:50 AnonymizedMachineName rtkit-daemon[997]: Supervising 12 
threads of 6 processes of 2 users.
Jul 18 14:52:50 AnonymizedMachineName wireplumber[2129]: SPA handle 
'api.libcamera.enum.manager' could not be loaded; is it installed?
Jul 18 14:52:50 AnonymizedMachineName wireplumber[2129]: PipeWire's 
libcamera SPA missing or broken. libcamera not supported.
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "28"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event5  - Power Button: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "31"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event4  - Power Button: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "32"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event3  - Sleep Button: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "33"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event1  - Microsoft Natural® Ergonomic Keyboard 4000: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "34"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "35"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event8  - USB2.0 FHD UVC WebCam: USB2.0 F: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "36"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event9  - USB2.0 FHD UVC WebCam: IR Camer: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "37"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event0  - USB Optical Mouse: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "38"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event7  - Eee PC WMI hotkeys: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(**) Option "fd" "34"
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) event2  - Microsoft Natural® Ergonomic Keyboard 4000: device removed
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(II) AIGLX: Suspending AIGLX clients for VT switch
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(EE) modeset(0): Failed to set CTM property: -13
Jul 18 14:52:51 AnonymizedMachineName /usr/libexec/gdm-x-session[992]: 
(EE) modeset(0): failed to set mode: No such file or directory
…

A higher-level error (which might be related or not) is that X.Org 
starts instead of Wayland (whereas before the upgrade from Debian 11/12 
to Debian 12, Wayland started).

I tried to get more information on the first of the two error messages:

# apropos gdm-x-session
gdm-x-session: nichts passendes.
# man gdm-x-session
Kein Handbucheintrag für gdm-x-session vorhanden
# apropos CTM
CTM: nichts passendes.
# apropos modeset
modesetting (4)      - video driver for framebuffer device
# man modesetting

The last call succeeds, but the man page contains no information on CTM. 
  However, I'd expect to get at least some idea on what is going on (at 
least on what CTM means and what is property “-13”) from locally 
installed documentation.

As for the second error, it would at least help to understand which file 
or directory is searched for.

As for repairing what goes wrong under the hood (if anything), here are 
some details for maintainers and developers:
The machine runs Debian 12 “bookworm”. The motherboard is ASUS WS C422 
PRO/SE with a built-in graphic chip ASPEED AST2500 64MB (to which 
nothing is connected) and an inserted PCIe graphics card NVIDIA® 
GeForce® GTX1660 Ti 6GB (to which a 2560×1440 monitor is connected via 
DisplayPort).

Gratefully,
AlMa0