From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rutger Helling Subject: Re: GNOME on Wayland current status Date: Thu, 4 Jan 2018 11:49:34 +0100 Message-ID: <20180104114934.6e607fba@mykolab.com> References: <7dbd6d56e6335050bedb1ca55c9a4828@mykolab.com> <87k1x11pxh.fsf@gnu.org> <20180102134758.703830e5@mykolab.com> <87y3lewd1s.fsf@netris.org> <20180104083858.vr3xk7xcjzedn7ga@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/r_5QeV5goadDc52t.fhxOtX"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44517) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eX35v-00062s-Oc for guix-devel@gnu.org; Thu, 04 Jan 2018 05:49:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eX35s-0005qx-Kk for guix-devel@gnu.org; Thu, 04 Jan 2018 05:49:55 -0500 Received: from mx.kolabnow.com ([95.128.36.42]:56030) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eX35s-0005nv-8x for guix-devel@gnu.org; Thu, 04 Jan 2018 05:49:52 -0500 In-Reply-To: <20180104083858.vr3xk7xcjzedn7ga@abyayala> 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: ng0 Cc: guix-devel@gnu.org --Sig_/r_5QeV5goadDc52t.fhxOtX Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi ng0, that might be a good idea. I was disturbed to learn that SLiM has seemingly been abandoned since 2013 (source: https://wiki.archlinux.org/index.php/SLiM), so lightdm might be a good light-weight alternative as the default display manager. Do you know if the lightdm process itself can run on Wayland (like GDM)? @Mark SDDM for the moment cannot run on Wayland yet, which is why it starts its own X server. I don't think I've had some of the problems you had with GNOME. Could you try logging in once via a display manager to GNOME (either X11 or Wayland is fine), then logging out, stopping the display manager and running the following command on a TTY: XDG_SESSION_TYPE=3Dwayland dbus-run-session gnome-session One of the problems I've run into myself is that X11 screen lockers like xlock don't seem to work. In GNOME GDM is supposed to be the screen locker I believe, but I don't think that works at the moment. I'll try and see if there's a simple Wayland-based screen locker we could use later. On Thu, 4 Jan 2018 08:38:58 +0000 ng0 wrote: > 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. =20 >=20 > 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 > standardized. >=20 > > 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 --Sig_/r_5QeV5goadDc52t.fhxOtX Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEAVThuRzJ2e93ZI3n86cn20T8yjYFAlpOBr4ACgkQ86cn20T8 yjb7xgf6A3pTy0YRG3KG4Ebge+ULYeS/qa7HPDUbeoVz6I2WhdGQwIJEB4uMZwNu Lc/Ap5A28KtEsBIV9r4XTvbzrw1AElKW6Xg7V12htG/lyHauUmhTZ4zcVktSpGSn I+fOSlRMIwS6cQ5g22ys2WLHHUj8XgAVTzPUeg8gGnAfZ2pY8pHxH9K+1MXlWVW6 jAaPhsmJLvIvYF/VjU5Fu2Ao3ecprVAz54EZDgKrIKXDR7nDsYq0GFdli9ex0Pnj bcL8u++7c6+ozFOqpnYUVDnawr+gUuCduNj4RevXvfQLdFoiXlWh+niEThAPHVxR cymht5YPcba8moM1FuG5Hz5zV6bdLQ== =r2Ql -----END PGP SIGNATURE----- --Sig_/r_5QeV5goadDc52t.fhxOtX--