From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: GNOME on Wayland current status Date: Thu, 4 Jan 2018 08:38:58 +0000 Message-ID: <20180104083858.vr3xk7xcjzedn7ga@abyayala> References: <7dbd6d56e6335050bedb1ca55c9a4828@mykolab.com> <87k1x11pxh.fsf@gnu.org> <20180102134758.703830e5@mykolab.com> <87y3lewd1s.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ummag46b7wguxflz" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41257) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eX13f-0003d2-6b for guix-devel@gnu.org; Thu, 04 Jan 2018 03:39:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eX13c-0002xu-2g for guix-devel@gnu.org; Thu, 04 Jan 2018 03:39:27 -0500 Received: from aibo.runbox.com ([91.220.196.211]:43216) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eX13b-0002ww-P0 for guix-devel@gnu.org; Thu, 04 Jan 2018 03:39:23 -0500 Content-Disposition: inline In-Reply-To: <87y3lewd1s.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org, Rutger Helling --ummag46b7wguxflz Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mark H Weaver transcribed 2.4K bytes: > Hi Rutger, >=20 > Rutger Helling writes: >=20 > > I've sent in a patch (#29943) that adds a small paragraph to the > > documentation about the current situation. > > > > I believe there was a plan to replace SLiM with GDM for the default > > login manager. Getting GDM to work properly should probably be the > > first step since it has great Wayland support. From what I know GDM can > > default to Wayland and falls back automatically to X11 if for some > > reason Wayland doesn't work. > > > > Alternatively we could switch to SDDM as the default for now, until GDM > > is ready. What about lightdm? Does it not offer wayland support? We have no service for it yet, but as far as I understand the greeters (like 'lightdm-gtk-greeter') writing your own theme is relatively standardi= zed. > I recently switched my x86_64 GuixSD laptop to use SDDM, so I could try > out GNOME on Wayland. It mostly works, but there are still a few > problems: >=20 > * Even after logging in, SDDM is still visibly running within > xorg-server on VT 7, while Wayland is running on VT 8. If you switch > back to VT 7, you can see the login screen still there, with the clock > showing the time that you logged in instead of the current time. I'm > not sure if there are security implications to this, but it's > certainly a waste of system resources. >=20 > * SDDM is based on Qt, so it substantially increases the closure size of > the system, as well as memory usage since SDDM and Xorg-server > continues to run in another VT during your entire session. >=20 > * The "Sound" panel of the GNOME settings is non-functional. Whenever I > try to change anything at all in that panel, it crashes. >=20 > * Startup notification for several GNOME programs is broken, e.g. GNOME > Terminal, Files (Nautilus), Videos (Totem), and possibly other. When > I launch any of those programs, although the program immediately > starts up, GNOME Shell doesn't seem to realize this, and for quite > some time the spinner continues to indicate that the application is > starting up, and it doesn't show up in the Alt-Tab application > switcher. If you switch to another application, you cannot switch > back to it via Alt-Tab. >=20 > * As far as I know, we haven't yet themed SDDM to include our beautiful > GuixSD login screen artwork. It would be a shame to lose that by > default. >=20 > On the other hand, I'm pleased to report that under Wayland, tearing no > longer occurs during video playback, scrolling, etc. >=20 > Anyway, it's very exciting to see progress on this, but I'm reluctant to > bring Qt into our default system closure, and furthermore I'd be > inclined to wait until more of the aforementioned problems are > addressed. >=20 > What do you think? >=20 > Mark >=20 >=20 --=20 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys WWW: https://n0.is/a/ :: https://ea.n0.is --ummag46b7wguxflz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlpN6CIACgkQ4i+bv+40 hYgZQA//aO05wsYYkUuXIJEmQ9d36sxSIDt6l5h6zdk81D3lKFkIhYmdnu8dP6tT GwEyJcFcmB2IXW8eZ5vDgk2b5km+Gd2M2iqG+W37VFASMVq6vRblYgmaR3424cOf kotrsWrSm/dGZdWlYKXR3hAlVVgtBw1wV5pem6gdHyaD/gYUn/qM+16Xvn/GnPK2 qcLp7UmH2OsmnqQPno3luvl++QOBncFJfc+3uC1s5Cq/KD6owZ028zcPXIhqu+2R amljajyhes0RYZN5LbM9rXvNJZSJ//mxLGFuxyaqc2QJxq2OxGP71fr/PCNkhFVX WgJke78N+DlZUqsQSVGZ4YvON15YHbwzfggKGtwFAgU1S9T7lhEjxwhc/hAZ0r1Q nYBHPVBb2qMILq1ORtQyyETd4nigfdjEm+BPNU8KAwAvt1U6hMuot0m4u6Y4sV6m 8kRnKF171V3yb5nwlf56p149rdFFnxgjn257XJQDto/YuQV3qqQ0TfAysPdIJiBE gNdLXS9O99f11hHIGmSDmdKXSOt+wHoSREt72pACo14OqwCKugYxeZyaELDOzumM 93M/5rL4JOS7x0gJUphIkQewvlqaNp9Ruq7dp1PAY0JS4Ox+3inpCsxpGzaIw4eS T2916rzN+FSZdgY5r7aaIcUlI+wi9wrUwAEh6m968eK0jIQssxg= =dt4J -----END PGP SIGNATURE----- --ummag46b7wguxflz--