Description of problem: The system was upgraded to F36 yesterday. While it is booting, it starts in textmode , switches to graphicalmode for the LUKS password. If entered it boots the system up to the point, when GDM is started. Instead of presenting the userlogin context, the display is switched off, no output to the gfx card anymore, so the connected monitor switches to energysafemode. The following observations can be made: a) system starts up normally, all processes required for a Desktopsession ( including GDM ) a running. SSH Login via network works, RDP Login works b) while logged in via ssh as root, a "startx" command leads to a normal Gnome-Shell ROOT Desktopsession on the display. The connected monitor is starting to show this. c) while logged in via ssh as root, "systemctl isolate multi-user" switches correctly to text only mode. "systemctl isolate graphical" switches correctly to the graphical mode, except, that GDMs Logincontext is not presented, same as when the system has booted up. d) no relevant output of X11 XORG context in systemlog. Conclusion: GDM does not work correctly Tried solutions: - Reboot - reinstall gdm package no change. Version-Release number of selected component (if applicable): Name : gdm Epoch : 1 Version : 42.0 Release : 2.fc36 xorg-x11-drv-qxl-0.1.5-20.fc35.x86_64 xorg-x11-drv-vmware-13.2.1-16.fc35.x86_64 xorg-x11-drv-wacom-serial-support-1.0.0-1.fc36.x86_64 xorg-x11-server-common-1.20.14-7.fc36.x86_64 xorg-x11-xauth-1.1.1-2.fc36.x86_64 xorg-x11-xinit-1.4.0-14.fc36.x86_64 xorg-x11-server-Xwayland-22.1.3-1.fc36.x86_64 abrt-addon-xorg-2.15.1-1.fc36.x86_64 xorg-x11-drv-libinput-1.2.1-1.fc36.x86_64 xorg-x11-server-Xorg-1.20.14-7.fc36.x86_64 xorg-x11-drv-amdgpu-22.0.0-1.fc36.x86_64 xorg-x11-drv-ati-19.1.0-7.fc36.x86_64 xorg-x11-drv-evdev-2.10.6-11.fc36.x86_64 xorg-x11-drv-fbdev-0.5.0-10.fc36.x86_64 xorg-x11-drv-intel-2.99.917-52.20200205.fc36.x86_64 xorg-x11-drv-nouveau-1.0.17-3.fc36.x86_64 xorg-x11-drv-openchrome-0.6.400-3.20210215git5dbad06.fc36.x86_64 xorg-x11-drv-vesa-2.5.0-3.fc36.x86_64 xorg-x11-drv-wacom-1.0.0-1.fc36.x86_64 xorg-x11-font-utils-7.5-53.fc36.x86_64 libwayland-client-1.21.0-1.fc36.x86_64 libwayland-server-1.21.0-1.fc36.x86_64 libwayland-egl-1.21.0-1.fc36.x86_64 libwayland-cursor-1.21.0-1.fc36.x86_64 xisxwayland-1-3.fc36.x86_64 xorg-x11-server-Xwayland-22.1.3-1.fc36.x86_64 qt5-qtwayland-5.15.6-1.fc36.x86_64 gnome-session-wayland-session-42.0-1.fc36.x86_64
Nov 09 15:56:16 <SERVER> systemd[1]: Stopping gdm.service - GNOME Display Manager... Nov 09 15:56:16 <SERVER> gdm-launch-environment][9635]: pam_unix(gdm-launch-environment:session): session closed for user gdm Nov 09 15:56:16 <SERVER> gdm-launch-environment][9635]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Nov 09 15:56:17 <SERVER> systemd[1]: gdm.service: Deactivated successfully. Nov 09 15:56:17 <SERVER> systemd[1]: Stopped gdm.service - GNOME Display Manager. Nov 09 15:56:17 <SERVER> systemd[1]: Starting gdm.service - GNOME Display Manager... Nov 09 15:56:17 <SERVER> systemd[1]: Started gdm.service - GNOME Display Manager. Nov 09 15:56:17 <SERVER> systemd-logind[4123]: New session c9 of user gdm. Nov 09 15:56:17 <SERVER> systemd[1]: Started session-c9.scope - Session c9 of User gdm. Nov 09 15:56:17 <SERVER> gdm-launch-environment][10032]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=42) by LOGIN(uid=0) Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=42 pid=10049 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.a11y.Bus' Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=42 pid=10049 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=42 pid=10049 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10073]: dbus-daemon[10073]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=42 pid=10049 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10073]: dbus-daemon[10073]: Successfully activated service 'org.a11y.atspi.Registry' Nov 09 15:56:17 <SERVER> /usr/libexec/gdm-wayland-session[10100]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 09 15:56:17 <SERVER> org.gnome.Shell.desktop[10049]: Window manager warning: Failed to parse saved session file: Datei »/var/lib/gdm/.config/mutter/sessions/10cba955edbc2fc358166800577723673300000100410000.ms« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.gnome.Shell.Notifications' Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.gtk.vfs.Daemon' requested by ':1.18' (uid=42 pid=10127 comm="ibus-daemon --panel disable" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.gtk.vfs.Daemon' Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.freedesktop.systemd1' requested by ':1.16' (uid=42 pid=10109 comm="/usr/libexec/gsd-sharing" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=42 pid=10127 comm="ibus-daemon --panel disable" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.freedesktop.portal.IBus' Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.gnome.ScreenSaver' requested by ':1.27' (uid=42 pid=10146 comm="/usr/libexec/gsd-power" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Activating service name='org.freedesktop.portal.IBus' requested by ':1.34' (uid=42 pid=10280 comm="ibus-daemon --panel disable -r --xim" label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.freedesktop.portal.IBus' Nov 09 15:56:18 <SERVER> /usr/libexec/gdm-wayland-session[10040]: dbus-daemon[10040]: [session uid=42 pid=10040] Successfully activated service 'org.gnome.ScreenSaver' Nov 09 15:56:18 <SERVER> gnome-shell[10049]: Registering session with GDM
Update: after installing & starting lightdm and lightdm-greeter instead of GDM, the login mask appears as expected, BUT: a) Login with Cinnamon: WORKS b) Login with GNOME WAYLAND : DOES NOT WORK => same black screen as with GDM c) Login with GNOME Xorg: WORKS!! Conclusion: Wayland not working!
switching component
Wayland is a set of protocol definitions, it has actually nothing to do with rendering issues when using a Wayland session. I am therefore moving this to mutter, as this is the Wayland compositor used with GNOME. Please attach the full `journalctl` logs of a session which fails to run properly, so we can investigate.
Created attachment 1923374 [details] Logfile from systemboot upto install of lightdm
This shows: Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Running GNOME Shell (using mutter 42.5) as a Wayland display server … Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Device '/dev/dri/card0' prefers shadow buffer … Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Added device '/dev/dri/card0' (ast) using atomic mode setting. … Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Created gbm renderer for '/dev/dri/card0' Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Boot VGA GPU /dev/dri/card0 selected as primary Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Initialized single buffered shadow fb for VGA-1 Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Disabling DMA buffer screen sharing (not hardware accelerated) Nov 09 10:34:48 <SERVER> gnome-shell[1759]: Disabling DMA buffer screen sharing (implicit modifiers not supported) … Nov 09 10:34:51 <SERVER> gnome-shell[1759]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found … Nov 09 10:40:00 <SERVER> gnome-shell[1759]: Page flip discarded: drmModeAtomicCommit: Das Argument ist ungültig Nov 09 10:41:00 <SERVER> gnome-shell[1759]: Failed to post KMS update: drmModeAtomicCommit: Das Argument ist ungültig Note that „Das Argument ist ungültig“ is basically „Invalid argument“ in plain English. Can you disabling KMS: * As root, add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment * reboot And see if that helps running GNOME Shell / mutter on Wayland on AST?
I can check .. Result: no change yet. gdm 17642 0.1 0.3 161020 57100 tty1 S+ 20:01 0:00 | \_ /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.DS39U1 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 # strings /proc/17642/environ |grep DEBUG MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 GJS_DEBUG_OUTPUT=stderr GJS_DEBUG_TOPICS=JS ERROR;JS LOG Quick question: As F35 was running fine with GDM / Mutter / Gnome Shell , doesn't that indicate a bug in the "new" F36 releases of those packages?
(In reply to customercare from comment #7) > > Quick question: As F35 was running fine with GDM / Mutter / Gnome Shell , > doesn't that indicate a bug in the "new" F36 releases of those packages? I *think* on F35, the udev rule that shipped with GDM would disable Wayland with AST.
Hi, From the logs, you are using an AST 2500 graphic card. This cards has some known issues with Mutter/wayland. There are patches upstream to fix this: https://cgit.freedesktop.org/drm/drm-misc/commit/?id=ce7fcf7003865a63983545fd8f84c04deb1b5dfd This one will fix the black screen error: Nov 09 10:34:51 <SERVER> gnome-shell[1759]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found but even with that the performance with Mutter/Wayland is so slow, that's unusable. This patch series will fix the performance issue: https://patchwork.freedesktop.org/series/109534/ We have to wait for kernel 6.2 to have this, so in the meantime using an Xorg session is preferable. I checked on my Fedora 36, and the file /usr/lib/udev/rules.d/61-gdm.rules doesn't have the rules to force Xorg for Aspeed chips.
I extracted the old version from F35 and compared it: ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false" has been reworked into a goto , but I can't find this part : DRIVER=="nvidia", ENV{GDM_HAS_VENDOR_NVIDIA_DRIVER}="1" DRIVER=="nvidia", RUN+="/usr/libexec/gdm-runtime-config set daemon PreferredDisplayServer xorg" SUBSYSTEM=="drm", KERNEL=="card[1-9]*", ENV{GDM_HAS_NVIDIA_DRIVER}=="1", RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false" ACTION=="add", SUBSYSTEM=="module", KERNEL=="nvidia_drm", ATTR{parameters/modeset}=="N", RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false but without an nvidia card, it won't do anything anyway. as it's working with lightdm, i will just use it. Can we keep this bug open for tracking and if fixed, send a broadcast for testing?
I think you need the lines found in this MR: https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171 # disable Wayland on aspeed chipsets ATTR{vendor}=="0x1a03", ATTR{device}=="0x2010", GOTO="gdm_disable_wayland" ATTR{vendor}=="0x1a03", ATTR{device}=="0x2000", GOTO="gdm_disable_wayland"
Right so this really was a bug in GDM :)
This gets critical now.. SAME BUG on INTEL graphics: 00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 540 (rev 0a) on a Surface Pro 4 .
Working workaround: # dnf --releasever=35 downgrade mutter works instantly after gmd restart
from mutter-42.5-3.fc36.x86_64 -> mutter-41.9-1.fc35.x86_64 + gnomeshell as complement downgrades
Can you provide dmesg logs when the "same bug" occurs on a Surface Pro 4 ? This is a very different hardware, so probably not the same bug as with Aspeed graphic.
Created attachment 1924175 [details] Surface Pro4 DMESG
Created attachment 1924176 [details] Surface Pro 4 Journal until the moment display went black
Surface Pro 4 Journal until the moment display went black added
I've seen nothing problematic in the kernel logs you sent. Can you send the logs from userspace (gnome-shell) too ?
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.