XF86Keyboard error after kernel update.

Ca5bah · 2018-06-21 01:40:08

Hey guys. Last night I upgraded my Arch system which included the kernel update. Upon reboot X refused to start with this error:

Unsupported high key code 372 for name I372. X11 cannot support keycodes above 255. Could not resolve keysym XF86Keyboard. Errors from xbcomp are not fatal to the X server.

I honestly cannot find a lot of information on this. Does anyone have any ideas?

Askannz · 2018-06-21 01:58:40

Well as it says, this error is not fatal to the X server, so I doubt it's the cause of X not starting. Could you paste the whole log ?

Ca5bah · 2018-06-21 03:26:04

Askannz wrote:

Well as it says, this error is not fatal to the X server, so I doubt it's the cause of X not starting. Could you paste the whole log ?

Here's my log:

https://pastebin.com/hcHgNa9L

jasonwryan · 2018-06-21 03:30:36

X is starting. What is supposed to run in it? Read the logs/journal for that application.

Moving to NC...

Askannz · 2018-06-21 03:36:09

Could we have a look to your Xorg config also ? Those lines bother me :

[    57.543] (EE) Failed to load module "synaptics" (module does not exist, 0)
[    57.543] (EE) No input driver matching `synaptics'

I suspect you are using an outdated configuration.

Ca5bah · 2018-06-21 21:07:47

Askannz wrote:

Could we have a look to your Xorg config also ? Those lines bother me :
[    57.543] (EE) Failed to load module "synaptics" (module does not exist, 0)
[    57.543] (EE) No input driver matching `synaptics'
I suspect you are using an outdated configuration.

Here are all of my x-related configs:

https://pastebin.com/vuiyjGyu - 99-killx.conf

https://pastebin.com/bXbHjRZR - 00-keyboard.conf

https://pastebin.com/Ud6fVtaG - 20-nvidia.conf

https://pastebin.com/up0QnM1P 50-synaptics.conf

Last edited by Ca5bah (2018-06-21 21:30:18)

jasonwryan · 2018-06-21 21:12:09

That synaptics conf is the wrong file...

loqs · 2018-06-21 21:15:19

I would suggest disabling 20-nvidia.conf and 50-synaptics.conf as redundant and remove the Section "InputClass" from 99-killx.conf and use localectl to generate an updated 00-keyboard.conf
however that will not be the cause your issue what is starting the X server and what is the X server supposed to start?

Ca5bah · 2018-06-21 21:30:53

jasonwryan wrote:

That synaptics conf is the wrong file...

Sorry, I must have pasted the wrong link. I fixed it. The commenting out was done by me as an attempt at possibly fixing it, it did nothing.

Ca5bah · 2018-06-21 21:32:45

loqs wrote:

I would suggest disabling 20-nvidia.conf and 50-synaptics.conf as redundant and remove the Section "InputClass" from 99-killx.conf and use localectl to generate an updated 00-keyboard.conf
however that will not be the cause your issue what is starting the X server and what is the X server supposed to start?

I am using LightDM to start Xfce4. Attempting to start X manually does not work as well.

loqs · 2018-06-21 21:53:10

What is the contents of ~/.xinitrc and after disabling all the X .conf files and disabling/stopping lightdm run startx and what output is there if any?
Edit:
Please also post the Xorg.log from the new attempt.

Last edited by loqs (2018-06-21 21:53:36)

Ca5bah · 2018-06-21 23:30:52

loqs wrote:

What is the contents of ~/.xinitrc and after disabling all the X .conf files and disabling/stopping lightdm run startx and what output is there if any?
Edit:
Please also post the Xorg.log from the new attempt.

Here is my xinitrc: https://pastebin.com/6YY7JMNk

And here is my log from the latest attempt: https://pastebin.com/uJNhiTwL

loqs · 2018-06-21 23:44:00

twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login

start twm in background then exit that would explain why startx just returns.

Ca5bah · 2018-06-22 02:44:41

loqs wrote:

twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
start twm in background then exit that would explain why startx just returns.

Could you clarify what you mean please?

seth · 2018-06-22 07:02:12

What is the meaning of the trailing ampersands?
What is the meaning of the leading hashes?
What does the xinitrc script actually do?

As soon as xinit ends, your session ends and the X11 server terminates.

Arch Linux

#1 2018-06-21 01:40:08

XF86Keyboard error after kernel update.

#2 2018-06-21 01:58:40

Re: XF86Keyboard error after kernel update.

#3 2018-06-21 03:26:04

Re: XF86Keyboard error after kernel update.

#4 2018-06-21 03:30:36

Re: XF86Keyboard error after kernel update.

#5 2018-06-21 03:36:09

Re: XF86Keyboard error after kernel update.

#6 2018-06-21 21:07:47

Re: XF86Keyboard error after kernel update.

#7 2018-06-21 21:12:09

Re: XF86Keyboard error after kernel update.

#8 2018-06-21 21:15:19

Re: XF86Keyboard error after kernel update.

#9 2018-06-21 21:30:53

Re: XF86Keyboard error after kernel update.

#10 2018-06-21 21:32:45

Re: XF86Keyboard error after kernel update.

#11 2018-06-21 21:53:10

Re: XF86Keyboard error after kernel update.

#12 2018-06-21 23:30:52

Re: XF86Keyboard error after kernel update.

#13 2018-06-21 23:44:00

Re: XF86Keyboard error after kernel update.

#14 2018-06-22 02:44:41

Re: XF86Keyboard error after kernel update.

#15 2018-06-22 07:02:12

Re: XF86Keyboard error after kernel update.

Board footer