Discussion:
Bug#931277: release-notes: document Wayland as default display server for GNOME in what's new
(too old to reply)
Paul Gevers
2019-06-30 10:40:01 UTC
Permalink
Package: release-notes
X-Debbugs-CC: debian-***@lists.debian.org
Control: tags -1 patch pending

Hi all,

I thinks we should document the switch of GNOME to Wayland as the
default display server in the What's New section. Proposal attached.
I've added d-***@l.d.o in X-D-CC, please keep them in the loop, because
I think it is worth mentioning a recommendation to not use Wayland for
people needing a11y technology. Did I phrase it right in the proposal?

Does this subject (a11y on Wayland) warrant a note in "Issues to be
aware of for buster" chapter?

Paul
Debian Bug Tracking System
2019-06-30 10:40:02 UTC
Permalink
Post by Paul Gevers
tags -1 patch pending
Bug #931277 [release-notes] release-notes: document Wayland as default display server for GNOME in what's new
Added tag(s) patch and pending.
--
931277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931277
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Justin B Rye
2019-06-30 12:00:01 UTC
Permalink
Post by Paul Gevers
I thinks we should document the switch of GNOME to Wayland as the
default display server in the What's New section. Proposal attached.
I think it is worth mentioning a recommendation to not use Wayland for
people needing a11y technology. Did I phrase it right in the proposal?
Does this subject (a11y on Wayland) warrant a note in "Issues to be
aware of for buster" chapter?
Probably the "apps-in-gnome-on-wayland" issues section should link
back to this whats-new section.
Post by Paul Gevers
+<section id="wayland-by-default-on-gnome">
+ <!-- stretch to buster -->
+ <title>GNOME defaults to Wayland</title>
+ <para>
+ Following the upstream code, GNOME in buster now uses the Wayland display
+ server by default instead of the Xorg display server. The Wayland display
+ server is more recent than Xorg, and therefor is designed to prevent some
+ security issues present in Xorg.
+ </para>
A bit repetitive, and we should probably say "modern", not "recent"
(for a start because that hints at the downside: its assumptions are
*too* modern for my video hardware).

Following upstream, GNOME in buster defaults to using the Wayland
display instead of Xorg. Wayland is a simpler and more modern
design, which has advantages for security.
Post by Paul Gevers
+ <para>
+ The Xorg display server is still installed by default and the default
+ display manager still allows you to choose it as the display server for the
+ next session, which may be needed if you want to use some applications (see
+ <xref linkend="apps-in-gnome-on-wayland"/>).
+ </para>
+ <para>
+ People requiring accessibility features of the display server, e.g. global
+ keyboard shortcuts, are recommended to use Xorg instead of Wayland.
+ </para>
+</section>
+
</section>
</chapter>
This all looks good to me, but I'm not sure how much of the detail
should go here and how much under "issues".
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Justin B Rye
2019-06-30 12:00:01 UTC
Permalink
Post by Justin B Rye
A bit repetitive, and we should probably say "modern", not "recent"
(for a start because that hints at the downside: its assumptions are
*too* modern for my video hardware).
Following upstream, GNOME in buster defaults to using the Wayland
display instead of Xorg. Wayland is a simpler and more modern
^server
Post by Justin B Rye
design, which has advantages for security.
Oops, that's *too* terse.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Paul Gevers
2019-06-30 13:00:01 UTC
Permalink
Hi Justin,
Post by Justin B Rye
Post by Justin B Rye
A bit repetitive, and we should probably say "modern", not "recent"
(for a start because that hints at the downside: its assumptions are
*too* modern for my video hardware).
Following upstream, GNOME in buster defaults to using the Wayland
display instead of Xorg. Wayland is a simpler and more modern
^server
Post by Justin B Rye
design, which has advantages for security.
Oops, that's *too* terse.
I think it should also be "Wayland *has* a ... design", right?

Paul
Justin B Rye
2019-06-30 13:40:02 UTC
Permalink
Post by Paul Gevers
Post by Justin B Rye
Post by Justin B Rye
A bit repetitive, and we should probably say "modern", not "recent"
(for a start because that hints at the downside: its assumptions are
*too* modern for my video hardware).
Following upstream, GNOME in buster defaults to using the Wayland
display instead of Xorg. Wayland is a simpler and more modern
^server
Post by Justin B Rye
design, which has advantages for security.
Oops, that's *too* terse.
I think it should also be "Wayland *has* a ... design", right?
They're both possible, but yes, that sounds better.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Paul Gevers
2019-06-30 12:50:01 UTC
Permalink
Hi Justin,
Post by Justin B Rye
Post by Paul Gevers
Does this subject (a11y on Wayland) warrant a note in "Issues to be
aware of for buster" chapter?
Probably the "apps-in-gnome-on-wayland" issues section should link
back to this whats-new section.
That's a good solution. I'll do that, see attachment.

Paul
Debian Bug Tracking System
2019-07-01 20:00:01 UTC
Permalink
Your message dated Mon, 1 Jul 2019 21:55:14 +0200
with message-id <ea34a2dc-53a5-a3b0-30b4-***@debian.org>
and subject line Re: Bug#931277: release-notes: document Wayland as default display server for GNOME in what's new
has caused the Debian Bug report #931277,
regarding release-notes: document Wayland as default display server for GNOME in what's new
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
931277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931277
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...