Created attachment 1471202 [details] journal logs for the failled boot Description of problem: Boot fails after upgrading kernel to 4.17.7 Wayland crashes, rebooting to the previous kernel, 4.17.5, fixes the issue. The journal contains the following crash log: jul 27 20:26:35 Mithrandir.bogado.net kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready jul 27 20:26:35 Mithrandir.bogado.net gnome-shell[1129]: X Wayland crashed; exiting jul 27 20:26:35 Mithrandir.bogado.net gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 jul 27 20:26:35 Mithrandir.bogado.net gnome-session-binary[1032]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 jul 27 20:26:35 Mithrandir.bogado.net gnome-session-binary[1032]: Unrecoverable failure in required component org.gnome.Shell.desktop jul 27 20:26:35 Mithrandir.bogado.net audit[865]: USER_END pid=865 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_key> jul 27 20:26:35 Mithrandir.bogado.net audit[865]: USER_LOGOUT pid=865 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=success' jul 27 20:26:35 Mithrandir.bogado.net audit[865]: CRED_DISP pid=865 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_gdm,pam_permit acct="bogado" exe="/usr/libexec/gdm-session-worker" host> jul 27 20:26:35 Mithrandir.bogado.net gdm-autologin][865]: pam_unix(gdm-autologin:session): session closed for user bogado jul 27 20:26:35 Mithrandir.bogado.net gdm[843]: GdmDisplay: display lasted 1.422188 seconds jul 27 20:26:35 Mithrandir.bogado.net gdm[843]: GLib: g_variant_new_string: assertion 'string != NULL' failed jul 27 20:26:35 Mithrandir.bogado.net systemd-coredump[1162]: Process 1160 (Xwayland) of user 1000 dumped core. Stack trace of thread 1160: #0 0x00007f63a6c9afeb raise (libc.so.6) #1 0x00007f63a6c855c1 abort (libc.so.6) #2 0x0000000000594de0 OsAbort (Xwayland) #3 0x000000000059a009 AbortServer (Xwayland) #4 0x000000000059ae7d FatalError (Xwayland) #5 0x0000000000421c7c xwl_log_handler (Xwayland) #6 0x00007f63a917c20e wl_log (libwayland-client.so.0) #7 0x00007f63a917757c display_handle_error (libwayland-client.so.0) #8 0x00007f63a63b203e ffi_call_unix64 (libffi.so.6) #9 0x00007f63a63b19ff ffi_call (libffi.so.6) #10 0x00007f63a917b2dd wl_closure_invoke (libwayland-client.so.0) #11 0x00007f63a9177a39 dispatch_event.isra.6 (libwayland-client.so.0) #12 0x00007f63a9178f2f wl_display_dispatch_queue_pending (libwayland-client.so.0) #13 0x00007f63a917939b wl_display_roundtrip_queue (libwayland-client.so.0) #14 0x0000000000421f9c xwl_screen_init (Xwayland) #15 0x0000000000558b5b AddScreen (Xwayland) #16 0x00000000004234ae InitOutput (Xwayland) #17 0x000000000055c78d dix_main (Xwayland) #18 0x00007f63a6c8724b __libc_start_main (libc.so.6) #19 0x000000000042199a _start (Xwayland) Version-Release number of selected component (if applicable): kernel-4.17.7-200.fc28.x86_64 xorg-x11-server-Xwayland-1.19.6-8.fc28.x86_64 How reproducible: Booted twice and got it twice. Steps to Reproduce: 1. reboot a Lenovo Ideapad 4.1580 with kernel 4.17.7 2. Observe the boot reverting back to the text termnal without a login prompt.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
I had returned to XOrg for a while, but right now it seems to be working again. Thanks.
It seems that I spoke too early. The laptop is freezing again on the latest kernel (kernel-4.18.14-200.fc28.x86_64) but not on the previous one (kernel-4.18.13-200.fc28.x86_64) It does looks like it has something to do with the external monitor, as the boot seems to have proceeded fine until the second monitor was correctly plugged in and then I got a freeze.
This is a graphics issue, moving to the graphics team
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.