From nobody Tue Dec 3 10:07:39 2024 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Y2btx2NnBz5gCjS for ; Tue, 03 Dec 2024 10:07:53 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y2btw2F7Gz4f0y for ; Tue, 3 Dec 2024 10:07:52 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=MBfHF2ZX; spf=pass (mx1.freebsd.org: domain of vadimnuclight@gmail.com designates 2a00:1450:4864:20::12f as permitted sender) smtp.mailfrom=vadimnuclight@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-53df67d6659so8246291e87.3 for ; Tue, 03 Dec 2024 02:07:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733220470; x=1733825270; darn=freebsd.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=gx+ffmbA3XpzJxk93NincnB0gFzXHMaxWrXW5jjabOk=; b=MBfHF2ZX1+ocwKimPPL230p1Op/qNkwNUgNO8n/MwyxXFkkr72QeNSobWcx0Sst3NR 1EQylgup2O6HVge790AgU8yPFuLPnhmCzc7aiSK3e+zOusH55x2v7T4hxVTyFS60rMsq i7MbL2h/5qs9ciZomcGXnkAtFfr9+eUwY2CJpSDIcBQ/AcV0EayvVM+btBUh4WAGRmOB sGEv+xVQUYdYCKZu5OJ0r7dsuCf/MZUL48CrxVk7mOsQCiwkxysBbrfSvwp4KUayp21E ByIHg9vdZJLn08LL55WxsMNDqETXqmOgKz9VnqknkJ1wV+3+ymjePv/tMN6TvTOw9G8y Qp8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733220470; x=1733825270; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gx+ffmbA3XpzJxk93NincnB0gFzXHMaxWrXW5jjabOk=; b=QSRkk98/vWcxcj7fFKWnVm0lLaFq8VBYdGWTq/US0AUccKBzftgXjvL+0EwTu7TWyp jwch0OGFcctbzsuQfgsBEax0j//ZG+2xymrMoauK0AzkhDHOErPyIGw+lCMBkc8qX2vx qiTKjt1hFQmiipPRlkvtVfznUx5qAZNYvahJsoggyHd7Bea6F5mITc0qp8i/5HRkeX7l lJG03900ZWJ50xQXuPl0LXJeLJ1dmibQjrJJdFNNJApBXYG+DEIVYtgaEWIeUU6Ke2uh e9Z6JhBMvqlfE8wK60A3rjyvos1zXuG2zhIxaYwz8awDtEBQ4CKlSKbQuxD3noBk+vvj IJCg== X-Gm-Message-State: AOJu0YzsJ+OYa24Ykwfi3P0x6UDXreDx/4oruzjn15usCusC0dwBWitZ vBz3RSWbXMcPveC/qmzIa7nciJcwThubFAqrDAOfPSc6Ilw10zgg X-Gm-Gg: ASbGncux7vqwOAuoxJ1JiHk6rp7jz+jm5t1e6XiGEgQyRXPKzd78zQmtjJVyoF2i7MP zqNSY7ZVTa/+zug9hio6pQs8JyL3KfNHoF14xVvBHK8v4YtCesGGYeCz9CeD+sG7KLfI8nHMfs0 guOLkAuS7RQIiR4+DVn2L4t5vPlEXzd91ft+aMO0U8H2r23ntyEktAwEL+gs7K8gjA/3d0uF0kM ihD3+XV+z+0ZwbMbuo+PEAcdODa1m1HO19sg64dqgWuijP3hO9H1g== X-Google-Smtp-Source: AGHT+IHVxykbYpb8GpZQxJypeEXPACgZ0ySjy1Awacv3BANd/0rxg9WKylMMBaMqpLTqpTAo4hNZ1A== X-Received: by 2002:a05:6512:3ca4:b0:53d:f50f:c3d4 with SMTP id 2adb3069b0e04-53e129ef555mr1636605e87.9.1733220470064; Tue, 03 Dec 2024 02:07:50 -0800 (PST) Received: from nuclight.lan ([37.204.254.214]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-53df64432efsm1771450e87.68.2024.12.03.02.07.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Dec 2024 02:07:49 -0800 (PST) Date: Tue, 3 Dec 2024 13:07:39 +0300 From: Vadim Goncharov To: Dominique Michel Cc: freebsd-hackers@freebsd.org Subject: Re: First time with freebsd and weird keyboard issue Message-ID: <20241203130739.2eacb909@nuclight.lan> In-Reply-To: <20241203100237.5623fcf0@tuxette> References: <20241126113912.60714f63@tuxette> <1732633036752.1687134307.2902732100@FreeBSD.org> <20241203100237.5623fcf0@tuxette> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd12.4) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.79 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.79)[-0.792]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TAGGED_RCPT(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::12f:from] X-Rspamd-Queue-Id: 4Y2btw2F7Gz4f0y X-Spamd-Bar: --- On Tue, 3 Dec 2024 10:20:26 +0100 Dominique Michel wrote: > Le Tue, 26 Nov 2024 14:57:32 +0000, > Lars Engels a =C3=A9crit : >=20 > > Dominique Michel schrieb am Dienstag, 26. November 2024 11:39:12 > > (+01:00): > > =20 > > > Hi, > > >=20 > > > I am the main fvwm-crystal maintainer and I am working on adding > > > freebsd support to it. To do that, I installed the last freebsd > > > version and I saw a double issue with the keyboard. > > >=20 > > > First: > > > In /etc/rc.conf > > > keymap=3D"ch-fr.acc.kbd" This is for console keyboard, it has nothing to do with X11. > > > In order to understand how to reproduce these issues, I do 2 test > > > user accounts with different shells, sh and bash. With both of > > > them, after login, the keyboard is working fine with the ttys. > > >=20 > > > Then I followed chapter 25 of the handbook and put in > > > ~/.login_conf: me:\ > > > :charset=3DUTF-8:\ > > > :lang=3Dfr_ch.UTF-8: > > >=20 > > > and ran cap_mkdb ~/.login_conf =20 That's essentially shell-independet setting of locale environment variables. > > You only need to run cap_mkdb /etc/login.conf. Your ~/.login_conf is > > read automatically upon login. By running cap_mkdb with your own > > login config you probably messed up your environment. =20 >=20 > I followed the handbook: 25.2.1.1. Login Classes Method > https://docs.freebsd.org/en/books/handbook/l10n/#login-class >=20 > "i Note:=09 >=20 > For an end user, the cap_mkdb command will need to be run on their > ~/.login_conf for any changes to take effect." >=20 > >=20 > > Another run cap_mkdb /etc/login.conf should fix it. > > =20 >=20 > Anyway, I ran that command 1 more time as root and commented out the > 'me: ....' stuff in ~/.login_conf. It works fine at the tty, but after > startx, that change nothing. Yep, because $LANG alone is not enough for full X11 l10n. > I found a workaround, it is to install lightdm and start fvwn-crystal > with it. And finally, I found a fix. It is to restore the 'me:...' > stuff and add in .xinitrc: >=20 > setxkbmap -layout 'ch(fr)' -model pc105 -option > terminate:ctrl_alt_bksp,keypad:pointerkeys >=20 > Note the single quotes around the layout and the (). Without language variables you'll only get keyboard with this and not messages, time etc. stuff, e.g. `ls -l` month names in xterm --=20 WBR, @nuclight