Christopher Gregory via blfs-support wrote:
Sent: Monday, August 26, 2019 at 8:21 PM
From: "Pierre Labastie via blfs-support"
<blfs-support@lists.linuxfromscratch.org>
To: blfs-support@lists.linuxfromscratch.org
Cc: "Pierre Labastie" <pierre.labas...@neuf.fr>
Subject: Re: [blfs-support] gdm: how to use a non us keyboard?
On 26/08/2019 08:48, Christopher Gregory via blfs-support wrote:
Sent: Monday, August 26, 2019 at 5:38 PM
From: "Pierre Labastie via blfs-support"
<blfs-support@lists.linuxfromscratch.org>
To: blfs-support@lists.linuxfromscratch.org
Cc: "Pierre Labastie" <pierre.labas...@neuf.fr>
Subject: Re: [blfs-support] gdm: how to use a non us keyboard?
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
Hello Pierre,
Sorry but this is going to probably come out of context due to mail servers
slow delivery.
The same problem that you are having with the keyboard and gdm, has been
addressed in freebsd, who do not run systemd.
They found that the issue is with gnome-shell which forces the use of systemd.
They created a patch back in January of this year, which may well be able to be
modified for lfs/blfs purposes:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235009
Thanks Christopher, but the last post of the thread does not make me very
optimistic... One patch does not apply (and seems to be using the freebsd
build system), while the other does do anything...
Giving up for now. I may try all this in a systemd build, if I have time, but
I want to try other things re extra-cmake-modules before the release...
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Hello Pierre,compiling
Whilst it may not seem important, due to the fact that you use a UTF8 locale, I
still think it may well be worth a shot at compiling it into elogind, that way
at least the default is correctly set as a primary. This eliminates the hard
use of localectl, which is not being used on the cut-down version that is being
used.
Ultimately it is up to you to decide, all I can do is to give some suggestions.
If indeed it is as freebsd have found, to be an issue with gnome-shell,
perhaps DJ could make a patch that works. It does at least point to something
else to look at.
Just to paraphrase my suggestion is:
1) Try and see what, if anything changes when you select to run gnome on xorg.
2) Hard compile the locale into elogind so that it is the primary locale.
All of this has been brought about by the corporation redhat pushing systemd on
everyone, so of course now even though it has not yet been made a compile time
hard option to use systemd, it is a run time one.
I wish that they had left well enough alone. The fact that I like gnome, is
the only reason I myself went to systemd in the first place. I would never use
systemd in a server environment.
I had also missed the part in that freebsd post about it not working.
It will take me too long, I feel to do an lfs/blfs build of sysv using elogind
to be of any assistance. It will take about a week to install everything up to
and including gnome on it.
As I only have one language installed, not even the manage languages option
that Ubuntu have shows up for me.
I've tried to set:
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
in /etc/gdm/custom.conf, so that it forces Xorg to be used (according to
the docs, but I've always found that gnome docs are either misleading or
too incomplete to be of any use). No change. I've started a gnome on
xorg session (from the supposedly xorg gdm). No change.
I'm in the process of trying to recompile gnome-shell with
"-Dsystemd=false" (at least it prevents installing unit files in
/usr/lib/systemd/user), and evolution-data-server with
-DWITHSYSTEMDUSERUNITDIR=no (there is a typo in the book, where it says
-DWITHSYSTEMDSYSTEMDUNITDIR=). I do not expect much.
I am also compiling lfs-systemd in a VM (good test of qemu), and hope to
reach gnome tonight, just to make sure the same issues do not appear
with systemd...
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
