just a tracker to collect bugs we need to fix for wayland-by-default in f25
no need for complicated dependencies
I propose bug 1376447 to be included.
I also nominate bug 1376471. It's not a showstopper, but it's inconvenient, might be confusing, and harms the overall impression.
I also propose https://bugzilla.gnome.org/show_bug.cgi?id=771548 and https://bugzilla.gnome.org/show_bug.cgi?id=760745
I propose bug #1372479.
Also bug #1277165
I propose 1384036. One can't work with Wayland running on a VM under Gnome Boxes (system is completely unmanageable)
Correction of the bug link: https://bugzilla.redhat.com/show_bug.cgi?id=1384036
(In reply to Zdenek Chmelar from comment #7) > I propose 1384036. One can't work with Wayland running on a VM under Gnome > Boxes (system is completely unmanageable) (In reply to Zdenek Chmelar from comment #8) > Correction of the bug link: > https://bugzilla.redhat.com/show_bug.cgi?id=1384036 This bug report is a duplicate of bug #1266484, please close it as such. That bug is already a blocker bug.
(In reply to Christian Stadelmann from comment #9) > This bug report is a duplicate of bug #1266484, please close it as such. > That bug is already a blocker bug. Thank you Christian to pint me to that bug. I closed the one of mine #1266484
Lost among the bug numbers... Wanted to say I closed bug #1384036
I propose bug #1384560 (and the related issue for totem and so on). Creating screenshots is basic functionality IMO.
(In reply to J. Haas from comment #12) > I propose bug #1384560 (and the related issue for totem and so on). Creating > screenshots is basic functionality IMO. I don't think this should be a blocker. This is just a minor bug with a few applications (totem, gnome-maps and probably gnome-contacts as far as I can tell). I wouldn't take this as blocker. Instead, I've added it to WaylandRelated where it belongs.
I propose bug #1384637. I suspect this affects any dual monitor setups that use the "arrange combined displays" feature.
It is surprising that I don't see bug 1274451 mentioned here. This is huge regression comparing to X.
some changes are intentional
I think the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=766284 should be a blocker bug. Possible issues because of thise: * Clicking a notification/calendar or other items in gnome-shell Notification menu may not present a window if the application is already open (eg: media, polari, etc.) * Clicking on links in some other application may not show the previously opened browser. And several others.
https://bugzilla.gnome.org/show_bug.cgi?id=758677 should be a blocker bug too imho, because using wayland by default will break any Gtk+ 3.x application using a GtkStatusIcon.
bug #1390198 is a quite severe session crasher too.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.