Ошибка при активации конфигурации xkb parrot os

Parrot Community

Loading

 * 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», «»

Screenshot from 2020-08-26 19-24-19

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», «»

Screenshot from 2020-08-26 19-24-19

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.

Кратко: выполните

Код: Выделить всё

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… :angry:

В процессах поиска определения раскладки 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"

:pray:

После перезагрузки X’ов проблема исчезла. :yahoo: :victory:

Дополнительные поиски в интернете (с уточнённым запросом) принесли две полезных ссылки:

  • 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.

 * 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», «»

Screenshot from 2020-08-26 19-24-19

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», «»

Screenshot from 2020-08-26 19-24-19

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.

Уголок новичка

   3610

При активации конфигурации ХКВ возникла ошибка :(

Это может возникнуть по разным причинам.
Если вы будете описывать данную ситуацию в отчете об ошибках, включите
xprop -root grep XKB
gsettings get org. gnome. libgnomekbd. keyboard model
gsettings get org. gnome. libgnomekbd. keyboard layouts
gsettings get org. gnome. libgnomekbd. keyboard options
xprop -root grep XKB
grep:  no such atom on any window.
XKB:  no such atom on any window.

Help, pls!

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.

#
14 лет назад

Сообщения:

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

#
14 лет назад

Сообщения:

574

Участник с: 21 февраля 2009

РЕШЕНО:
просто убрал эту строчку из xorg.conf

Option "XkbVariant" ",winkeys"


Description


Bernhard Schuster


2009-04-25 14:42:37 UTC

Description of problem:


Version-Release number of selected component (if applicable):
Rawhide / 11beta / 10.92

Dialog says:

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


How reproducible:


Steps to Reproduce:
1. Install Fedora beta
2. First login complete
3. Wait
  
Actual results:


Expected results:
No error pop up

Additional info:

 xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "nodeadkeys", ""
_XKB_RULES_NAMES(STRING) = "evdev", "evdev", "de", "", ""

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 options = []


Comment 1


Matěj Cepl


2009-04-26 09:45:04 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 5


Peter Hutterer


2009-04-28 02:26:54 UTC

please attach your /etc/sysconfig/keyboard too.


Comment 7


Bernhard Schuster


2009-04-28 06:19:06 UTC

Note: I got over that se linux blocked something regarding ck-get-x11-serv (2 times)


SELinux is preventing ck-get-x11-serv (consolekit_t) "search" xdm_var_run_t.

Detaillierte Beschreibung:

SELinux denied access requested by ck-get-x11-serv. It is not expected that this
access is required by ck-get-x11-serv and this access may signal an intrusion
attempt. It is also possible that the specific version or configuration of the
application is causing it to require additional access.

Allow access:

You can generate a local policy module to allow this access - see FAQ
(http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Or you can disable
SELinux protection altogether. Disabling SELinux protection is not recommended.
Please file a bug report (http://bugzilla.redhat.com/bugzilla/enter_bug.cgi)
against this package.

Additional Information:

Quellkontext                  system_u:system_r:consolekit_t:s0-s0:c0.c1023
Zielkontext                   system_u:object_r:xdm_var_run_t:s0
Zielobjekte                   gdm [ dir ]
Quelle                        ck-get-x11-serv
Quellen-Pfad                  /usr/libexec/ck-get-x11-server-pid
Port                          <Unbekannt>
Host                          betabot.localdomain
Quellen-RPM-Pakete            ConsoleKit-x11-0.3.0-8.fc11
Ziel-RPM-Pakete               
RPM-Richtlinie                selinux-policy-3.6.12-9.fc11
SELinux aktiviert             True
Richtlinienversion            targeted
MLS aktiviert                 True
Enforcing-Modus               Enforcing
Plugin-Name                   catchall
Hostname                      betabot.localdomain
Plattform                     Linux betabot.localdomain 2.6.29.1-102.fc11.x86_64
                              #1 SMP Mon Apr 20 15:33:38 EDT 2009 x86_64 x86_64
Anzahl der Alarme             4
Zuerst gesehen                Sa 25 Apr 2009 19:33:35 CEST
Zuletzt gesehen               Di 28 Apr 2009 08:10:11 CEST
Lokale ID                     54677e4f-e622-43d2-9cea-0cc677a3c8e6
Zeilennummern                 

Raw-Audit-Meldungen           

node=betabot.localdomain type=AVC msg=audit(1240899011.421:18): avc:  denied  { search } for  pid=2499 comm="ck-get-x11-serv" name="gdm" dev=sda2 ino=163149 scontext=system_u:system_r:consolekit_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_run_t:s0 tclass=dir

node=betabot.localdomain type=SYSCALL msg=audit(1240899011.421:18): arch=c000003e syscall=21 success=no exit=-13 a0=7fff3ac36fab a1=4 a2=0 a3=7fff3ac35673 items=0 ppid=2496 pid=2499 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ck-get-x11-serv" exe="/usr/libexec/ck-get-x11-server-pid" subj=system_u:system_r:consolekit_t:s0-s0:c0.c1023 key=(null)


Comment 8


Dennis Jacobfeuerborn


2009-04-28 21:45:30 UTC

I saw the same error when running the beta and I just encountered it again after making a fresh install of the f11 preview release.


Comment 10


Alexandr Kara


2009-06-14 10:14:29 UTC

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.


Comment 11


Matěj Cepl


2009-11-05 18:27:33 UTC

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.]


Comment 12


Matěj Cepl


2010-02-26 12:25:39 UTC

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]


Comment 13


Bernhard Schuster


2010-02-26 13:25:51 UTC

There is some easy fix, using the UI and reselct the keyboard layout. This fixed it for me and it never popped up again (Fedora 11 and 12, though I atm can't remember if F12 had it all).


Comment 15


darkside720


2010-07-13 14:40:25 UTC

I am also getting the same error when attempting to launch a VNC session with the same error message. When attempting to grab the following, I get no response.

 xprop -root | grep XKB

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd


Here my xorg.conf file:

more xorg.conf

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# RgbPath is the location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
        RgbPath      "/usr/X11R6/lib/X11/rgb"
        FontPath     "unix/:7100"
EndSection.
Section "Module"
        Load  "dbe"
        Load  "extmod"
        Load  "fbdevhw"
        Load  "glx"
        Load  "record"
        Load  "freetype"
        Load  "type1"
        Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#       Option  "Xleds"         "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#       Option  "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#       Option  "XkbModel"      "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#       Option  "XkbModel"      "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#       Option  "XkbLayout"     "de"
# or:
#       Option  "XkbLayout"     "de"
#       Option  "XkbVariant"    "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#       Option  "XkbOptions"    "ctrl:swapcaps"
# Or if you just want both to be control, use:
#       Option  "XkbOptions"    "ctrl:nocaps"
#
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
        Option      "XkbRules" "xorg"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Unprobed Monitor"
        HorizSync    31.5 - 37.9
        VertRefresh  50.0 - 61.0
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "ati"
        VendorName  "Videocard vendor"
        BoardName   "ATI ES1000"
EndSection
Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "800x600" "640x480"
        EndSubSection
EndSection

Section "DRI"
        Group        0
        Mode         0666
EndSection


Comment 16


darkside720


2010-07-13 16:02:07 UTC

I am also getting the same error when attempting to launch a VNC session with the same error message. When attempting to grab the following, I get no response.

 xprop -root | grep XKB

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd


Here my xorg.conf file:

more xorg.conf

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# RgbPath is the location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
        RgbPath      "/usr/X11R6/lib/X11/rgb"
        FontPath     "unix/:7100"
EndSection.
Section "Module"
        Load  "dbe"
        Load  "extmod"
        Load  "fbdevhw"
        Load  "glx"
        Load  "record"
        Load  "freetype"
        Load  "type1"
        Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#       Option  "Xleds"         "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#       Option  "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#       Option  "XkbModel"      "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#       Option  "XkbModel"      "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#       Option  "XkbLayout"     "de"
# or:
#       Option  "XkbLayout"     "de"
#       Option  "XkbVariant"    "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#       Option  "XkbOptions"    "ctrl:swapcaps"
# Or if you just want both to be control, use:
#       Option  "XkbOptions"    "ctrl:nocaps"
#
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
        Option      "XkbRules" "xorg"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Unprobed Monitor"
        HorizSync    31.5 - 37.9
        VertRefresh  50.0 - 61.0
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "ati"
        VendorName  "Videocard vendor"
        BoardName   "ATI ES1000"
EndSection
Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "800x600" "640x480"
        EndSubSection
EndSection

Section "DRI"
        Group        0
        Mode         0666
EndSection

 * 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», «»

Screenshot from 2020-08-26 19-24-19

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.

#
14 лет, 2 месяца назад

Сообщения:

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

#
14 лет, 2 месяца назад

Сообщения:

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», «»

Screenshot from 2020-08-26 19-24-19

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», «»

Screenshot from 2020-08-26 19-24-19

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.

Уголок новичка

   3799

При активации конфигурации ХКВ возникла ошибка :(

Это может возникнуть по разным причинам.
Если вы будете описывать данную ситуацию в отчете об ошибках, включите
xprop -root grep XKB
gsettings get org. gnome. libgnomekbd. keyboard model
gsettings get org. gnome. libgnomekbd. keyboard layouts
gsettings get org. gnome. libgnomekbd. keyboard options
xprop -root grep XKB
grep:  no such atom on any window.
XKB:  no such atom on any window.

Help, pls!

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.

Понравилась статья? Поделить с друзьями:
  • Ошибка при активации автокада 0015 111
  • Ошибка при активации конфигурации xkb linux mint
  • Ошибка при активации автокад 2015
  • Ошибка при активации кода в гта 5
  • Ошибка при активации word 0xc004c060