From owner-freebsd-current@freebsd.org Wed Feb 3 12:49:27 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F928535EE0 for ; Wed, 3 Feb 2021 12:49:27 +0000 (UTC) (envelope-from 0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com) Received: from a48-99.smtp-out.amazonses.com (a48-99.smtp-out.amazonses.com [54.240.48.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DW1j23swYz4Y47 for ; Wed, 3 Feb 2021 12:49:26 +0000 (UTC) (envelope-from 0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1612356565; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=oSvris/Fgdq3iYUX/Xt7cfK3MaVH0k+Wf7+7apm3Xrg=; b=AcTBjyyhzs0Z85vCrJafAhwXFYzQeulA5vaANvTNzm7U/ZKBShE03UXtLUOaZn5Z rna8H9eHXXqhTugiatCbEuLCxsu0XwpPkUu95RfRdJzv7E0rXoB6qm9O7245geh9X5x /WodOioGKY6vfrcHXI0hvIjWx+pi1HC15mQzHbq4= Subject: Re: Problem with X Server when updating to 38bfc6dee33 To: David Wolfskill References: <0100017762dfa8ac-dedaf152-02d5-4816-ab97-6f89c0b65337-000000@email.amazonses.com> Cc: freebsd-current@freebsd.org From: Thomas Laus Message-ID: <0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@email.amazonses.com> Date: Wed, 3 Feb 2021 12:49:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2021.02.03-54.240.48.99 Feedback-ID: 1.us-east-1.9pbSdi8VQuDGy3n7CRAr3/hYnLCug78GrsPo0xSgBOs=:AmazonSES X-Rspamd-Queue-Id: 4DW1j23swYz4Y47 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=amazonses.com header.s=224i4yxa5dv7c2xz3womw6peuasteono header.b=AcTBjyyh; dmarc=none; spf=pass (mx1.freebsd.org: domain of 0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com designates 54.240.48.99 as permitted sender) smtp.mailfrom=0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com X-Spamd-Result: default: False [-0.70 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=224i4yxa5dv7c2xz3womw6peuasteono]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[acm.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[amazonses.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[54.240.48.99:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[lausts@acm.org,0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[54.240.48.99:from]; ASN(0.00)[asn:14618, ipnet:54.240.48.0/23, country:US]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,0100017767f0b892-bf075fd9-8d1d-4dc7-a28e-75db886a7e1e-000000@amazonses.com]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2021 12:49:27 -0000 On 2/2/21 8:16 AM, David Wolfskill wrote: > You might want to see if this ports/UPDATING entry: > > 20200320: > AFFECTS: users of x11/libxkbcommon > AUTHOR: zeising@FreeBSD.org > > The libxkbcommon library (x11/libxkbcommon), used to handle keyboards > in some applications, most notably kde and wayland, have been switched > to use evdev rules by default on FreeBSD 12 and later. Some keys, most > notably arrow keys, may not work in applications using libxkbcommon if > you are using xf86-input-keyboard rather than xf86-input-libinput. > If you have trouble with the keyboard keys, and if /var/log/Xorg.*.log > shows that the "kbd" or "keyboard" driver is being used, you need to > switch to legacy rules by setting the environment variable > XKB_DEFAULT_RULES to xorg. > This switch is made to match the default configuration on FreeBSD 12.1 and > later, the default configuration on FreeBSD 11.3 still uses the legacy > rules. > It did not apply. I am using xf86-input-libinput-0.30.0_1 on both of the problem computers. Everything worked until I performed the 'pkg bootstrap -f' after my last build world update. Until then I was able to start X with a working keyboard and mouse. When my packages were updated after the the ABI change, the mouse and keyboard stopped working. I always upgrade all of my packages after building world and was prompted after the change to 14.0-CURRENT from 13.0-CURRENT to do so. I ran the 'pkg upgrade' command and the prompt told me to run 'pkg bootstrap -f' because of the ABI change. It downloaded a new pkg program and then upgraded all of my packages because of the change in ABI. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF