Date: Tue, 26 Jan 2021 13:58:15 +0100 From: Michael Gmelin <freebsd@grem.de> To: Jakob Alvermark <jakob@alvermark.net> Cc: Guido Falsi <mad@madpilot.net>, Alexey Dokuchaev <danfe@freebsd.org>, x11@freebsd.org Subject: Re: 'End' key stopped working (xfce) Message-ID: <7210540F-BC2D-4EB8-BF56-C754450938C1@grem.de> In-Reply-To: <43713fc4-ea9b-1e77-0bb7-5b3f20ff3900@alvermark.net> References: <43713fc4-ea9b-1e77-0bb7-5b3f20ff3900@alvermark.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 26. Jan 2021, at 13:55, Jakob Alvermark <jakob@alvermark.net> wrote: >=20 > =EF=BB=BFOn 1/26/21 11:01 AM, Guido Falsi wrote: >>> On 26/01/21 10:45, Jakob Alvermark wrote: >>>=20 >>> 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. >>>>>>>=20 >>>>>>> I changed one shortcut, next time I restarted xfce my up-arrow key >>>>>>> doesn't work. >>>>>>>=20 >>>>>>> I changed one shortcut without restarting xfce and the up-arrow work= s >>>>>>> again... >>>>>> You might find reading the discussion in the following bugzilla PR >>>>>> useful (esp. comment #54): https://bugs.freebsd.org/244290. >>>>>>=20 >>>>>> ./danfe >>>>>=20 >>>>> Thanks for the suggestion, applying the change suggested in #54 seems t= o have fixed the issue. >>>>>=20 >>>>=20 >>>> What change exactly? If there is a change that reliably mitigates the i= ssue it could be included in the ports tree, but I'm not sure I understand w= hat to change exaclty. >>>>=20 >>>> It looks like removing the "ungrab" code line causes other regressions,= so I'm not sure is a good candidate. >>>=20 >>>=20 >>> The change that worked was adding back the ungrab line that was removed i= n that commit. >>>=20 >>=20 >> Thanks for the feedback. >>=20 >> If that change really works for most users it's a good candidate for incl= usion in the ports tree. I'd also try to get it back upstream. >>=20 >> I followed up to bug 244290 about this. >>=20 >> But since I'm not experiencing the issue myself I can't test this. So I'm= asking for consensus from users. >>=20 >=20 > By chance I discovered that it seems it only happens when you have UDEV op= tion on xorg-server. >=20 > (Which I do. Tracking -current all pkgs was upgraded when -current was bum= ped to 14, and the binary package of xorg-server does not have udev enabled)= >=20 Any chance that your keymap config is simply wrong/doesn=E2=80=99t match lib= input? (You can check that by using setxkbmap to set the correct keymap expl= icitly). Maybe you could share your X11 config files/your .xinitrc. -m >=20 > Jakob >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7210540F-BC2D-4EB8-BF56-C754450938C1>