Date: Mon, 15 Jun 2020 11:03:37 +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-20ejNU6HFg@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 #44 from Jethro Nederhof <jethro@jethron.id.au> --- (In reply to Samy Mahmoudi from comment #43) Hey Samy, Yes, thanks for clarifying it's just the first keypress, you had me worried there! I can replicate this, and as far as I understand the bug, being brok= en on the first keypress is expected behaviour because the initial keymap is s= till incorrect, but first keypress triggers the update to the correct keymap. The patch from this PR only updates how XFCE handles the change of state from insane keymap to sane and makes it work appropriately instead of continuing with the insane state after the update. I suspect the issue not appearing with display managers is because the first keypress happens there and triggers the keymap update before XFCE loads, wh= ich makes it work correctly as in the initial workaround with setxkbmap (skippi= ng this with autologin avoids this). So I think there's a different issue with xorg initially detecting the wrong keymap until first keypress, but it's unrelated to this issue and XFCE and probably should be a different PR. Compiz may just not handle the keymap updating? Not sure. Hope this helps! --=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-20ejNU6HFg>