https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #45 from Samy Mahmoudi <samy.mahmo...@gmail.com> --- (In reply to Jethro Nederhof from comment #44) > Yes, thanks for clarifying it's just the first keypress, you had me worried > there! You're welcome. > I suspect the issue not appearing with display managers is because the first > keypress happens there and triggers the keymap update before XFCE loads, > which makes it work correctly as in the initial workaround with setxkbmap > (skipping this with autologin avoids this). Your explanation makes sense and unifies the two workarounds (using setxkbmap/using a display manager). So I think there's a different issue with xorg initially detecting the wrong keymap until first keypress. > With all the mess that results from recent changes in Xorg, I can only agree > :-) > Compiz may just not handle the keymap updating? Not sure. I could not do compiz-specific tests previously because x11-wm/ccsm has been removed from the ports tree due to Python 2 deprecation, and I did not want to lose time on resurrecting it because I was working on porting Compiz Reloaded. I have just finished porting Compiz Reloaded to FreeBSD (committed upstream in summer 2018 and in May/June 2020) so I was able to test a bit today: compiz triggers desktop switches on CTRL+ALT+AN_ARROW_KEY if and only if one of the workarounds is applied (using setxkbmap/using a display manager). I don't know what conclusion to draw but I will definitely wait for an Xorg fix before coming back to this, as my environment is now fully functional again. > Hope this helps! Yes it does, thank you Jethro. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
