Hide Forgot
Created attachment 1213039 [details] xrandr output under weston Description of problem: I have 2 VGA monitors, one connected to the motherboard of my Asus desktop & one to a graphics card. The one connected to the graphics card is not detectable by Wayland, but works fine in X11. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce + actual results: 1. Log in with "GNOME" setting, both monitors are activated and can be configured in settings. 2. Log out. 3. Log in with "GNOME on Wayland" setting (i.e. mutter), only the motherboard-connected monitor is detected/configurable. 4. Log out. 5. Hit CTRL-Fn. The monitor connected to the motherboard shows a console login. 6. Run weston-launch, only the motherboard-connected monitor is detected/configurable. Bonus steps: 7. Log in with "GNOME" setting, both monitors are activated and can be configured in settings. 8. Hit CTRL-Fn. The monitor connected to the motherboard shows a console login. 9. Run weston-launch, only the the motherboard-connected monitor is detected/configurable. The monitor connected to the graphics card continues to display the X11 GNOME desktop, albeit frozen. Expected results: Both monitors can be configured with "GNOME on Wayland" and weston. Additional info: Possible previous report at https://bugzilla.gnome.org/show_bug.cgi?id=764584 but I suspect this is not a GNOME issue.
Created attachment 1213040 [details] xrandr output under x11
Created attachment 1213041 [details] lspci output
Seem similar to bug #1349672
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.