I debugged it, found that by default it will use gdm-wayland-session in greeter UI.
/usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart
After login the system, it will change to use the gdm-x-session, so this might be the root cause.
When I try to disable Wayland in gdm3, this issue is fixed, because it will use gdm-x-session all the time. So it might be a gdm3 issue.
cat /etc/gdm3/daemon.conf
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
Copy the comment from mutter bug.
I debugged it, found that by default it will use gdm-wayland-session in greeter UI. gdm3/gdm- wayland- session gnome-session --autostart /usr/share/ gdm/greeter/ autostart daemon. conf gdm/gdm. schemas for a list of available options.
/usr/lib/
After login the system, it will change to use the gdm-x-session, so this might be the root cause.
When I try to disable Wayland in gdm3, this issue is fixed, because it will use gdm-x-session all the time. So it might be a gdm3 issue.
cat /etc/gdm3/
# GDM configuration storage
#
# See /usr/share/
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false