On 25/08/2019 21:50, Pierre Labastie via blfs-support wrote: > On 25/08/2019 20:09, DJ Lucas via blfs-support wrote: >> >> >> On 8/23/2019 7:56 PM, Ken Moffat via blfs-support wrote: >>> On Fri, Aug 23, 2019 at 09:39:41PM +0200, Pierre Labastie via blfs-support >>> wrote: >>>> Will try using obconf in lxde. >>>> >>>> Pierre >>> Hi Pierre, >>> >>> not sure if https://issues.guix.info/issue/35118 might help for gdm. >>> >>> Some of the details look to be very specific to guix, but in patch 2 >>> localed is extracted from systemd and an xkeyboard patch is added. >>> >>> But all the wiring-up seems to be specific to how guix do things. >> Well, that seems like an interesting approach, and was fairly easy to do >> (took >> me about 20m...less time than it took for me to write this email in fact), >> but >> the Guix solution just uses "GUIX_XKB_*" environment variables. I hacked up a >> patch to elogind to mimic what Guix did if you want to fiddle with it and >> see. >> It does introduce a hard dependency on xkb-common. I renamed the workaround >> environment variables without the GUIX_ prefix. I haven't done any testing >> other than verifying that it builds and installs correctly (into DESTDIR, so >> at least no linking issues with elogind). The additional source files in the >> locale directory were taken directly from systemd-241. The variables that >> need >> to make their way into GDM's environment are >> XKB_{LAYOUT,MODEL,VARIANT,OPTIONS} (without configured /etc/vconsole.conf >> anyway), so it's a lot of systemd cruft left for just a simple workaround, >> but >> if it works, I could put a bit more time into it. Despite comment #6 in the >> above thread, it really wouldn't be _that_ difficult to decouple from >> elogind, >> but elogind would require a couple of small changes already in the patch >> below >> (or the handful of reintroduced functions added directly to the targets or a >> tiny libelocaled, but I'd much rather get these back into elogind and just >> depend on it). >> >> http://www.linuxfromscratch.org/~dj/elogind-241.3-add_localed-1.patch >> >> --DJ >> > > First, no joy trying to tweak greeter-dconf-defaults. This could have been > expected, since the source seems to rely on org.freedesktop.locale1 > > Will try the patch, to confirm that problems come from the lack of localed, > but I fear that we may encounter another problem: GNOME sets the local time to > UTC, and while I can open the time-date configuration, I cannot save the > settings, and it falls back to UTC on a minute change. I suspect the lack of > datetimed... > > So at the end, we'll be building a big part of systemd (except PID 1...), just > for the sake of GNOME... Is it worth it? > > Note that Gentoo pretends that GNOME 3.30 and 3.32 is usable with elogind + > openrc. But the ebuild file for gdm (3.30) does not seem to do more than what > we do... Maybe there is something in openrc. >
So I've rebuilt elogind with the patch provided by DJ, and now I have a "login" button in the region and language screen of gnome-control-center! Progress! Except the button does nothing /-: And no difference for gdm. I still have to try gnome on xorg. But I begin to be fed up of this. For now, I propose to add to the gdm page that it is impossible to have a non us keyboard, but it is possible to bring up the screen keyboard, and enter the password by clicking on keys. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
