GNOME Bugzilla – Bug 757579
Tracker for Wayland-related issues
Last modified: 2021-07-05 13:46:57 UTC
This is a tracker bug for issues related to Wayland, but not necessarily issues in Wayland itself (but instead bugs in compositors, toolkits and apps). If we want to have Wayland as the default display technology soon, we need to have an overall picture of all that is not working properly with it. Here's a basic document for debugging Wayland issues: https://fedoraproject.org/wiki/How_to_debug_Wayland_problems If you find a bug related to Wayland (in any component), set "Blocks: WaylandRelated" in your bug report to make it block this tracker. See https://bugzilla.gnome.com/showdependencytree.cgi?id=WaylandRelated&hide_resolved=1 to see all such bug reports. Here's a similar tracker in Red Hat Bugzilla for those who report the issues there: https://bugzilla.redhat.com/show_bug.cgi?id=1277927
The link to show tracked bugs doesn't seem to work well for some reason, this one does: https://bugzilla.gnome.org/showdependencytree.cgi?id=757579&hide_resolved=1
Thanks for working on this! Is it useful to have a tracker bug? I can't imagine that we'll ever fix all Wayland related issues in GNOME - in the future any bug related to input, output, or application/desktop communication will be "Wayland related". Most Wayland specific bugs for GNOME will either be filed against mutter/wayland or gtk+/Backend: Wayland - searching those components is likely the most efficient way to find Wayland related issues. I could see that it might be useful to have a tracker bug for specific Wayland regressions and application crashes hit when testing 3.18 - perhaps this bug could be repurposed for that? I think tracker bugs are useful for "sprints" - fixing a bunch of bugs and moving on - but not useful long-term.
Sorry, I haven't really mentioned the intended scope. I imagine this would serve its purpose until Wayland was the default display server in Fedora and GNOME (and hopefully elsewhere as well). That could mean 6-12 months? After that, I believe there will be no reason in keeping this up. Definitely not forever :) Until that happens, I believe there's considerable benefit in having such a tracker, because it's a new area for many people, we can expect the bugs to be distributed across many components, and people will have very little experience with it and will be likely to report bugs against apps when not sure whether it's an app or toolkit or compositor problem. A tracker helps reporters to see whether a particular bug was already reported, because I can search for e.g. "nautilus" in bugs blocking this tracker, regardless whether the issue is reported in nautilus, gtk+, mutter or some other component (as long as it is tracked here). But it is also reasonable to use this only for bugs outside of mutter and gtk+ components (but still related to wayland), if you think it's a better idea. I guess it's a question of how many such bugs overall we expect to see. I expect this tracker to be used mostly by a handful of people involved in regular testing of Fedora and GNOME, so I don't expect an avalanche of reports coming in every day (I can be wrong). Originally I wanted to create the tracker against some kind of a neutral component (something like "distribution" in RH Bugzilla), not mutter, but I couldn't find any. I certainly don't want to spam mutter developers with bugzilla updates of sometimes unrelated issues, so please tell me if you want to adjust this somehow.
Hey Kamil, I just discovered that there is an existing tracker, bug #695806 (with a pretty cool URL: https://bugzilla.gnome.org/show_bug.cgi?id=wayland !) Should we merge this into it (that'll be fun...)?
(In reply to Kamil Páral from comment #0) > Here's a similar tracker in Red Hat Bugzilla for those who report the issues > there: Not to be left out, here's the equivalent in Debian: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintainers@lists.alioth.debian.org;tag=wayland (In reply to Kamil Páral from comment #3) > I imagine this would > serve its purpose until Wayland was the default display server in Fedora and > GNOME (and hopefully elsewhere as well). I agree that while Wayland is the weird new thing for early adopters, it makes sense to have a tracker for Wayland-specific bugs - if nothing else, it helps developers and distributors to gauge whether it's ready yet. When Wayland-by-default is production-ready, a specific tracker loses its usefulness. FYI, the Debian GNOME maintainers are currently in the process of integrating GNOME 3.20 into the "unstable" suite. We plan to ship 3.22 in the next stable Debian release (Debian 9), so we're considering having Wayland by default with 3.20 (potentially with fixes backported from 3.21 as needed), to get enough implementation experience that we can catch bugs early and assess whether Wayland-by-default is something we can support in Debian 9.
Bug https://bugzilla.gnome.org/show_bug.cgi?id=768531 should be on this list too, but I am not allowed to add it.
Please add bug https://bugzilla.gnome.org/show_bug.cgi?id=760745 too, since it is happening on wayland only.
Please add bug 766241 too.
Please add [https://bugzilla.gnome.org/show_bug.cgi?id=721224] too.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help.