Le mar. 22 déc. 2020 à 20:58, Richard Shaw <hobbes1069@xxxxxxxxx> a écrit : > > I was able to ssh in after reloading Fedora Workstation adding the public key. > > I was then able to do a dnf update, however, upon reboot I no longer get a graphical boot. Looking through the journal now, I see this on the current boot but no instance of it on the previous boot: > > Dec 22 14:28:37 nano.localdomain org.gnome.Shell.desktop[1452]: The XKEYBOARD keymap compiler (xkbcomp) reports: > Dec 22 14:28:37 nano.localdomain org.gnome.Shell.desktop[1452]: > Internal error: Could not resolve keysym XF86FullScreen > Dec 22 14:28:37 nano.localdomain org.gnome.Shell.desktop[1452]: Errors from xkbcomp are not fatal to the X server I have this error in all gdm sessions inclusing x86_64 desktop, so it's not significant. > Too much other crud in the journal to do a detailed comparison. Actually, I don't have a nano, but a jetson-tx1 (so using the very same tegra210 SOC), and from time to time, gdm fails to run into wayland for any reason and try to run Xorg. With current kernel/xorg/mesa in fedora, the jetson can't have a chance to run into Xorg in accelerated mode, it would need Xorg from master to deal with it. It's possible that Xfce manage to work because this DE doesn't wire the acceleration automatically (pretty much with how optimus works on desktop). One way to workaround the problem might be to restart gdm service once fully booted... Hope this helps. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
