From owner-freebsd-x11@freebsd.org Tue Jan 26 10:01:22 2021 Return-Path: Delivered-To: freebsd-x11@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 48ADA4E7F1E for ; Tue, 26 Jan 2021 10:01:22 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DQ2Ln63Ccz3KJZ for ; Tue, 26 Jan 2021 10:01:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by mailman.nyi.freebsd.org (Postfix) id CFA224E818A; Tue, 26 Jan 2021 10:01:21 +0000 (UTC) Delivered-To: x11@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 CF6B44E8189 for ; Tue, 26 Jan 2021 10:01:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQ2Ln4pb8z3JlT; Tue, 26 Jan 2021 10:01:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4DQ2Ld5xdyz6ddc; Tue, 26 Jan 2021 11:01:13 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id IjW73puXdIpL; Tue, 26 Jan 2021 11:01:11 +0100 (CET) Subject: Re: 'End' key stopped working (xfce) To: Jakob Alvermark , Alexey Dokuchaev Cc: Michael Schuster , x11@freebsd.org References: <25d26cd7-0082-675e-4655-dfe97c7b59ac@alvermark.net> <9c810b1b-f117-3f8f-7d23-3917ad53f6eb@madpilot.net> <022af763-720c-219c-3590-e7632a4c0e21@alvermark.net> <5cba4fbe-8e6d-8a66-4a1c-4f3c1ec59b32@alvermark.net> <20210121075453.GA4808@FreeBSD.org> <8a49d2b6-0e2e-76ac-3f8c-8a9edcc26482@alvermark.net> <277069f9-3697-cbac-a0ab-e5e786f0f6ac@madpilot.net> <3336616d-284d-50b9-5a6c-fad842e508f1@alvermark.net> From: Guido Falsi Message-ID: <3c4f405b-2bb9-105d-5ba8-6949112fcb31@madpilot.net> Date: Tue, 26 Jan 2021 11:01:10 +0100 In-Reply-To: <3336616d-284d-50b9-5a6c-fad842e508f1@alvermark.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DQ2Ln4pb8z3JlT X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2021 10:01:22 -0000 On 26/01/21 10:45, Jakob Alvermark wrote: > > On 1/21/21 9:25 AM, Guido Falsi wrote: >> On 21/01/21 09:10, Jakob Alvermark wrote: >>> On 1/21/21 8:54 AM, Alexey Dokuchaev wrote: >>>> On Thu, Jan 21, 2021 at 08:49:39AM +0100, Jakob Alvermark wrote: >>>>> ... >>>>> Something strange is going on here. >>>>> >>>>> I changed one shortcut, next time I restarted xfce my up-arrow key >>>>> doesn't work. >>>>> >>>>> I changed one shortcut without restarting xfce and the up-arrow works >>>>> again... >>>> You might find reading the discussion in the following bugzilla PR >>>> useful (esp. comment #54): https://bugs.freebsd.org/244290. >>>> >>>> ./danfe >>> >>> Thanks for the suggestion, applying the change suggested in #54 seems >>> to have fixed the issue. >>> >> >> What change exactly? If there is a change that reliably mitigates the >> issue it could be included in the ports tree, but I'm not sure I >> understand what to change exaclty. >> >> It looks like removing the "ungrab" code line causes other >> regressions, so I'm not sure is a good candidate. > > > The change that worked was adding back the ungrab line that was removed > in that commit. > Thanks for the feedback. If that change really works for most users it's a good candidate for inclusion in the ports tree. I'd also try to get it back upstream. I followed up to bug 244290 about this. But since I'm not experiencing the issue myself I can't test this. So I'm asking for consensus from users. -- Guido Falsi