Created attachment 337818 [details] jpg of error message Description of problem: After logging in into the gnome session in F11 Beta, getting a keyboard error popup. My keyboard is German, no dead keys. But the dead keys options is not operable. Version-Release number of selected component (if applicable): F11 Beta How reproducible: Ich time when logging in Steps to Reproduce: 1.login into gnome desktop 2. 3. Actual results: Error activating XKB configuration Expected results: Keyboard works properly. Additional info: Output of gconf-tool: ====================== layouts = [] overrideSettings = false options = [] model = pc101 Output of xprop-root | grep XKB =============================== _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", "" Contents
Same here. Appears once when logging in, appears about 20-times at once when resuming from suspend. Furthermore, after resuming from suspend the AltGr-key doesn't function. This is particularly annoying since the pipe-symbol, at-symbol and the braces only work together with AltGr. Therefor I'd like to set the severity to high. My keyboard is "de" as well.
(In reply to comment #1) > Same here. Appears once when logging in, appears about 20-times at once when > resuming from suspend. > Furthermore, after resuming from suspend the AltGr-key doesn't function. This > is particularly annoying since the pipe-symbol, at-symbol and the braces only > work together with AltGr. Therefor I'd like to set the severity to high. > > My keyboard is "de" as well. I cannot confirm the AltGr problem: on my Box, AltGr operations are all OK.
I counted: after resuming from suspend the error message appears exactly 22 times.
Are those the same bugs (duplicates)? https://bugzilla.redhat.com/show_bug.cgi?id=180861 https://bugzilla.redhat.com/show_bug.cgi?id=494947
Same symptome with a French keyboard. [~ ]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "terminate:ctrl_alt_bksp" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr", "", "" [ ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [] model = I have not noticed any misfunctionning of the keyboard though.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
same here # xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "intl", "terminate:ctrl_alt_bksp" _XKB_RULES_NAMES(STRING) = "evdev", "cymotionlinux", "us", "alt-intl", "grp:shift_caps_toggle" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd model = options = [] layouts = [de-latin1-nodeadkeys]
Fixed by going to System -> Preferences -> Keyboard -> Layouts and selecting "Reset to Defaults" and changing settings again. Maybe changing "Keyboard model" to "Evdev-managed keyboard" would help, too.
Creating a xorg.conf via su -c 'Xorg -configure' and setting up xorg conf with correct xkb values makes everything work as supposed. su -c 'nano /etc/X11/xorg.conf' Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" EndSection Nothing else did help me in any way. This was the only thing which tured out working. [I know this doesn't seem apropriate here, but I just have mention.]
the default configuration returned by Xorg -configure lets X ignore the keyboard section completely and rely on HAL instead. looking at the configuration above, it looks like us + de(nodeadkeys) got mixed up somehow. I need the Xorg.log file and (if you have one) the xorg.conf file please.
Well, it seems that gnome's keyboard config overwrites xorg.conf keyboard settings. Since both have the de variant <dead grave acute> it works as supposed (desktop + laptop both work this way) If you still wan't my xorg.conf /Xorg.0.log tell me....
Created attachment 350611 [details] Xorg.0.log (In reply to comment #5) Fedora rawhide, x86_64, up to date. For a week or so now my es keyboard doesn't react to Alt or AltGr (so I can't go to tty2, nor can I enter a lot of rather important characters). Recently it shows strange characters (an '?' over a black oval) for tilde or pipe. Running "od -c" on the keyboard gives giberish like: 0000000 033 302 272 033 1 033 2 033 3 033 4 033 5 033 + 033 0000020 303 247 \n (this should be backslash, pipe, at, tilde, open/close brackets, open/close braces, i.e. I typed AltGr + º, 1, 2, 3, 4, `, +, ', ç). $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "es", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [es] options = [] model = No xorg.conf file around here. Xorg.0.log attached.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
No problem in the current F12 with the GNOME keyboard configuration (no such error msg).
closing as WORKSFORME as per comment 15