I have recently re-emerge xfree. Now I cannot enter (at) or (dollar) as these are entered with AltGr. Xfree86.0.log seems to hint that xkb is broken (attached)
Created attachment 3284 [details] /var/log/XFree86.0.log
Created attachment 3285 [details] application/octet-stream
Created attachment 3286 [details] /var/log/XFree86.0.log
*** Bug 6824 has been marked as a duplicate of this bug. ***
I get this at top of my log: (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" Attatch your XF86Config, or check that you have a valid keyboard Model/Rules/Layout setup. ------------------snip-------------------------------- Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection ------------------snip--------------------------------
Created attachment 3363 [details] my XF86Config
I tried your addition to XF86Config with the "us" => "dk". This did not help. If I should try "us" then I will need to know some characters that can only be entered with AltGr on a US-keyboard. What is peculiar is that the XF86Config has worked before, so the change ought to be elsewhere.
I think i have a explanatoin for this bug : when I emerge xfree on my box, it deletes the file "/usr/X11R6/lib/X11/xkb/rules/xfree86", but he creates "/usr/X11R6/lib/X11/xkb/rules/._cfg0000_xfree86" despite the fact that this directories wasn't in CONFIG_PROTECT list in make.globals. I think to solve this you only have to add /usr/X11R6/lib/X11/xkb/rules/ to the CONFIG_PROTECT variable in "/etc/make.globals" PS: I was upgrading from 1.2 to 1.4
Hrm, ok. I added /usr/X11R6/lib/X11/xkb/ to CONFIG_PROTECT, so the file should not be unmerged by mistake ...
Still working fine ? With what version of xfree was it btw ?
It seems to be fixed. I will reopen the bug if that is not the case