Date: Sat, 16 Jan 2021 01:05:22 +0000 From: bugzilla-noreply@freebsd.org To: xfce@FreeBSD.org Subject: [Bug 244290] x11-wm/xfce4 does not see up arrow after reinstall Message-ID: <bug-244290-28711-SNiAmjoCCg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244290-28711@https.bugs.freebsd.org/bugzilla/> References: <bug-244290-28711@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244290 --- Comment #54 from Jethro Nederhof <jethro@jethron.id.au> --- Yeah, can confirm this was reintroduced to 4.16 upstream in https://gitlab.xfce.org/xfce/libxfce4ui/-/commit/85d8d390f9f2265613da429199= 2523937a7a2519 If you don't mind building the port instead, you can un-delete the line at https://gitlab.xfce.org/xfce/libxfce4ui/-/commit/85d8d390f9f2265613da429199= 2523937a7a2519#80f74afa9222af5979dad472e393792fb0194051_175_183 (in the port x11/libxfce4menu). This restores the patched 4.14 behaviour of "up" being broken until the fir= st keypress, which updates the keymap and everything works OK after that. But you'll also probably re-introduce the performance issue that patch tries to solve if you're using a .Xmodmap file and experiencing that issue. Restoring the default shortcuts will also fix it as mentioned, (this ungrabs everythi= ng and regrabs the defaults) but in my experience you have to do it every sess= ion. That same patch also seems to have possible regressions in https://gitlab.xfce.org/xfce/libxfce4ui/-/issues/33 so there'll hopefully b= e a fix soon that fixes both issues, or diagnosing that will find the root caus= e of this issue and we'll get it for free. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244290-28711-SNiAmjoCCg>