On Wed, 19 Jun 2019 22:16:58 +0200 Ansgar Burchardt <ans...@43-1.org> wrote: > Jonathan Dowland writes: > > So far as I am aware there is still radio silence from active GNOME > > packaging team members regarding this issue. No comment yet on the > > patch I adapted, positive or negative; this bug (#927667) remains > > at an RC severity. > > > > I've not yet read all the thread that Samuel linked to[1] but it looks > > like it leans in favour of preserving the current default (xorg). > > > > I'm copying -release team to see if they have any (new) opinions on > > the matter. Otherwise I guess it's up to someone to prepare an NMU > > upload, which I will *try* to look at in the next few days, but can't > > make any guarantees. > > I'm just a GNOME user, but from gdm3's changelog the default was > switched to Wayland in July 2017 (or August 2017 for unstable). I > myself only noticed the switch after reading it happened somewhere on > the internet shortly after it happened.
gdm was switched over to use Wayland before the main session was and in Debian we kept that default for gdm (even for stretch, and still true for buster). gdm runs in a much more limited environment though, so some of the limitations (like screen sharing) do not really affect the gdm session. I suppose the a11y issues that were pointed out for Wayland do affect the gdm wayland session though? What kind of display technology gdm is using is a separate discussion though from what kind of desktop session is started as default: GNOME on Xorg or GNOME on Wayland. When you talk about "gdm3's default", what exactly do you mean: the display technology gdm is using or the type of GNOME session that is started as default? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
