Description of problem: Attempting to boot the XFCE spin on the Wandboard Quad (i.MX6) fails with only boot messages displayed on screen. Version-Release number of selected component (if applicable): lightdm-1.28.0-7.fc30.armv7hl How reproducible: Everytime Steps to Reproduce: 1. Boot a recent Fedora 30 Desktop image 2. Boot will hang with boot messages displayed. Actual results: coredumpctl debug PID: 1086 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Tue 2019-04-09 16:54:26 EDT (6min ago) Command Line: /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch Executable: /usr/libexec/Xorg Control Group: /system.slice/lightdm.service Unit: lightdm.service Slice: system.slice Boot ID: 8e046c090f484078a42d81d80ad3cde1 Machine ID: 20b27699049a4079b5d8e978cadc895e Hostname: wand Storage: /var/lib/systemd/coredump/core.Xorg.0.8e046c090f484078a42d81d80ad3cde1.1086.1554843266000000.lz4 Message: Process 1086 (Xorg) of user 0 dumped core. Stack trace of thread 1086: #0 0x00000000b6832200 __GI_raise (libc.so.6) #1 0x00000000b681d364 __GI_abort (libc.so.6) #2 0x00000000005c7430 OsAbort (Xorg) #3 0x00000000005cd2d8 AbortServer (Xorg) #4 0x00000000005cdcf4 FatalError (Xorg) #5 0x00000000004944d0 xf86PostProbe (Xorg) #6 0x00000000004a23e8 InitOutput (Xorg) #7 0x0000000000464698 dix_main (Xorg) #8 0x00000000b681d87c __libc_start_main (libc.so.6) #9 0x000000000044d108 .annobin_vidmode.c_end.startup (Xorg)
Created attachment 1553978 [details] backtrace
Looks more like a X issue, lightdm isn't even mentioned in the meagre backtrace.
@Adam W I believe this issue might be a release blocker?
Shouldnt be a release blocker, this is only happening on the Wandboard.
Can you get the X logs from anywhere? The backtrace looks like X basically intentionally died on a known error, so that ought to be logged.
oh, hah. Looking at the full backtrace not the short one, the error is actually the very same as in the nomodeset UEFI bug: "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" Not sure if that means these are the same bug, but...obviously related. That's https://bugzilla.redhat.com/show_bug.cgi?id=1693409 .
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.