Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Jan 2021 14:33:40 +0100
From:      Jakob Alvermark <jakob@alvermark.net>
To:        Michael Gmelin <freebsd@grem.de>
Cc:        Guido Falsi <mad@madpilot.net>, Alexey Dokuchaev <danfe@freebsd.org>, x11@freebsd.org
Subject:   Re: 'End' key stopped working (xfce)
Message-ID:  <a5c1e9d9-baeb-d472-4598-bf585fbcbddb@alvermark.net>
In-Reply-To: <7210540F-BC2D-4EB8-BF56-C754450938C1@grem.de>
References:  <43713fc4-ea9b-1e77-0bb7-5b3f20ff3900@alvermark.net> <7210540F-BC2D-4EB8-BF56-C754450938C1@grem.de>

next in thread | previous in thread | raw e-mail | index | archive | help

On 1/26/21 1:58 PM, Michael Gmelin wrote:
>
>> On 26. Jan 2021, at 13:55, Jakob Alvermark <jakob@alvermark.net> wrote:
>>
>> On 1/26/21 11:01 AM, Guido Falsi wrote:
>>>> 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.
>>>
>> By chance I discovered that it seems it only happens when you have UDEV option on xorg-server.
>>
>> (Which I do. Tracking -current all pkgs was upgraded when -current was bumped to 14, and the binary package of xorg-server does not have udev enabled)
>>
> Any chance that your keymap config is simply wrong/doesn’t match libinput? (You can check that by using setxkbmap to set the correct keymap explicitly). Maybe you could share your X11 config files/your .xinitrc.


It was working fine before the upgrade of libxfce4menu. It is working 
fine now after I have patched in the removed line discussed in the above PR.


$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     se

I have no special X11 config files, except for some settings for my 
touchpad.

My .xinitrc just contains a single line: 'xfce4-session'


I had a look a x11-servers/xorg-server because I felt it should have 
UDEV enabled by default, and found why it is not:

In the Makefile there is this:

OPTIONS_DEFAULT_FreeBSD_11=     DEVD
OPTIONS_DEFAULT_FreeBSD_12=     UDEV
OPTIONS_DEFAULT_FreeBSD_13=     UDEV
OPTIONS_DEFAULT+=       ${OPTIONS_DEFAULT_${OPSYS}_${OSREL:R}}


There is no OPTIONS_DEFAULT_FreeBSD_14=     UDEV


Jakob




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5c1e9d9-baeb-d472-4598-bf585fbcbddb>