* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
[SOLVED: I missed a comma on one of the keys that ended up unmodified. I didn’t catch it, bc it looked normal, bc all the second column entries had commas, bc they all had entries after them. except «m». that key only has the standard SHIFT levels, no AltGr levels at all. That extra comma made everything unreadable to my system.]
[If you, like me, are trying to build your own custom keyboard layout, I’d recommend overcoming your fear and just making a separate file for it, since a typo in the language file you’re using can make your keyboard useless, but a typo in your custom file means you still have your default file to fall back on. I recommend reading this guide to learn how the XKB configuration files work, and this guide for some extra information, like unicode characters and such]
I’m trying to modify one of the US keyboard variants with this tutorial as a guide (preferred to xmodchar, since every single key except ‘m’ gets two extra characters). I was able to do this once before on Linux Mint 19 (I edited and saved the file in Atom that time, and it prompted me for password before saving). When I tried to do that after upgrading to Linux Mint 20, I had to run Atom as root, and the changes didn’t really take (I edited the «basic» layout, pretty sure I forgot to include the line setting the third option key), and upon restart my system was unable to load a keyboard layout at all, and I had to reinstall.
This time, I’m trying again, editing the «intl» layout. When I save (using Xed run as root), nothing bad seems to happen, but when I try to add a new keyboard layout in preferences, I get the error:
«»»
Error activating xkb configuration
There can be various reasons for this
If you report this situation as a bug, please include the output of
[cut code, see below]
«»»
Running the suggested commands yields:
Code: Select all
~$ xprop -root|grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "terminate:ctrl_alt_bksp"
~$ gsettings get org.gnome.libgnomekbd.keyboard model
''
~$ gsettings get org.gnome.libgnomekbd.keyboard layouts
['us', 'ustintl']
~$ gsettings get org.gnome.libgnomekbd.keyboard options
['grptgrp:shift_caps_toggle']
Which, nothing looks off with that? But I’m not sure.
I ran «sudo dpkg-reconfigure xkb-data» to reload my xkb data and I’m still getting that message.
I restarted my computer and my system was unable to load a keyboard layout. So something I did made the us file unreadable(?). I was able to replace the bad fire with the known good file in a Live session, but I’m kind of at a loss as to what I screwed up.
I’m running Linux Mint 20 with the Cinnamon environment, and I have links to the known good and modified us symbols file (/usr/share/X11/xkb/symbols/us), and while it might be more than necessary, in case it does turn out to be relevant, here’s the output of «inxi -Fxz»:
Code: Select all
~$ inxi -Fxz
System:
Kernel: 5.4.0-48-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI)
v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1405
date: 11/19/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
charge: 55% (should be ignored) status: Discharging
CPU:
Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics
bits: 64 type: MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28746
Speed: 1252 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1257 2: 1257
3: 1258 4: 1258
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia
v: 450.66 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.8 driver: nvidia
unloaded: modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66
direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0a:00.6
Sound Server: ALSA v: k5.4.0-48-generic
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: f000
bus ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 06:00.0
IF: enp6s0 state: down mac: <filter>
Drives:
Local Storage: total: 2.05 TiB used: 414.27 GiB (19.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB
size: 232.89 GiB
ID-2: /dev/sda type: USB vendor: Seagate model: Portable size: 1.82 TiB
Partition:
ID-1: / size: 227.74 GiB used: 71.41 GiB (31.4%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 41.5 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 243 Uptime: 2d 16h 25m Memory: 15.61 GiB used: 3.92 GiB (25.1%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38
What obvious thing did I miss?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
3782
При активации конфигурации ХКВ возникла ошибка ![:(]()
Это может возникнуть по разным причинам.
Если вы будете описывать данную ситуацию в отчете об ошибках, включите
xprop -root grep XKB
gsettings get org. gnome. libgnomekbd. keyboard model
gsettings get org. gnome. libgnomekbd. keyboard layouts
gsettings get org. gnome. libgnomekbd. keyboard optionsxprop -root grep XKB
grep: no such atom on any window.
XKB: no such atom on any window.
Help, pls!
Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
[SOLVED: I missed a comma on one of the keys that ended up unmodified. I didn’t catch it, bc it looked normal, bc all the second column entries had commas, bc they all had entries after them. except «m». that key only has the standard SHIFT levels, no AltGr levels at all. That extra comma made everything unreadable to my system.]
[If you, like me, are trying to build your own custom keyboard layout, I’d recommend overcoming your fear and just making a separate file for it, since a typo in the language file you’re using can make your keyboard useless, but a typo in your custom file means you still have your default file to fall back on. I recommend reading this guide to learn how the XKB configuration files work, and this guide for some extra information, like unicode characters and such]
I’m trying to modify one of the US keyboard variants with this tutorial as a guide (preferred to xmodchar, since every single key except ‘m’ gets two extra characters). I was able to do this once before on Linux Mint 19 (I edited and saved the file in Atom that time, and it prompted me for password before saving). When I tried to do that after upgrading to Linux Mint 20, I had to run Atom as root, and the changes didn’t really take (I edited the «basic» layout, pretty sure I forgot to include the line setting the third option key), and upon restart my system was unable to load a keyboard layout at all, and I had to reinstall.
This time, I’m trying again, editing the «intl» layout. When I save (using Xed run as root), nothing bad seems to happen, but when I try to add a new keyboard layout in preferences, I get the error:
«»»
Error activating xkb configuration
There can be various reasons for this
If you report this situation as a bug, please include the output of
[cut code, see below]
«»»
Running the suggested commands yields:
Code: Select all
~$ xprop -root|grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "terminate:ctrl_alt_bksp"
~$ gsettings get org.gnome.libgnomekbd.keyboard model
''
~$ gsettings get org.gnome.libgnomekbd.keyboard layouts
['us', 'ustintl']
~$ gsettings get org.gnome.libgnomekbd.keyboard options
['grptgrp:shift_caps_toggle']
Which, nothing looks off with that? But I’m not sure.
I ran «sudo dpkg-reconfigure xkb-data» to reload my xkb data and I’m still getting that message.
I restarted my computer and my system was unable to load a keyboard layout. So something I did made the us file unreadable(?). I was able to replace the bad fire with the known good file in a Live session, but I’m kind of at a loss as to what I screwed up.
I’m running Linux Mint 20 with the Cinnamon environment, and I have links to the known good and modified us symbols file (/usr/share/X11/xkb/symbols/us), and while it might be more than necessary, in case it does turn out to be relevant, here’s the output of «inxi -Fxz»:
Code: Select all
~$ inxi -Fxz
System:
Kernel: 5.4.0-48-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI)
v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1405
date: 11/19/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
charge: 55% (should be ignored) status: Discharging
CPU:
Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics
bits: 64 type: MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28746
Speed: 1252 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1257 2: 1257
3: 1258 4: 1258
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia
v: 450.66 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.8 driver: nvidia
unloaded: modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66
direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0a:00.6
Sound Server: ALSA v: k5.4.0-48-generic
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: f000
bus ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 06:00.0
IF: enp6s0 state: down mac: <filter>
Drives:
Local Storage: total: 2.05 TiB used: 414.27 GiB (19.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB
size: 232.89 GiB
ID-2: /dev/sda type: USB vendor: Seagate model: Portable size: 1.82 TiB
Partition:
ID-1: / size: 227.74 GiB used: 71.41 GiB (31.4%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 41.5 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 243 Uptime: 2d 16h 25m Memory: 15.61 GiB used: 3.92 GiB (25.1%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38
What obvious thing did I miss?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Модератор: Модераторы разделов
-
malor
- Сообщения: 335
Gnome: Ошибка активирования параметров XKB
При загрузке в Gnome выскакивает окошко с таким содержанием:
Ошибка активирования параметров XKB.
Она может произойти при следующих обстоятельствах:
— ошибка в библиотеке libxklavier
— ошибка в X-сервере (утилиты xkbcomp, xmodmap)
— X-сервер имеет несовместимую реализацию libxkbfileДанные о версии X-сервера:
The X.Org Foundation
70101000При составлении отчета об ошибке пожалуйста включите:
— Результат xprop -root | grep XKB
— Результат gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Чел сказал, что такое стало появляться после того как он один раз грузанулся вместо Гнома в KDE.
# xprop -root| grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «xorg», «pc105», «us,ru», «,winkeys», «grp:ctrl_shift_toggle,grp_led:scroll»
_XKB_RULES_NAMES(STRING) = «xorg», «pc105», «us,ru(winkeys)», «», «grp:ctrl_shift_toggle,grp_led:scroll»
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
overrideSettings = true
options = []
Несколько ссылок от поисковика:
https://bugzilla.altlinux.org/show_bug.cgi?id=5266
http://lists.altlinux.org/pipermail/sisyph…ril/080191.html
https://bugzilla.altlinux.org/show_bug.cgi?id=9147
-
arachnid
- Модератор
- Сообщения: 1099
- ОС: freeBSD
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
arachnid » 27.03.2007 10:38
malor писал(а): ↑
27.03.2007 08:21
При загрузке в Gnome выскакивает окошко с таким содержанием:
Ошибка активирования параметров XKB.
Она может произойти при следующих обстоятельствах:
— ошибка в библиотеке libxklavier
— ошибка в X-сервере (утилиты xkbcomp, xmodmap)
— X-сервер имеет несовместимую реализацию libxkbfileДанные о версии X-сервера:
The X.Org Foundation
70101000При составлении отчета об ошибке пожалуйста включите:
— Результат xprop -root | grep XKB
— Результат gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbdЧел сказал, что такое стало появляться после того как он один раз грузанулся вместо Гнома в KDE.
# xprop -root| grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «xorg», «pc105», «us,ru», «,winkeys», «grp:ctrl_shift_toggle,grp_led:scroll»
_XKB_RULES_NAMES(STRING) = «xorg», «pc105», «us,ru(winkeys)», «», «grp:ctrl_shift_toggle,grp_led:scroll»
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
overrideSettings = true
options = []Несколько ссылок от поисковика:
https://bugzilla.altlinux.org/show_bug.cgi?id=5266
http://lists.altlinux.org/pipermail/sisyph…ril/080191.html
https://bugzilla.altlinux.org/show_bug.cgi?id=9147
если это вопрос, то подтвержу, что после обновления гнома до 2.18 в оном при использвоании win раскладки стали падать темы (сервер, за оных отвечающий). удалил в xorg.conf русскую виндовую раскладку — полегчало, но менеджер тем продолжает падать при разблокировании экрана 
-= freeBSD stable, fluxbox =-
«если ты будешь со мной спорить, я тебя запишу в книжечку!» (с) Ежик
-
malor
- Сообщения: 335
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
malor » 27.03.2007 11:04
Да, вопрос конечно был;) — как избавится от того сообщения? Но падений никаких пока еще замечено не было. Надеюсь не будет.
>>удалил в xorg.conf русскую виндовую раскладку
Какую именно строку?
Что-то поменяли в ‘Option «XkbLayout» «us,ru(winkeys)»»‘?
-
arachnid
- Модератор
- Сообщения: 1099
- ОС: freeBSD
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
arachnid » 27.03.2007 12:15
malor писал(а): ↑
27.03.2007 11:04
Да, вопрос конечно был
— как избавится от того сообщения? Но падений никаких пока еще замечено не было. Надеюсь не будет.
>>удалил в xorg.conf русскую виндовую раскладку
Какую именно строку?
Что-то поменяли в ‘Option «XkbLayout» «us,ru(winkeys)»»‘?
убрал winkeys
сейчас обновился, падения пропали, попробовал включить winkeys обранто — ничего не изменилось (в том смысле, что падений нет, но и раскладка невиндовая
-= freeBSD stable, fluxbox =-
«если ты будешь со мной спорить, я тебя запишу в книжечку!» (с) Ежик
-
cherep36
- Сообщения: 128
- Статус: Йа пробудилсо!
- ОС: Arch Linux
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
cherep36 » 03.04.2007 22:44
arachnid писал(а): ↑
27.03.2007 12:15
сейчас обновился, падения пропали, попробовал включить winkeys обранто — ничего не изменилось (в том смысле, что падений нет, но и раскладка невиндовая
чтобы раскладка была виндовая и переключалась нормально, воткни в автозагрузку wm
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleменя тока это и спасает, и не надо никаких kxkb, kkbswitch и т.д.
-
o_serg
- Сообщения: 106
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
o_serg » 05.04.2007 08:44
cherep36 писал(а): ↑
03.04.2007 22:44
чтобы раскладка была виндовая и переключалась нормально, воткни в автозагрузку wm
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleменя тока это и спасает, и не надо никаких kxkb, kkbswitch и т.д.
У меня тоже проблема с xkb.
При вводе
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleговорит «Can’t find rule xorg». Что он там не может найти и почему? замучился уже с клавой…
-
cherep36
- Сообщения: 128
- Статус: Йа пробудилсо!
- ОС: Arch Linux
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
cherep36 » 05.04.2007 20:52
o_serg
а в xorg.conf есть такое
Код: Выделить всё
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,ru(winkeys)"
Option "XkbOption" "grp:ctrl_shift_toggle,grp_led:scroll"
Option "XkbRules" "xorg"
EndSection???
Самое главное Option «XkbRules» «xorg», если xfree86 то переключение может и не работать.
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
0
0
Ubuntu feisty. После запуска гнома вылезает такое сообщение: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 70200000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Делаю как советуют, получаю следующее: master@master:~$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us,ru", ",winkeys", "grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us,ru", ",winkeys", "grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll" master@master:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [en,ru winkeys] model = pc105 options = [lv3 lv3:ralt_switch,grp grp:ctrl_shift_toggle,altwin altwin:super_win] overrideSettings = true
Кратко: выполните
Код: Выделить всё
zgrep -A 3 2008-04-19 /usr/share/doc/xkb-data/changelog.gzЕсли вывод команды у вас совпадает с приведённым ниже:
foo@bar
2008-04-19 Sergey Udaltsov
* symbols/ru, rules/base.xml.in, rules/compat/variantRename.lst:
changed ru(winkeys) to default
то смените ru(winkeys) на ru в
- /etc/X11/xorg.conf
- в центре управления вашего DE
Некратко…
После dist-upgrade я столкнулся с:
- сообщением об ошибке Error activating xkb configuration, появляющимся при загрузке Gnome;
- невозможностью переключить раскладку клавиатуры на русскую (ни посредством клавиши, отвечающей за это переключение, ни посредством апплета-индикатора раскладок клавиатуры);
- возникновением всё той же ошибки Error activating xkb configuration при попытке изменения каких-либо параметров клавиатуры или комбинаций горячих клавиш (в соответствующих разделах центра управления Gnome).
В сообщении об ошибке рекомендовалось просмотреть вывод xprop -root | grep XKB. Он оказался следующим:
foo@bar
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc104", "us,ru", ",winkeys", "grp:caps_toggle,grp_led:scroll"
_XKB_RULES_NAMES(STRING) = "xorg", "pc104", "us,ru", ",winkeys", "grp_led:scroll,altwin:hyper_win,grp:caps_toggle"
Далее, в логах gdm было обнаружено сообщение об ошибке:
foo@bar
$ grep -A 4 XKEYBOARD /var/log/gdm/:0.log
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: No Symbols named "winkeys" in the include file "ru"
> Exiting
> Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server
А для меня errors-то как раз fatal… 
В процессах поиска определения раскладки winkeys нашлось примечание:
foo@bar
$ grep -A 2 -E "bwinkeys" /usr/share/X11/xkb/symbols/ru
// Windows layout, former winkeys
partial default alphanumeric_keys
xkb_symbols "basic" {
После чего в /etc/X11/xorg.conf строчки
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"были заменены на
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",basic"… 
…
После перезагрузки X’ов проблема исчезла. 
Дополнительные поиски в интернете (с уточнённым запросом) принесли две полезных ссылки:
- X.org 7.3, Debian Sid и клавиатура
(stasikos) писал(а):После aptitude upgrade неожиданно обнаружил, что в иксах перестали работать старые комбинации клавиш (Ctrl-Alt-F1, например, гг). В поисках проблемы наткнулся на пакет xkb-data-legacy, который заменяет новый xkb-data — это решает проблему.
Но позже adjkerntz с #linux подсказал, в чем проблема — дело в том что вариант winkeys из новой версии xkb-data убрали, поэтому XkbVariant из конфига надо убирать.
Итак, я снова установил xkb-data и стер «,winkeys» из конфига xorg.conf — и полет нормальный!
- Debian Bug report logs — #480124
xkb-data: language switch doesn’t work for ru layout after upgrade
UPD (12.05.2008)
Ещё одна ссылка (форум ЛОР’а): Winkeys’окапец
(anonymous) писал(а):Сегодня обнаружил, что в Debian Unstable с вариантом раскладки winkeys переключалка не работает. Оказалось, что в /usr/share/X11/xkb/symbols/ru вариант winkeys стал basic, а basic переименовали в legacy. При этом winkeys более не является правильных вариантом.
Представляю новичков, тщетно пытающихся настроить xkb по старым мануалам с us,ru(winkeys)
Чуть более подробное описание того, что и как нужно изменить в xorg.conf:
adjkerntz писал(а): ↑
12.05.2008 15:59
130 писал(а): ↑
11.05.2008 03:37
Option «XkbVariant» «,basic»
эта строчка вообще не нужна: basic — это вариант по умолчанию.
Таким образом, если в xorg.conf было что-то наподобие:
то следует удалить (winkeys), чтобы в итоге получилось:
Иначе, если в xorg.conf было что-то наподобие:
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"то можно удалить строчку c XkbVariant целиком, чтобы в итоге получилось:
А если в xorg.conf нет ничего похожего ни на первый вариант, ни на второй, то, вероятнее всего, следует изменять настройки в центре управления DE (Gnome/KDE).
> There are 10 kinds of people in the world, those that understand binary, and those that don’t.
There are two kinds of people in the world, those that divide everything into two kinds, and those that don’t.
[SOLVED: I missed a comma on one of the keys that ended up unmodified. I didn’t catch it, bc it looked normal, bc all the second column entries had commas, bc they all had entries after them. except «m». that key only has the standard SHIFT levels, no AltGr levels at all. That extra comma made everything unreadable to my system.]
[If you, like me, are trying to build your own custom keyboard layout, I’d recommend overcoming your fear and just making a separate file for it, since a typo in the language file you’re using can make your keyboard useless, but a typo in your custom file means you still have your default file to fall back on. I recommend reading this guide to learn how the XKB configuration files work, and this guide for some extra information, like unicode characters and such]
I’m trying to modify one of the US keyboard variants with this tutorial as a guide (preferred to xmodchar, since every single key except ‘m’ gets two extra characters). I was able to do this once before on Linux Mint 19 (I edited and saved the file in Atom that time, and it prompted me for password before saving). When I tried to do that after upgrading to Linux Mint 20, I had to run Atom as root, and the changes didn’t really take (I edited the «basic» layout, pretty sure I forgot to include the line setting the third option key), and upon restart my system was unable to load a keyboard layout at all, and I had to reinstall.
This time, I’m trying again, editing the «intl» layout. When I save (using Xed run as root), nothing bad seems to happen, but when I try to add a new keyboard layout in preferences, I get the error:
«»»
Error activating xkb configuration
There can be various reasons for this
If you report this situation as a bug, please include the output of
[cut code, see below]
«»»
Running the suggested commands yields:
Code: Select all
~$ xprop -root|grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "terminate:ctrl_alt_bksp"
~$ gsettings get org.gnome.libgnomekbd.keyboard model
''
~$ gsettings get org.gnome.libgnomekbd.keyboard layouts
['us', 'ustintl']
~$ gsettings get org.gnome.libgnomekbd.keyboard options
['grptgrp:shift_caps_toggle']
Which, nothing looks off with that? But I’m not sure.
I ran «sudo dpkg-reconfigure xkb-data» to reload my xkb data and I’m still getting that message.
I restarted my computer and my system was unable to load a keyboard layout. So something I did made the us file unreadable(?). I was able to replace the bad fire with the known good file in a Live session, but I’m kind of at a loss as to what I screwed up.
I’m running Linux Mint 20 with the Cinnamon environment, and I have links to the known good and modified us symbols file (/usr/share/X11/xkb/symbols/us), and while it might be more than necessary, in case it does turn out to be relevant, here’s the output of «inxi -Fxz»:
Code: Select all
~$ inxi -Fxz
System:
Kernel: 5.4.0-48-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI)
v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1405
date: 11/19/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
charge: 55% (should be ignored) status: Discharging
CPU:
Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics
bits: 64 type: MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28746
Speed: 1252 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1257 2: 1257
3: 1258 4: 1258
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia
v: 450.66 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.8 driver: nvidia
unloaded: modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66
direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0a:00.6
Sound Server: ALSA v: k5.4.0-48-generic
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: f000
bus ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 06:00.0
IF: enp6s0 state: down mac: <filter>
Drives:
Local Storage: total: 2.05 TiB used: 414.27 GiB (19.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB
size: 232.89 GiB
ID-2: /dev/sda type: USB vendor: Seagate model: Portable size: 1.82 TiB
Partition:
ID-1: / size: 227.74 GiB used: 71.41 GiB (31.4%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 41.5 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 243 Uptime: 2d 16h 25m Memory: 15.61 GiB used: 3.92 GiB (25.1%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38
What obvious thing did I miss?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Description of problem: After startup I get: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10503000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd The requestet reports are: [fidepus@FUCKUP ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "de", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "de", "", "" [fidepus@FUCKUP ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [de-latin1-nodeadkeys] model = options = [] Version-Release number of selected component (if applicable): How reproducible: happens allways Steps to Reproduce: 1. start up the machinge 2. autologin 3. error Actual results: Expected results: Additional info:
Comment 1
Matěj Cepl
2009-02-07 14:07:01 UTC
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Comment 4
Matěj Cepl
2009-02-08 14:29:38 UTC
Are you able to reproduce this using only open source software? I see that you are using nVidia's binary-only driver. I understand that this bug is not primarily about graphic drivers, but unfortunately it is quite possible that some other part of whole Xorg suite of software got changed by installation of nvidia. Please refer to https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers and clean your system to the original Fedora state, which we can support. Then, please regenerate and re-attach X server log file (/var/log/Xorg.*.log; don't use any /etc/X11/xorg.conf for this testing) to the bug report. Thanks in advance.
Comment 5
Peter Hutterer
2009-02-09 02:07:09 UTC
(In reply to comment #0)
> [fidepus@FUCKUP ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
> layouts = [de-latin1-nodeadkeys]
> model =
> options = []
What keyboard layout do you want to activate here? I can't find any such layout, neither in the gnome config, nor in xkeyboard-config.
Comment 6
Eric Tanguy
2009-02-26 18:49:46 UTC
Same problem here : $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr-latin9", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us latin9,fr] model = pc105 options = [grp grp:shift_caps_toggle] this problem is since recent updates and if i remember well there a xorg one.
Comment 7
galerien
2009-02-28 09:42:58 UTC
same problem after update : $ xprop -root |grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr-latin9", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] model = options = []
Comment 8
Peter Hutterer
2009-03-02 00:16:57 UTC
this seems to be a gnome problem. there's no us-latin9 keyboard, somehow the gconf keys seem to get mixed up. does this happen with a test user?
Comment 9
Julian Sikorski
2009-03-12 22:33:59 UTC
This also happens with freshly installed rawhide: [julas@rawhide ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "pl", "", "" [julas@rawhide ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [pl_PL.UTF-8] options = [] model =
Comment 10
Vinagre
2009-03-13 15:00:15 UTC
Same here, on a fresh rawhide installation, I don't have any xorg.conf Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10600000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd ---------------------------------------------------- $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "pt", "", "" --------------------------------------------------------- $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [en_US.UTF-8] options = [] model =
Comment 12
Peter Hutterer
2009-03-16 00:10:58 UTC
*** Bug 489408 has been marked as a duplicate of this bug. ***
Comment 13
Eric Paris
2009-03-20 18:57:56 UTC
*** Bug 489054 has been marked as a duplicate of this bug. ***
Comment 14
Ray Strode [halfline]
2009-03-20 20:17:36 UTC
Should be fixed with the latest gdm (2.26.0-6.fc11) for *new* users. Existing users will still be hosed. The way to clean it up is sort of gross: su -c "gconftool-2 --config-source=xml:readwrite:/var/lib/gdm/.gconf --unset /apps/gdm/simple-greeter/recent-layouts --direct" rm -f ~/.dmrc gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd Need to figure out if there's a way I can do that automatically.
Comment 15
Andreas Thienemann
2009-04-01 19:30:35 UTC
*** Bug 491439 has been marked as a duplicate of this bug. ***
Comment 16
Andreas Thienemann
2009-04-01 19:39:08 UTC
*** Bug 491759 has been marked as a duplicate of this bug. ***
Comment 17
Andreas Thienemann
2009-04-01 19:47:18 UTC
(In reply to comment #14) > Should be fixed with the latest gdm (2.26.0-6.fc11) for *new* users. Existing > users will still be hosed. Nope. I cannot confirm that it's working for *new* users. gdm-2.26.0-7.fc11.i586 on a fresh rawhide scratch installation. Same message appears on first login. [andreas@workstation ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", "" [andreas@workstation ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [] model = [andreas@workstation ~]$ > The way to clean it up is sort of gross: > > su -c "gconftool-2 --config-source=xml:readwrite:/var/lib/gdm/.gconf --unset > /apps/gdm/simple-greeter/recent-layouts --direct" > rm -f ~/.dmrc > gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd Doesn't fix the problem. The message appears nevertheless as soon as control is passed from gdm to the normal user session.
Comment 18
Andreas Thienemann
2009-04-08 16:11:52 UTC
Still not fixed with rawhide as of 20090408, neither with deleting the kbd configuration for existing users nor for new users.
Comment 19
Peter Hutterer
2009-04-09 05:01:50 UTC
*** Bug 492483 has been marked as a duplicate of this bug. ***
Comment 20
Joachim Backes
2009-04-10 08:33:11 UTC
Having additionally the problem that the nodeadkeys switch does not operate correctly: the handling of "|@[]" on a german nodeadkeys keyboard is correct, but I have to type the tilde character "~" twice and not once.
Comment 21
Andreas Thienemann
2009-04-10 09:13:38 UTC
(In reply to comment #20)
> Having additionally the problem that the nodeadkeys switch does not operate
> correctly: the handling of "|@[]" on a german nodeadkeys keyboard is correct,
> but I have to type the tilde character "~" twice and not once.
Confirmed. Same here.
|@[] are not deadkeys, ~´`^ are.
Comment 22
Joachim Backes
2009-04-10 09:49:53 UTC
You are right ;-) Weird: My keyboard model is "Generic 101-key PC" with USA layout (installed by anaconda as a "german/nodeadkeys" keyboard) , but it functions as it would be a german keyboard (umlauts äöü or s sharp ß are right). But if I switch by System->preferences->keyboard to "Germany Eliminate dead keys" by using the +ADD button in the "Keyboard Preferences" window instead of USA, then AltGr does no more function: getting only + sign instead of ~, or getting no ^ char.
Comment 23
Joachim Backes
2009-04-13 11:00:07 UTC
Got rid from all described problems after updating my system on monday, april 13. Now my keyboard controls: Keyboard model: Generic 101-Keys PC Layout: Only "Germany Eliminate dead keys" added and selected. (No more USA layout needed). The AltGr, tilde (~) and the ^ key now work correctly.
Comment 24
Andreas Thienemann
2009-04-13 13:02:59 UTC
(In reply to comment #23)
> Got rid from all described problems after updating my system on monday, april
> 13.
>
> Now my keyboard controls:
>
> Keyboard model: Generic 101-Keys PC
> Layout: Only "Germany Eliminate dead keys" added and selected. (No more USA
> layout needed).
>
> The AltGr, tilde (~) and the ^ key now work correctly.
Did you set this manually in the configuration tool or was it autodetected?
If you set it manually, it works but can be considered a workaroung. It should be set automatically.
Comment 25
Joachim Backes
2009-04-13 14:10:03 UTC
No, I set it manually (I didn't try a Fc11 re-install).
Comment 26
Matthieu Araman
2009-04-13 23:52:00 UTC
with rawhide updated for today, after applying above command to reset config, still have the same error message.
Comment 27
Robert Nichols
2009-04-14 02:08:53 UTC
To fix the problem for an existing user I had to delete directory ~/.gconf/desktop/gnome/peripherals/keyboard .
Comment 28
Andreas Thienemann
2009-04-18 13:19:54 UTC
Problem is still happening on a new rawhide installation, setting F11Blocker
Comment 29
Joachim Frieben
2009-04-26 12:04:42 UTC
After a fresh install from current "rawhide", I do obtain multiple instances of the "Error activating XKB configuration." error window. During install, I had chosen a keyboard layout "German w/o dead keys" for a German PS/2 keyboard attached to an IBM ThinkPad T23. Furthermore, I get: $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "terminate:ctrl_alt_bksp" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [] model =
Comment 30
Matthias Clasen
2009-04-28 05:03:12 UTC
Did you select a layout on the login screen ? What does echo $GDM_KEYBOARD_LAYOUT show in this situation ? And what about lshal | grep xkb ?
Comment 31
Need Real Name
2009-04-28 06:20:37 UTC
de_AT.UTF-8 input.xkb.layout = 'us' (string) input.xkb.model = 'evdev' (string) input.xkb.rules = 'base' (string) input.xkb.variant = '' (string) input.xkb.layout = 'us' (string) input.xkb.model = 'evdev' (string) input.xkb.rules = 'base' (string) input.xkb.variant = '' (string) input.xkb.layout = 'de' (string) input.xkb.model = 'pc105' (string) input.xkb.options = 'terminate:ctrl_alt_bksp' (string) input.xkb.rules = 'base' (string) input.xkb.variant = 'nodeadkeys' (string)
Comment 32
Joachim Frieben
2009-04-28 10:58:44 UTC
The issue stops by adding a German keyboard layout by means gnome-keyboard-properties, setting it to be the default one and removing the US layout which was the only one displayed in "Selected Layouts" although the system layout was "German w/o dead keys".
Comment 33
Need Real Name
2009-04-28 16:11:36 UTC
But we can't keep asking people to fix their keyboard layouts. This is what? The third time this has happened? It should just work.
Comment 34
Matthias Clasen
2009-04-28 16:37:50 UTC
To make sure that it just works, you need to help identify what is different in your setup that makes this happen to you, since it does not happen here.
Comment 35
Need Real Name
2009-04-28 17:31:38 UTC
Of course. But as soon as I implement the workaround of reconfiguring my keyboard, you lose that information. So what do you need to know?
Comment 36
Andreas Thienemann
2009-04-28 20:12:17 UTC
Setting the severity to high. There have been several reports of this triggering F11 preview release users on IRC.
Comment 38
Joachim Frieben
2009-04-30 05:07:22 UTC
After updating to gnome-settings-daemon-2.26.1-4.fc11, the issue does not appear for a new user anymore.
Comment 39
Steven Moix
2009-05-01 18:09:17 UTC
I can confirm that, after updating to gnome-settings-daemon-2.26.1-4.fc11, the issue does not appear for a new user anymore (nor does it for old users). I'm using an fr_CH keyboard layout.
Comment 40
Matthias Clasen
2009-05-02 05:44:14 UTC
Ok, I'll take this as sufficient proof that things are fixed.
Comment 41
Peter Hutterer
2009-05-11 00:19:08 UTC
*** Bug 496784 has been marked as a duplicate of this bug. ***
Comment 42
Matthieu Araman
2009-05-11 07:01:48 UTC
I can also confirm that this fixed it on french install + keyboard both for new users and for existing users.
#
13 лет, 10 месяцев назад
Сообщения:
574
Участник с: 21 февраля 2009
Использую GNOME, смена раскладки клавиатуры никак не хочет работать, а при настроке в Параметры Клавиатуры выдает ошибку:
Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10503000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Вот чать моего /etc/X11/xorg.conf
Section “InputDevice”
Identifier “Keyboard0”
Driver “keyboard”
Option “CoreKeyboard”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105”
Option “XkbLayout” “ru,us”
Option “XkbVariant” “,winkeys”
Option “XkbOptions” “grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll”
EndSection
вот часть /etc/rc.conf
LOCALE=“ru_RU.UTF-8”
HARDWARECLOCK=“local”
USEDIRECTISA=“no”
TIMEZONE=“Asia/Novosibirsk”
KEYMAP=“ru”
CONSOLEFONT=“/usr/share/kbd/consolefonts/cyr-sun16.psfu.gz”
CONSOLEMAP=
USECOLOR=“yes”
Пробовал в гномовских настройках раскладки клавиатуры восстанавливать значения по умолчанию — не помогает!
Подскажите что делать и куда копать.
xSPiRiTx
#
13 лет, 10 месяцев назад
Сообщения:
574
Участник с: 21 февраля 2009
РЕШЕНО:
просто убрал эту строчку из xorg.conf
Option "XkbVariant" ",winkeys"
* Cinnamon version (cinnamon --version)
Cinnamon 4.4.8
- Please specify if you are using the daily builds PPA
(https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds).
No
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Ubuntu Cinnamon Remix 20.04
* Graphics hardware *and* driver used
GeForce GTX 1650
Nvidia 440.100
* 32 or 64 bit
64 bit
* Attach /home/<username>/.xsession-errors, or /var/log/syslog
[xsession-errors.zip](https://github.com/linuxmint/cinnamon/files/5133368/xsession-errors.zip)
Issue
On login or when trying to add an additional keyboard layout, the error message «error activating XKB configuration.
There can be various reasons for that.
If you report this situation as a bug, include the results of xprop -root | grep XKB
Output of xprop:
~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
_XKB_RULES_NAMES(STRING) = «evdev», «applealu_iso», «gb», «mac», «»
Steps to reproduce
Log into Cinnamon session
OR
Configure keyboard layouts/add second keyboard layout
The keyboard layouts are not displayed in the taskbar as usual
Expected behaviour
Login without the error message
Add keyboard layouts without the error message
Find the keyboard layout indicator in the taskbar
Other information
Configuration info, if applicable
If this bug report is related to an Applet, Desklet or Extension, please paste (or use a pastebin service) the offending extension’s settings, if it has any. You can obtain this by opening its configuration, clicking the ‘hamburger’ button in the upper-right corner of the window, and selecting «Export to a file». Please be sure to review the contents and remove any personal data it may contain.
0
0
Ubuntu feisty. После запуска гнома вылезает такое сообщение: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 70200000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Делаю как советуют, получаю следующее: master@master:~$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us,ru", ",winkeys", "grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us,ru", ",winkeys", "grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll" master@master:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [en,ru winkeys] model = pc105 options = [lv3 lv3:ralt_switch,grp grp:ctrl_shift_toggle,altwin altwin:super_win] overrideSettings = true
Кратко: выполните
Код: Выделить всё
zgrep -A 3 2008-04-19 /usr/share/doc/xkb-data/changelog.gzЕсли вывод команды у вас совпадает с приведённым ниже:
foo@bar
2008-04-19 Sergey Udaltsov
* symbols/ru, rules/base.xml.in, rules/compat/variantRename.lst:
changed ru(winkeys) to default
то смените ru(winkeys) на ru в
- /etc/X11/xorg.conf
- в центре управления вашего DE
Некратко…
После dist-upgrade я столкнулся с:
- сообщением об ошибке Error activating xkb configuration, появляющимся при загрузке Gnome;
- невозможностью переключить раскладку клавиатуры на русскую (ни посредством клавиши, отвечающей за это переключение, ни посредством апплета-индикатора раскладок клавиатуры);
- возникновением всё той же ошибки Error activating xkb configuration при попытке изменения каких-либо параметров клавиатуры или комбинаций горячих клавиш (в соответствующих разделах центра управления Gnome).
В сообщении об ошибке рекомендовалось просмотреть вывод xprop -root | grep XKB. Он оказался следующим:
foo@bar
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc104", "us,ru", ",winkeys", "grp:caps_toggle,grp_led:scroll"
_XKB_RULES_NAMES(STRING) = "xorg", "pc104", "us,ru", ",winkeys", "grp_led:scroll,altwin:hyper_win,grp:caps_toggle"
Далее, в логах gdm было обнаружено сообщение об ошибке:
foo@bar
$ grep -A 4 XKEYBOARD /var/log/gdm/:0.log
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: No Symbols named "winkeys" in the include file "ru"
> Exiting
> Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server
А для меня errors-то как раз fatal…
В процессах поиска определения раскладки winkeys нашлось примечание:
foo@bar
$ grep -A 2 -E "bwinkeys" /usr/share/X11/xkb/symbols/ru
// Windows layout, former winkeys
partial default alphanumeric_keys
xkb_symbols "basic" {
После чего в /etc/X11/xorg.conf строчки
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"были заменены на
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",basic"… …
После перезагрузки X’ов проблема исчезла.
Дополнительные поиски в интернете (с уточнённым запросом) принесли две полезных ссылки:
- X.org 7.3, Debian Sid и клавиатура
(stasikos) писал(а):После aptitude upgrade неожиданно обнаружил, что в иксах перестали работать старые комбинации клавиш (Ctrl-Alt-F1, например, гг). В поисках проблемы наткнулся на пакет xkb-data-legacy, который заменяет новый xkb-data — это решает проблему.
Но позже adjkerntz с #linux подсказал, в чем проблема — дело в том что вариант winkeys из новой версии xkb-data убрали, поэтому XkbVariant из конфига надо убирать.
Итак, я снова установил xkb-data и стер «,winkeys» из конфига xorg.conf — и полет нормальный!
- Debian Bug report logs — #480124
xkb-data: language switch doesn’t work for ru layout after upgrade
UPD (12.05.2008)
Ещё одна ссылка (форум ЛОР’а): Winkeys’окапец
(anonymous) писал(а):Сегодня обнаружил, что в Debian Unstable с вариантом раскладки winkeys переключалка не работает. Оказалось, что в /usr/share/X11/xkb/symbols/ru вариант winkeys стал basic, а basic переименовали в legacy. При этом winkeys более не является правильных вариантом.
Представляю новичков, тщетно пытающихся настроить xkb по старым мануалам с us,ru(winkeys)
Чуть более подробное описание того, что и как нужно изменить в xorg.conf:
adjkerntz писал(а): ↑
12.05.2008 15:59
130 писал(а): ↑
11.05.2008 03:37
Option «XkbVariant» «,basic»
эта строчка вообще не нужна: basic — это вариант по умолчанию.
Таким образом, если в xorg.conf было что-то наподобие:
то следует удалить (winkeys), чтобы в итоге получилось:
Иначе, если в xorg.conf было что-то наподобие:
Код: Выделить всё
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"то можно удалить строчку c XkbVariant целиком, чтобы в итоге получилось:
А если в xorg.conf нет ничего похожего ни на первый вариант, ни на второй, то, вероятнее всего, следует изменять настройки в центре управления DE (Gnome/KDE).
> There are 10 kinds of people in the world, those that understand binary, and those that don’t.
There are two kinds of people in the world, those that divide everything into two kinds, and those that don’t.
[SOLVED: I missed a comma on one of the keys that ended up unmodified. I didn’t catch it, bc it looked normal, bc all the second column entries had commas, bc they all had entries after them. except «m». that key only has the standard SHIFT levels, no AltGr levels at all. That extra comma made everything unreadable to my system.]
[If you, like me, are trying to build your own custom keyboard layout, I’d recommend overcoming your fear and just making a separate file for it, since a typo in the language file you’re using can make your keyboard useless, but a typo in your custom file means you still have your default file to fall back on. I recommend reading this guide to learn how the XKB configuration files work, and this guide for some extra information, like unicode characters and such]
I’m trying to modify one of the US keyboard variants with this tutorial as a guide (preferred to xmodchar, since every single key except ‘m’ gets two extra characters). I was able to do this once before on Linux Mint 19 (I edited and saved the file in Atom that time, and it prompted me for password before saving). When I tried to do that after upgrading to Linux Mint 20, I had to run Atom as root, and the changes didn’t really take (I edited the «basic» layout, pretty sure I forgot to include the line setting the third option key), and upon restart my system was unable to load a keyboard layout at all, and I had to reinstall.
This time, I’m trying again, editing the «intl» layout. When I save (using Xed run as root), nothing bad seems to happen, but when I try to add a new keyboard layout in preferences, I get the error:
«»»
Error activating xkb configuration
There can be various reasons for this
If you report this situation as a bug, please include the output of
[cut code, see below]
«»»
Running the suggested commands yields:
Code: Select all
~$ xprop -root|grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "terminate:ctrl_alt_bksp"
~$ gsettings get org.gnome.libgnomekbd.keyboard model
''
~$ gsettings get org.gnome.libgnomekbd.keyboard layouts
['us', 'ustintl']
~$ gsettings get org.gnome.libgnomekbd.keyboard options
['grptgrp:shift_caps_toggle']
Which, nothing looks off with that? But I’m not sure.
I ran «sudo dpkg-reconfigure xkb-data» to reload my xkb data and I’m still getting that message.
I restarted my computer and my system was unable to load a keyboard layout. So something I did made the us file unreadable(?). I was able to replace the bad fire with the known good file in a Live session, but I’m kind of at a loss as to what I screwed up.
I’m running Linux Mint 20 with the Cinnamon environment, and I have links to the known good and modified us symbols file (/usr/share/X11/xkb/symbols/us), and while it might be more than necessary, in case it does turn out to be relevant, here’s the output of «inxi -Fxz»:
Code: Select all
~$ inxi -Fxz
System:
Kernel: 5.4.0-48-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI)
v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1405
date: 11/19/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
charge: 55% (should be ignored) status: Discharging
CPU:
Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics
bits: 64 type: MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28746
Speed: 1252 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1257 2: 1257
3: 1258 4: 1258
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia
v: 450.66 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.8 driver: nvidia
unloaded: modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66
direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0a:00.6
Sound Server: ALSA v: k5.4.0-48-generic
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: f000
bus ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 06:00.0
IF: enp6s0 state: down mac: <filter>
Drives:
Local Storage: total: 2.05 TiB used: 414.27 GiB (19.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB
size: 232.89 GiB
ID-2: /dev/sda type: USB vendor: Seagate model: Portable size: 1.82 TiB
Partition:
ID-1: / size: 227.74 GiB used: 71.41 GiB (31.4%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 41.5 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 243 Uptime: 2d 16h 25m Memory: 15.61 GiB used: 3.92 GiB (25.1%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38
What obvious thing did I miss?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Description of problem: After startup I get: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10503000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd The requestet reports are: [fidepus@FUCKUP ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "pc105", "de", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "de", "", "" [fidepus@FUCKUP ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [de-latin1-nodeadkeys] model = options = [] Version-Release number of selected component (if applicable): How reproducible: happens allways Steps to Reproduce: 1. start up the machinge 2. autologin 3. error Actual results: Expected results: Additional info:
Comment 1
Matěj Cepl
2009-02-07 14:07:01 UTC
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Comment 4
Matěj Cepl
2009-02-08 14:29:38 UTC
Are you able to reproduce this using only open source software? I see that you are using nVidia's binary-only driver. I understand that this bug is not primarily about graphic drivers, but unfortunately it is quite possible that some other part of whole Xorg suite of software got changed by installation of nvidia. Please refer to https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers and clean your system to the original Fedora state, which we can support. Then, please regenerate and re-attach X server log file (/var/log/Xorg.*.log; don't use any /etc/X11/xorg.conf for this testing) to the bug report. Thanks in advance.
Comment 5
Peter Hutterer
2009-02-09 02:07:09 UTC
(In reply to comment #0)
> [fidepus@FUCKUP ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
> layouts = [de-latin1-nodeadkeys]
> model =
> options = []
What keyboard layout do you want to activate here? I can't find any such layout, neither in the gnome config, nor in xkeyboard-config.
Comment 6
Eric Tanguy
2009-02-26 18:49:46 UTC
Same problem here : $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr-latin9", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us latin9,fr] model = pc105 options = [grp grp:shift_caps_toggle] this problem is since recent updates and if i remember well there a xorg one.
Comment 7
galerien
2009-02-28 09:42:58 UTC
same problem after update : $ xprop -root |grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "latin9", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "fr-latin9", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] model = options = []
Comment 8
Peter Hutterer
2009-03-02 00:16:57 UTC
this seems to be a gnome problem. there's no us-latin9 keyboard, somehow the gconf keys seem to get mixed up. does this happen with a test user?
Comment 9
Julian Sikorski
2009-03-12 22:33:59 UTC
This also happens with freshly installed rawhide: [julas@rawhide ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "pl", "", "" [julas@rawhide ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [pl_PL.UTF-8] options = [] model =
Comment 10
Vinagre
2009-03-13 15:00:15 UTC
Same here, on a fresh rawhide installation, I don't have any xorg.conf Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10600000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd ---------------------------------------------------- $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "pt", "", "" --------------------------------------------------------- $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [en_US.UTF-8] options = [] model =
Comment 12
Peter Hutterer
2009-03-16 00:10:58 UTC
*** Bug 489408 has been marked as a duplicate of this bug. ***
Comment 13
Eric Paris
2009-03-20 18:57:56 UTC
*** Bug 489054 has been marked as a duplicate of this bug. ***
Comment 14
Ray Strode [halfline]
2009-03-20 20:17:36 UTC
Should be fixed with the latest gdm (2.26.0-6.fc11) for *new* users. Existing users will still be hosed. The way to clean it up is sort of gross: su -c "gconftool-2 --config-source=xml:readwrite:/var/lib/gdm/.gconf --unset /apps/gdm/simple-greeter/recent-layouts --direct" rm -f ~/.dmrc gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd Need to figure out if there's a way I can do that automatically.
Comment 15
Andreas Thienemann
2009-04-01 19:30:35 UTC
*** Bug 491439 has been marked as a duplicate of this bug. ***
Comment 16
Andreas Thienemann
2009-04-01 19:39:08 UTC
*** Bug 491759 has been marked as a duplicate of this bug. ***
Comment 17
Andreas Thienemann
2009-04-01 19:47:18 UTC
(In reply to comment #14) > Should be fixed with the latest gdm (2.26.0-6.fc11) for *new* users. Existing > users will still be hosed. Nope. I cannot confirm that it's working for *new* users. gdm-2.26.0-7.fc11.i586 on a fresh rawhide scratch installation. Same message appears on first login. [andreas@workstation ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", "" [andreas@workstation ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [] model = [andreas@workstation ~]$ > The way to clean it up is sort of gross: > > su -c "gconftool-2 --config-source=xml:readwrite:/var/lib/gdm/.gconf --unset > /apps/gdm/simple-greeter/recent-layouts --direct" > rm -f ~/.dmrc > gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd Doesn't fix the problem. The message appears nevertheless as soon as control is passed from gdm to the normal user session.
Comment 18
Andreas Thienemann
2009-04-08 16:11:52 UTC
Still not fixed with rawhide as of 20090408, neither with deleting the kbd configuration for existing users nor for new users.
Comment 19
Peter Hutterer
2009-04-09 05:01:50 UTC
*** Bug 492483 has been marked as a duplicate of this bug. ***
Comment 20
Joachim Backes
2009-04-10 08:33:11 UTC
Having additionally the problem that the nodeadkeys switch does not operate correctly: the handling of "|@[]" on a german nodeadkeys keyboard is correct, but I have to type the tilde character "~" twice and not once.
Comment 21
Andreas Thienemann
2009-04-10 09:13:38 UTC
(In reply to comment #20)
> Having additionally the problem that the nodeadkeys switch does not operate
> correctly: the handling of "|@[]" on a german nodeadkeys keyboard is correct,
> but I have to type the tilde character "~" twice and not once.
Confirmed. Same here.
|@[] are not deadkeys, ~´`^ are.
Comment 22
Joachim Backes
2009-04-10 09:49:53 UTC
You are right ;-) Weird: My keyboard model is "Generic 101-key PC" with USA layout (installed by anaconda as a "german/nodeadkeys" keyboard) , but it functions as it would be a german keyboard (umlauts äöü or s sharp ß are right). But if I switch by System->preferences->keyboard to "Germany Eliminate dead keys" by using the +ADD button in the "Keyboard Preferences" window instead of USA, then AltGr does no more function: getting only + sign instead of ~, or getting no ^ char.
Comment 23
Joachim Backes
2009-04-13 11:00:07 UTC
Got rid from all described problems after updating my system on monday, april 13. Now my keyboard controls: Keyboard model: Generic 101-Keys PC Layout: Only "Germany Eliminate dead keys" added and selected. (No more USA layout needed). The AltGr, tilde (~) and the ^ key now work correctly.
Comment 24
Andreas Thienemann
2009-04-13 13:02:59 UTC
(In reply to comment #23)
> Got rid from all described problems after updating my system on monday, april
> 13.
>
> Now my keyboard controls:
>
> Keyboard model: Generic 101-Keys PC
> Layout: Only "Germany Eliminate dead keys" added and selected. (No more USA
> layout needed).
>
> The AltGr, tilde (~) and the ^ key now work correctly.
Did you set this manually in the configuration tool or was it autodetected?
If you set it manually, it works but can be considered a workaroung. It should be set automatically.
Comment 25
Joachim Backes
2009-04-13 14:10:03 UTC
No, I set it manually (I didn't try a Fc11 re-install).
Comment 26
Matthieu Araman
2009-04-13 23:52:00 UTC
with rawhide updated for today, after applying above command to reset config, still have the same error message.
Comment 27
Robert Nichols
2009-04-14 02:08:53 UTC
To fix the problem for an existing user I had to delete directory ~/.gconf/desktop/gnome/peripherals/keyboard .
Comment 28
Andreas Thienemann
2009-04-18 13:19:54 UTC
Problem is still happening on a new rawhide installation, setting F11Blocker
Comment 29
Joachim Frieben
2009-04-26 12:04:42 UTC
After a fresh install from current "rawhide", I do obtain multiple instances of the "Error activating XKB configuration." error window. During install, I had chosen a keyboard layout "German w/o dead keys" for a German PS/2 keyboard attached to an IBM ThinkPad T23. Furthermore, I get: $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", "terminate:ctrl_alt_bksp" _XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", "" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [] model =
Comment 30
Matthias Clasen
2009-04-28 05:03:12 UTC
Did you select a layout on the login screen ? What does echo $GDM_KEYBOARD_LAYOUT show in this situation ? And what about lshal | grep xkb ?
Comment 31
Need Real Name
2009-04-28 06:20:37 UTC
de_AT.UTF-8 input.xkb.layout = 'us' (string) input.xkb.model = 'evdev' (string) input.xkb.rules = 'base' (string) input.xkb.variant = '' (string) input.xkb.layout = 'us' (string) input.xkb.model = 'evdev' (string) input.xkb.rules = 'base' (string) input.xkb.variant = '' (string) input.xkb.layout = 'de' (string) input.xkb.model = 'pc105' (string) input.xkb.options = 'terminate:ctrl_alt_bksp' (string) input.xkb.rules = 'base' (string) input.xkb.variant = 'nodeadkeys' (string)
Comment 32
Joachim Frieben
2009-04-28 10:58:44 UTC
The issue stops by adding a German keyboard layout by means gnome-keyboard-properties, setting it to be the default one and removing the US layout which was the only one displayed in "Selected Layouts" although the system layout was "German w/o dead keys".
Comment 33
Need Real Name
2009-04-28 16:11:36 UTC
But we can't keep asking people to fix their keyboard layouts. This is what? The third time this has happened? It should just work.
Comment 34
Matthias Clasen
2009-04-28 16:37:50 UTC
To make sure that it just works, you need to help identify what is different in your setup that makes this happen to you, since it does not happen here.
Comment 35
Need Real Name
2009-04-28 17:31:38 UTC
Of course. But as soon as I implement the workaround of reconfiguring my keyboard, you lose that information. So what do you need to know?
Comment 36
Andreas Thienemann
2009-04-28 20:12:17 UTC
Setting the severity to high. There have been several reports of this triggering F11 preview release users on IRC.
Comment 38
Joachim Frieben
2009-04-30 05:07:22 UTC
After updating to gnome-settings-daemon-2.26.1-4.fc11, the issue does not appear for a new user anymore.
Comment 39
Steven Moix
2009-05-01 18:09:17 UTC
I can confirm that, after updating to gnome-settings-daemon-2.26.1-4.fc11, the issue does not appear for a new user anymore (nor does it for old users). I'm using an fr_CH keyboard layout.
Comment 40
Matthias Clasen
2009-05-02 05:44:14 UTC
Ok, I'll take this as sufficient proof that things are fixed.
Comment 41
Peter Hutterer
2009-05-11 00:19:08 UTC
*** Bug 496784 has been marked as a duplicate of this bug. ***
Comment 42
Matthieu Araman
2009-05-11 07:01:48 UTC
I can also confirm that this fixed it on french install + keyboard both for new users and for existing users.
#
13 лет, 10 месяцев назад
Сообщения:
574
Участник с: 21 февраля 2009
Использую GNOME, смена раскладки клавиатуры никак не хочет работать, а при настроке в Параметры Клавиатуры выдает ошибку:
Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10503000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Вот чать моего /etc/X11/xorg.conf
Section “InputDevice”
Identifier “Keyboard0”
Driver “keyboard”
Option “CoreKeyboard”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105”
Option “XkbLayout” “ru,us”
Option “XkbVariant” “,winkeys”
Option “XkbOptions” “grp:alt_shift_toggle,lv3:ralt_switch,grp_led:scroll”
EndSection
вот часть /etc/rc.conf
LOCALE=“ru_RU.UTF-8”
HARDWARECLOCK=“local”
USEDIRECTISA=“no”
TIMEZONE=“Asia/Novosibirsk”
KEYMAP=“ru”
CONSOLEFONT=“/usr/share/kbd/consolefonts/cyr-sun16.psfu.gz”
CONSOLEMAP=
USECOLOR=“yes”
Пробовал в гномовских настройках раскладки клавиатуры восстанавливать значения по умолчанию — не помогает!
Подскажите что делать и куда копать.
xSPiRiTx
#
13 лет, 10 месяцев назад
Сообщения:
574
Участник с: 21 февраля 2009
РЕШЕНО:
просто убрал эту строчку из xorg.conf
Option "XkbVariant" ",winkeys"
Модератор: Модераторы разделов
-
malor
- Сообщения: 335
Gnome: Ошибка активирования параметров XKB
При загрузке в Gnome выскакивает окошко с таким содержанием:
Ошибка активирования параметров XKB.
Она может произойти при следующих обстоятельствах:
— ошибка в библиотеке libxklavier
— ошибка в X-сервере (утилиты xkbcomp, xmodmap)
— X-сервер имеет несовместимую реализацию libxkbfileДанные о версии X-сервера:
The X.Org Foundation
70101000При составлении отчета об ошибке пожалуйста включите:
— Результат xprop -root | grep XKB
— Результат gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Чел сказал, что такое стало появляться после того как он один раз грузанулся вместо Гнома в KDE.
# xprop -root| grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «xorg», «pc105», «us,ru», «,winkeys», «grp:ctrl_shift_toggle,grp_led:scroll»
_XKB_RULES_NAMES(STRING) = «xorg», «pc105», «us,ru(winkeys)», «», «grp:ctrl_shift_toggle,grp_led:scroll»
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
overrideSettings = true
options = []
Несколько ссылок от поисковика:
https://bugzilla.altlinux.org/show_bug.cgi?id=5266
http://lists.altlinux.org/pipermail/sisyph…ril/080191.html
https://bugzilla.altlinux.org/show_bug.cgi?id=9147
-
arachnid
- Модератор
- Сообщения: 1099
- ОС: freeBSD
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
arachnid » 27.03.2007 10:38
malor писал(а): ↑
27.03.2007 08:21
При загрузке в Gnome выскакивает окошко с таким содержанием:
Ошибка активирования параметров XKB.
Она может произойти при следующих обстоятельствах:
— ошибка в библиотеке libxklavier
— ошибка в X-сервере (утилиты xkbcomp, xmodmap)
— X-сервер имеет несовместимую реализацию libxkbfileДанные о версии X-сервера:
The X.Org Foundation
70101000При составлении отчета об ошибке пожалуйста включите:
— Результат xprop -root | grep XKB
— Результат gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbdЧел сказал, что такое стало появляться после того как он один раз грузанулся вместо Гнома в KDE.
# xprop -root| grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = «xorg», «pc105», «us,ru», «,winkeys», «grp:ctrl_shift_toggle,grp_led:scroll»
_XKB_RULES_NAMES(STRING) = «xorg», «pc105», «us,ru(winkeys)», «», «grp:ctrl_shift_toggle,grp_led:scroll»
# gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
overrideSettings = true
options = []Несколько ссылок от поисковика:
https://bugzilla.altlinux.org/show_bug.cgi?id=5266
http://lists.altlinux.org/pipermail/sisyph…ril/080191.html
https://bugzilla.altlinux.org/show_bug.cgi?id=9147
если это вопрос, то подтвержу, что после обновления гнома до 2.18 в оном при использвоании win раскладки стали падать темы (сервер, за оных отвечающий). удалил в xorg.conf русскую виндовую раскладку — полегчало, но менеджер тем продолжает падать при разблокировании экрана
-= freeBSD stable, fluxbox =-
«если ты будешь со мной спорить, я тебя запишу в книжечку!» (с) Ежик
-
malor
- Сообщения: 335
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
malor » 27.03.2007 11:04
Да, вопрос конечно был;) — как избавится от того сообщения? Но падений никаких пока еще замечено не было. Надеюсь не будет.
>>удалил в xorg.conf русскую виндовую раскладку
Какую именно строку?
Что-то поменяли в ‘Option «XkbLayout» «us,ru(winkeys)»»‘?
-
arachnid
- Модератор
- Сообщения: 1099
- ОС: freeBSD
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
arachnid » 27.03.2007 12:15
malor писал(а): ↑
27.03.2007 11:04
Да, вопрос конечно был
>>удалил в xorg.conf русскую виндовую раскладку
Какую именно строку?
Что-то поменяли в ‘Option «XkbLayout» «us,ru(winkeys)»»‘?
убрал winkeys
сейчас обновился, падения пропали, попробовал включить winkeys обранто — ничего не изменилось (в том смысле, что падений нет, но и раскладка невиндовая
-= freeBSD stable, fluxbox =-
«если ты будешь со мной спорить, я тебя запишу в книжечку!» (с) Ежик
-
cherep36
- Сообщения: 128
- Статус: Йа пробудилсо!
- ОС: Arch Linux
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
cherep36 » 03.04.2007 22:44
arachnid писал(а): ↑
27.03.2007 12:15
сейчас обновился, падения пропали, попробовал включить winkeys обранто — ничего не изменилось (в том смысле, что падений нет, но и раскладка невиндовая
чтобы раскладка была виндовая и переключалась нормально, воткни в автозагрузку wm
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleменя тока это и спасает, и не надо никаких kxkb, kkbswitch и т.д.
-
o_serg
- Сообщения: 106
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
o_serg » 05.04.2007 08:44
cherep36 писал(а): ↑
03.04.2007 22:44
чтобы раскладка была виндовая и переключалась нормально, воткни в автозагрузку wm
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleменя тока это и спасает, и не надо никаких kxkb, kkbswitch и т.д.
У меня тоже проблема с xkb.
При вводе
Код: Выделить всё
setxkbmap -option -option grp_led:scroll,grp:ctrl_shift_toggleговорит «Can’t find rule xorg». Что он там не может найти и почему? замучился уже с клавой…
-
cherep36
- Сообщения: 128
- Статус: Йа пробудилсо!
- ОС: Arch Linux
Re: Gnome: Ошибка активирования параметров XKB
Сообщение
cherep36 » 05.04.2007 20:52
o_serg
а в xorg.conf есть такое
Код: Выделить всё
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,ru(winkeys)"
Option "XkbOption" "grp:ctrl_shift_toggle,grp_led:scroll"
Option "XkbRules" "xorg"
EndSection???
Самое главное Option «XkbRules» «xorg», если xfree86 то переключение может и не работать.