Date: Wed, 10 Jun 2020 13:34:44 +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-KV2fHkfuQ3@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 #36 from Samy Mahmoudi <samy.mahmoudi@gmail.com> --- By trial and error I have noticed some things that might be interesting. Context: libxfce4menu-4.14.1_1 12.1-RELEASE-p5 amd64 FACT 1: Starting xfce4 from vt, the up arrow key is not correctly mapped (pressing the key makes the xfce4-terminal cursor blinks but does not show previous shell commands...) and my compiz desktop switcher (CTRL+ALT+AN_ARROW_KEY) does not trigger. FACT 2: When using SLiM autologin or lightdm autologin: same faulty behavio= r. FACT 3: - When manually setting my SLiM session to "Xfce Session" (by pressing F1 at the SLiM login screen): not problem at all after the start. - When using SLiM "default" session (which I have mapped to startxfce4 in my .xinitrc) by NOT pressing F1 at the SLiM login screen: no problem at all af= ter the start. - When using the lightdm login screen: no problem at all after the start. FACT 4: Adding a setxkbmap command at the beginning of my .xinitrc works ar= ound the SLiM autologin but not the lightdm autologin. My understanding is that the underlying problem is not resolved, despite revision 531554, so I am quite comforted by comment 35. That's why I wrote comment 34, in the hope of testing your first reworked patch. FACTS 3 and 4 may just reveal variants of the same workaround. Moreover, th= ese workarounds may not be sustainable during the whole session lifetime. Now I will rather test the rereworked patch ;-) --=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-KV2fHkfuQ3>