F34 hanging after boot

Which graphic card /driver do you use?

AMD Kaveri [Radeon R5 Graphics]

I have another system (AMD Stoney) that doesn’t have the issue.

strange at all- I have myself AMD Ryzen 5 3500U and no issues

1 Like

The full log is too big. Just included those gnome related entry of journal when boot the gdm hanging deployment.

cat gdm-hangs.journal.log | grep gnome

Summary
May 17 21:39:48 amdf gnome-session[1114]: gnome-session-binary[1114]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-session-binary[1114]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-session[1114]: gnome-session-binary[1114]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-session-binary[1114]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-session[1114]: gnome-session-binary[1114]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-session-binary[1114]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
May 17 21:39:48 amdf gnome-shell[1128]: Adding device '/dev/dri/card0' (radeon) using non-atomic mode setting.
May 17 21:39:49 amdf gnome-shell[1128]: Boot VGA GPU /dev/dri/card0 selected as primary
May 17 21:39:50 amdf gnome-shell[1128]: Disabling DMA buffer screen sharing for driver 'radeon'.
May 17 21:39:50 amdf gnome-shell[1128]: Using public X11 display :1024, (using :1025 for managed services)
May 17 21:39:50 amdf gnome-shell[1128]: Using Wayland display name 'wayland-0'
May 17 21:39:50 amdf audit[1128]: AVC avc:  denied  { write } for  pid=1128 comm="gnome-shell" name="dbus-vc4GbD3MfA" dev="tmpfs" ino=48 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmp_t:s0 tclass=sock_file permissive=0
May 17 21:39:50 amdf gnome-shell[1128]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-vc4GbD3MfA: Permission denied
May 17 21:39:50 amdf org.gnome.Shell.desktop[1245]: glamor: No eglstream capable devices found
May 17 21:39:50 amdf gnome-shell[1128]: Skipping parental controls support as it’s disabled
May 17 21:39:50 amdf gnome-shell[1128]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
May 17 21:39:50 amdf gnome-shell[1128]: Will monitor session c1
May 17 21:39:51 amdf polkitd[818]: Registered Authentication Agent for unix-session:c1 (system bus name :1.35 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 17 21:39:52 amdf gnome-shell[1128]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
May 17 21:39:52 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:39:52 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:39:52 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:39:52 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:39:52 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:39:52 amdf org.gnome.Shell.desktop[1476]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 17 21:39:52 amdf org.gnome.Shell.desktop[1476]: > Warning:          Could not resolve keysym XF86FullScreen
May 17 21:39:52 amdf org.gnome.Shell.desktop[1476]: Errors from xkbcomp are not fatal to the X server
May 17 21:39:53 amdf gnome-session-binary[1114]: Entering running state
May 17 21:39:54 amdf gnome-shell[1128]: Failed to init X11 display: Unknown error
May 17 21:39:54 amdf org.gnome.Shell.desktop[1573]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 17 21:39:54 amdf org.gnome.Shell.desktop[1573]: > Warning:          Unsupported maximum keycode 569, clipping.
May 17 21:39:54 amdf org.gnome.Shell.desktop[1573]: >                   X11 cannot support keycodes above 255.
May 17 21:39:54 amdf org.gnome.Shell.desktop[1573]: > Warning:          Could not resolve keysym XF86FullScreen
May 17 21:39:54 amdf org.gnome.Shell.desktop[1573]: Errors from xkbcomp are not fatal to the X server
May 17 21:40:04 amdf gnome-shell[1128]: Registering session with GDM
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:05 amdf org.gnome.Shell.desktop[1645]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 17 21:40:05 amdf org.gnome.Shell.desktop[1645]: > Warning:          Unsupported maximum keycode 569, clipping.
May 17 21:40:05 amdf org.gnome.Shell.desktop[1645]: >                   X11 cannot support keycodes above 255.
May 17 21:40:05 amdf org.gnome.Shell.desktop[1645]: > Warning:          Could not resolve keysym XF86FullScreen
May 17 21:40:05 amdf org.gnome.Shell.desktop[1645]: Errors from xkbcomp are not fatal to the X server
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument
May 17 21:40:09 amdf gnome-shell[1128]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument

Another full log is attached to the bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1960937

1 Like

@sampsonf
Thx a lot and especially reporting it as a bug on bugzilla! :wink:

1 Like

As tested with Fedora 34,
The GOLD version works but with latest updates, GDM also hangs on startup.

Update:
Under Fedora 34 and Silverblue 34, the GDM issue is gone once switch over using the AMDGPU driver instead of RADEON driver.

Please see this for details:

1 Like

Fefora 34 not show up logins manager but only blank screen with cursor at top left of display.

I fresh install fedora 34 with gnome 40. Before updating fedora it work just fine. Now i simply run sudo dnf update and after that reboot the system.
Now gdm login is not showings. It blink cursor in left top of display.
So i use contrl + alt + fn + f3 to login through terminals and type command: startx it showing fine .
Can any one help me to fix this or i simply switch back to Ubuntu.
I really like fedora it pre-installed jdk which is amazing as developer.

I remember i make separate partition for 1024mb for boot during installation did it makings problem ?

Save me to fix this here systemctl status:

● fedora
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Tue 2021-05-18 16:17:02 IST; 5h 19min left
   CGroup: /
           ├─user.slice 
           │ └─user-1000.slice 
           │   ├─user@1000.service 
           │   │ ├─session.slice 
           │   │ │ ├─dbus-broker.service 
           │   │ │ │ ├─1836 /usr/bin/dbus-broker-launch --scope user
           │   │ │ │ └─1839 dbus-broker --log 4 --controller 10 --machine-id 0e>
           │   │ │ ├─pipewire-pulse.service 
           │   │ │ │ └─1829 /usr/bin/pipewire-pulse
           │   │ │ └─pipewire.service 
           │   │ │   ├─1827 /usr/bin/pipewire
           │   │ │   └─1841 /usr/bin/pipewire-media-session
           │   │ └─init.scope 
           │   │   ├─1570 /usr/lib/systemd/systemd --user
           │   │   └─1573 (sd-pam)
           │   └─session-2.scope 
           │     ├─1555 login -- anuj
           │     ├─1581 -bash
           │     ├─1609 /usr/bin/sh /usr/bin/startx
           │     ├─1631 xinit /etc/X11/xinit/xinitrc -- /usr/bin/X :0 vt3 -keep>
           │     ├─1632 /usr/libexec/Xorg :0 vt3 -keeptty -auth /home/anuj/.ser>
           │     ├─1658 /usr/libexec/gnome-session-binary
           │     ├─1669 dbus-launch --sh-syntax --exit-with-session
           │     ├─1670 /usr/bin/dbus-daemon --syslog --fork --print-pid 6 --pr>
           │     ├─1694 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
           │     ├─1716 /usr/libexec/at-spi-bus-launcher
           │     ├─1721 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/>
           │     ├─1725 /usr/libexec/gvfsd
           │     ├─1730 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
           │     ├─1750 /usr/bin/gnome-keyring-daemon --start --components=ssh
           │     ├─1759 /usr/bin/gnome-shell
           │     ├─1786 ibus-daemon --panel disable --xim
           │     ├─1790 /usr/libexec/ibus-dconf
           │     ├─1791 /usr/libexec/ibus-extension-gtk3
           │     ├─1795 /usr/libexec/ibus-x11 --kill-daemon
           │     ├─1798 /usr/libexec/ibus-portal
           │     ├─1802 /usr/libexec/xdg-permission-store
           │     ├─1810 /usr/libexec/gnome-shell-calendar-server
           │     ├─1815 /usr/libexec/at-spi2-registryd --use-gnome-session
           │     ├─1826 /usr/libexec/evolution-source-registry
           │     ├─1849 /usr/libexec/goa-daemon
           │     ├─1864 /usr/libexec/evolution-calendar-factory
           │     ├─1868 /usr/libexec/gvfs-udisks2-volume-monitor
           │     ├─1878 /usr/libexec/gvfs-mtp-volume-monitor
           │     ├─1883 /usr/libexec/gvfs-gphoto2-volume-monitor
           │     ├─1888 /usr/libexec/gvfs-afc-volume-monitor
           │     ├─1894 /usr/libexec/gvfs-goa-volume-monitor
           │     ├─1906 /usr/libexec/dconf-service
           │     ├─1907 /usr/libexec/evolution-addressbook-factory
           │     ├─1928 /usr/libexec/goa-identity-service
           │     ├─1940 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Not>
           │     ├─1958 /usr/libexec/gsd-usb-protection
           │     ├─1961 /usr/libexec/gsd-media-keys
           │     ├─1966 /usr/libexec/gsd-rfkill
           │     ├─1969 /usr/libexec/gsd-a11y-settings
           │     ├─1971 /usr/libexec/gsd-wacom
           │     ├─1973 /usr/libexec/gsd-wwan
           │     ├─1975 /usr/libexec/gsd-power
           │     ├─1977 /usr/libexec/gsd-screensaver-proxy
           │     ├─1980 /usr/libexec/gsd-color
           │     ├─1981 /usr/libexec/gsd-xsettings
           │     ├─1984 /usr/libexec/gsd-print-notifications
           │     ├─1985 /usr/libexec/gsd-sharing
           │     ├─1987 /usr/libexec/gsd-datetime
           │     ├─1989 /usr/libexec/gsd-smartcard
           │     ├─1991 /usr/libexec/gsd-housekeeping
           │     ├─1996 /usr/libexec/gsd-sound
           │     ├─1998 /usr/libexec/gsd-keyboard
           │     ├─2050 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSav>
           │     ├─2128 /usr/libexec/gsd-printer
           │     ├─2145 /usr/libexec/evolution-data-server/evolution-alarm-noti>
           │     ├─2147 /usr/libexec/gsd-disk-utility-notify
           │     ├─2149 /usr/libexec/tracker-miner-fs-3
           │     ├─2155 /usr/bin/gnome-software --gapplication-service
           │     ├─2174 /usr/bin/abrt-applet --gapplication-service
           │     ├─2230 /usr/libexec/ibus-engine-simple
           │     ├─2350 /usr/bin/python3 /usr/bin/gnome-abrt -p /var/spool/abrt>
           │     ├─2493 /usr/libexec/abrt-handle-event -e report-gui -- /var/sp>
           │     ├─2494 report-gtk -- /var/spool/abrt/ccpp-2021-05-18-09:17:03.>
           │     ├─2506 /usr/bin/python3 -u /usr/bin/abrt-action-perform-ccpp-a>
           │     ├─2507 /bin/sh -c abrt-retrace-client batch --dir "$DUMP_DIR" >
        abrt-action-analyze-backtrace
           │     ├─2508 abrt-retrace-client batch --dir /var/spool/abrt/ccpp-20>
           │     ├─2521 /usr/libexec/abrt-handle-event -e report-gui -- /var/sp>
           │     ├─2522 report-gtk -- /var/spool/abrt/ccpp-2021-05-18-10:33:02.>
           │     ├─2534 /usr/bin/python3 -u /usr/bin/abrt-action-perform-ccpp-a>
           │     ├─2535 /bin/sh -c abrt-retrace-client batch --dir "$DUMP_DIR" >
        abrt-action-analyze-backtrace
           │     ├─2536 abrt-retrace-client batch --dir /var/spool/abrt/ccpp-20>
           │     ├─2555 /usr/libexec/gnome-terminal-server
           │     ├─2562 bash
           │     ├─2608 systemctl status
           │     └─2609 less
           ├─init.scope 
           │ └─1 /usr/lib/systemd/systemd --switched-root --system --deserializ>
           └─system.slice 
             ├─abrt-journal-core.service 
             │ └─724 /usr/bin/abrt-dump-journal-core -D -T -f -e
             ├─low-memory-monitor.service 
             │ └─677 /usr/libexec/low-memory-monitor
             ├─packagekit.service 
             │ ├─1142 /usr/libexec/packagekitd
             │ └─2599 gpg-agent --homedir /var/cache/PackageKit/34/metadata/fed>
             ├─systemd-udevd.service 
             │ └─514 /usr/lib/systemd/systemd-udevd
             ├─dbus-broker.service 
             │ ├─688 /usr/bin/dbus-broker-launch --scope system --audit
             │ └─713 dbus-broker --log 4 --controller 9 --machine-id 0e8ffe8311>
             ├─systemd-homed.service 
             │ └─681 /usr/lib/systemd/systemd-homed
             ├─polkit.service 
             │ └─741 /usr/lib/polkit-1/polkitd --no-debug
             ├─rtkit-daemon.service 
             │ └─678 /usr/libexec/rtkit-daemon
             ├─chronyd.service 
             │ └─709 /usr/sbin/chronyd
             ├─bluetooth.service 
             │ └─674 /usr/libexec/bluetooth/bluetoothd
             ├─auditd.service 
             │ └─646 /sbin/auditd
             ├─accounts-daemon.service 
             │ └─759 /usr/libexec/accounts-daemon
             ├─abrt-xorg.service 
             │ └─726 /usr/bin/abrt-dump-journal-xorg -fxtD
             ├─wpa_supplicant.service 
             │ └─880 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_suppli>
             ├─libvirtd.service 
             │ ├─1014 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/de>
             │ └─1015 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/de>
             ├─ModemManager.service 
             │ └─672 /usr/sbin/ModemManager
             ├─systemd-journald.service 
             │ └─502 /usr/lib/systemd/systemd-journald
             ├─fwupd.service 
             │ └─2299 /usr/libexec/fwupd/fwupd
             ├─colord.service 
             │ └─1385 /usr/libexec/colord
             ├─uresourced.service 
             │ └─934 /usr/libexec/uresourced
             ├─NetworkManager.service 
             │ └─779 /usr/sbin/NetworkManager --no-daemon
             ├─gdm.service 
             │ └─888 /usr/sbin/gdm
             ├─systemd-machined.service 
             │ └─682 /usr/lib/systemd/systemd-machined
             ├─switcheroo-control.service 
             │ └─680 /usr/libexec/switcheroo-control
             ├─gssproxy.service 
             │ └─798 /usr/sbin/gssproxy -D
             ├─abrtd.service 
             │ └─710 /usr/sbin/abrtd -d -s
             ├─firewalld.service 
             │ └─675 /usr/bin/python3 -s /usr/sbin/firewalld --nofork --nopid
             ├─systemd-userdbd.service 
             │ ├─ 909 /usr/lib/systemd/systemd-userdbd
             │ ├─1556 systemd-userwork
             │ ├─1557 systemd-userwork
             │ └─1558 systemd-userwork
             ├─alsa-state.service 
             │ └─727 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/als>
             ├─system-dbus\x2d:1.14\x2dorg.freedesktop.problems.slice 
             │ └─dbus-:1.14-org.freedesktop.problems@1.service 
             │   └─2280 /usr/sbin/abrt-dbus -t133
             ├─sssd.service 
             │ ├─679 /usr/sbin/sssd -i --logger=files
             │ ├─757 /usr/libexec/sssd/sssd_be --domain implicit_files --uid 0 >
             │ └─758 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
             ├─cups.service 
             │ └─790 /usr/sbin/cupsd -l
             ├─pcscd.service 
             │ └─2084 /usr/sbin/pcscd --foreground --auto-exit
             ├─upower.service 
             │ └─685 /usr/libexec/upowerd
             ├─systemd-oomd.service 
             │ └─642 /usr/lib/systemd/systemd-oomd
             ├─systemd-resolved.service 
             │ └─643 /usr/lib/systemd/systemd-resolved
             ├─udisks2.service 
             │ └─684 /usr/libexec/udisks2/udisksd
             ├─sssd-kcm.service 
             │ └─1951 /usr/libexec/sssd/sssd_kcm --uid 0 --gid 0 --logger=files
             ├─system-getty.slice 
             │ └─getty@tty2.service 
             │   └─1554 /sbin/agetty -o -p -- \u --noclear tty2 linux
             ├─avahi-daemon.service 
             │ ├─673 avahi-daemon: running [fedora.local]
             │ └─712 avahi-daemon: chroot helper
             ├─systemd-logind.service 
             │ └─760 /usr/lib/systemd/systemd-logind
             └─abrt-oops.service 
               └─725 /usr/bin/abrt-dump-journal-oops -fxtD

1 Like

It sounds like the same issue

My error came after those components upgraded:

gnome-classic-session 40.0-1.fc34 -> 40.1-1.fc34
gnome-shell 40.0-6.fc34 -> 40.1-1.fc34
gnome-shell-extension-apps-menu 40.0-1.fc34 -> 40.1-1.fc34
gnome-shell-extension-common 40.0-1.fc34 -> 40.1-1.fc34
gnome-shell-extension-launch-new-instance 40.0-1.fc34 -> 40.1-1.fc34
gnome-shell-extension-places-menu 40.0-1.fc34 -> 40.1-1.fc34
gnome-shell-extension-window-list 40.0-1.fc34 -> 40.1-1.fc34
mutter 40.0-5.fc34 -> 40.1-1.fc34

Welcome @anuj900
Thx for asking your question and explaining your issue. I’ve moved your problem to this one bc it’s almost the same topic to be solved and discussed.

v/r
Andi

1 hour into using F34 , gdm started to give me “White Screen of Death” .

usual procedure now is to create a new user, try get a gnomeshell-GUI of the new user.

Funnily, this fixed it for the old, initial user account too ! :smirk:

tried for hours all sorts of troubleshooting but as usual, that only made it worse.

Kaveri + Radeon R600

May I ask what is white screen of death?

1 Like

It is like a white empty Desktop background made by gdm,

telling you to relogin because of unfixable crash . if you do , you come back to the white screen of death, of course.

sometimes, if you press the Windows-key, the gnomeshell app-folder shows.

release the windows-key , and the white screen of death rears its ugly head again.

sometimes, it also has a logout button and an icon like a “crying TV screen”.

or a sad-looking Screen icon.

1 Like

so in my case WSOD (as opposed to BSOD = blue windows crash screen) showed, even though gdm was kind of only semi-crashed.

weird, huh.

so WSOD is like the BSOD for MS Windows of Bill Gates, but white instead of blue.

comes, when the GUI crashed badly and won’t fix easily.

Summary:

This issue happens when the open source radeon drivers is using with gnome 40.1.

While waiting for future updates that might fix this issue, I am doing below as alternatives:

  1. avoid using gnome at the moment
  • Use i3 or sway
  • Use KDE/Plasma. As I use Silverblue, I rebased to Kinoite - which is in rawhide
  1. Do not use radeon
  • by adding two kernel boot parameters, amdgpu is used instead of radeon. But for me, sound over hdmi is not working, so I need to route sound over to bluetooth speakers .

Exactly my situation. I’m using an AMD RX 5700XT. The starting Fedora logo screen displays fine then I end up with the blank screen and blinking top left cursor. Logs are big and confusing so I tried getting what I thought is relevant.

I never got to get Gnome or anything GUI at all to work. I tried previous kernels - no luck.

I hope this helps.

Thanks.

/usr/libexec/gdm-x-session[1431]: (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_video_caps_info)
(EE) AIGLX error: unable to load driver swrast
(EE) GLX: could not load software renderer
(II) GLX: no usable GL providers found for screen 0
AMDGPU(0): Setting screen physical size to 889 x 277
Xorg: /usr/include/xorg/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized’ failed.

2 Likes

Please help comment at the bug so that it will get more exposure.

2 Likes

OK, I commented using FAS credentials via Epiphany browser and not entering the password myself. cool!

2 Likes

I got a suggestion at: (And this allowd Gnome to start for me)
https://bugzilla.redhat.com/show_bug.cgi?id=1960937#c12

[ Jonas Ådahl] 2021-05-26 20:32:39 UTC

Try adding DRIVERS=="radeon", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers" to /usr/lib/udev/rules.d/61-mutter.rules and remoot.

As I am using Silverblue, which /usr is readonly.

How can I modify udev rules under Silverblue?

Updated below:
OK. I find out how

1 Like

The above suggestion is now publish as a fix ON_QA:

https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.