Without keyboard in Lenovo V310, suddenly

Ravenman · 2017-12-21 15:15:05

Hi to everyone.

Some time ago, I'm working in KDE and I can not have write nothing (and the lock screen option neither works) suddenly, but the mouse pad continues working.

Checking the log, I found this:

dic 21 09:52:49 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5438, resource id: 62914590, major code: 142 (Unknown), minor code: 3
dic 21 09:52:49 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5437, resource id: 62914576, major code: 142 (Unknown), minor code: 3
dic 21 09:52:49 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5435, resource id: 62914576, major code: 142 (Unknown), minor code: 3
dic 21 09:52:49 archlinux plasmashell[2134]: trying to show an empty dialog
dic 21 09:52:48 archlinux plasmashell[2134]: trying to show an empty dialog
dic 21 09:52:48 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5146, resource id: 62914576, major code: 142 (Unknown), minor code: 3
dic 21 09:52:48 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5145, resource id: 58720272, major code: 142 (Unknown), minor code: 3
dic 21 09:52:48 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5144, resource id: 58720272, major code: 142 (Unknown), minor code: 3
dic 21 09:52:48 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5143, resource id: 58720272, major code: 142 (Unknown), minor code: 3
dic 21 09:52:46 archlinux plasmashell[2134]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5079, resource id: 60817414, major code: 142 (Unknown), minor code: 3

Somebody can help me, please?

jasonwryan · 2017-12-21 17:12:50

Does it work in the console? What changed? Packages? Versions? Settings?

Moving to NC...

Ravenman · 2017-12-21 17:50:27

jasonwryan wrote:

Does it work in the console? What changed? Packages? Versions? Settings?

It does not work in Konsole, any program on KDE or KDE itself ... I can not to say about the Arch Linux console because I can not change to it from KDE.

Changes: only updatings ... these behavior begun two or three updatings before.

Packages: KDE 17.12

jasonwryan wrote:

Moving to NC...

I do not think it's something to be in NC, since it affects a specific laptop model (I have another laptop and everything works fine).

jasonwryan · 2017-12-21 18:06:22

It was moved to NC because you hadn't done any debugging yourself.

You can get to the console by changing the systemd target.

Ravenman · 2017-12-26 16:18:11

jasonwryan wrote:

It was moved to NC because you hadn't done any debugging yourself.

I did put here log information. Anyone know where I can get more information?

You can get to the console by changing the systemd target.

I have changed to system console and everything works fine. The problem is only in KDE looks like.

I found this in log:

dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13072, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13071, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13069, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13068, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13067, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13066, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:14 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13065, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux plasmashell[2292]: QXcbConnection: XCB error: 2 (BadValue), sequence: 51123, resource id: 52428805, major code: 142 (Unknown), minor code: 3
dic 26 10:54:09 archlinux plasmashell[2292]: QXcbConnection: XCB error: 2 (BadValue), sequence: 51122, resource id: 50331653, major code: 142 (Unknown), minor code: 3
dic 26 10:54:09 archlinux plasmashell[2292]: QXcbConnection: XCB error: 2 (BadValue), sequence: 51121, resource id: 50331653, major code: 142 (Unknown), minor code: 3
dic 26 10:54:09 archlinux plasmashell[2292]: QXcbConnection: XCB error: 2 (BadValue), sequence: 51120, resource id: 50331653, major code: 142 (Unknown), minor code: 3
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11379, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11378, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11377, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11376, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11375, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11374, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11373, resource id: 0, major code: 14 (GetGeometry), minor code: 0
dic 26 10:54:09 archlinux kwin_x11[2289]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 11372, resource id: 0, major code: 14 (GetGeometry), minor code: 0

robg · 2017-12-26 18:43:11

Please answer jasonwryan's other questions, i.e., did you start experiencing this behavior after an upgrade? If so, please post the corresponding pacman log. Did you change any settings? If yes, what _exact_ changes did you make? Also, could you please share details of your hardware? For starters, telling us the laptop model and an `lspci` output should suffice.

Ravenman · 2017-12-26 19:25:14

robg wrote:

Please answer jasonwryan's other questions, i.e., did you start experiencing this behavior after an upgrade? If so, please post the corresponding pacman log. Did you change any settings? If yes, what _exact_ changes did you make? Also, could you please share details of your hardware? For starters, telling us the laptop model and an `lspci` output should suffice.

I have tried give an answer for every question because I need fix this soon (This laptop is from my work and I am losing a lot of time by this issue).

Yes, I did start experiencing this behavior after an upgrade but I do not remember one specific date for take the pacman log.

No, I did not make changes in settings.

The laptop model is Lenovo V310.

[root@archlinux ~]# lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
        Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
        Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
        Subsystem: Lenovo Skylake GT2 [HD Graphics 520]
        Kernel driver in use: i915
        Kernel modules: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
        Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
        Subsystem: Lenovo Sunrise Point-LP Thermal subsystem
        Kernel driver in use: intel_pch_thermal
        Kernel modules: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
        Subsystem: Lenovo Sunrise Point-LP CSME HECI
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
        Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
        Subsystem: Lenovo Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
        Subsystem: Lenovo Sunrise Point-LP PMC
        Kernel driver in use: intel_pmc_core
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)                                                                                                                      
        Subsystem: Lenovo Sunrise Point-LP HD Audio                                                                                                                                             
        Kernel driver in use: snd_hda_intel                                                                                                                                                     
        Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
        Subsystem: Lenovo Sunrise Point-LP SMBus
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
        Kernel driver in use: r8169
        Kernel modules: r8169
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30)
        Subsystem: Lenovo QCA9377 802.11ac Wireless Network Adapter
        Kernel driver in use: ath10k_pci
        Kernel modules: ath10k_pci

Thanks by your interest.

robg · 2017-12-26 20:00:09

Thank you for the information. From this and the output you provided in your first post, it seems reasonable to infer that either an update to xorg or the qt / kde stack lead to your issue. Looking into the update dates of the respective packages, the latter seems more likely. Unfortunately I don't run KDE myself, but someone who does might suggest to you which packages to downgrade to isolate the issue.

seth · 2017-12-26 20:08:46

Check your xinput and the xorg log on whether a keyboard is detected for X11 and which driver it uses.
Since it's likely (iff at all) using xf86-input-libinput, try xf86-input-evdev instead.

Ravenman · 2017-12-27 15:45:40

seth wrote:

Check your xinput and the xorg log on whether a keyboard is detected for X11 and which driver it uses.
Since it's likely (iff at all) using xf86-input-libinput, try xf86-input-evdev instead.

Checking the /var/log/Xorg.0.log file, I found this:

[root@archlinux ~]# cat /var/log/Xorg.0.log | grep keyboard
[    26.230] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    26.453] (II) event4  - (II) Power Button: (II) device is a keyboard
[    26.474] (II) event4  - (II) Power Button: (II) device is a keyboard
[    26.475] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[    26.476] (II) event7  - (II) Video Bus: (II) device is a keyboard
[    26.514] (II) event7  - (II) Video Bus: (II) device is a keyboard
[    26.515] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    26.516] (II) event3  - (II) Power Button: (II) device is a keyboard
[    26.544] (II) event3  - (II) Power Button: (II) device is a keyboard
[    26.545] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    26.546] (II) event1  - (II) Sleep Button: (II) device is a keyboard
[    26.564] (II) event1  - (II) Sleep Button: (II) device is a keyboard
[    26.566] (**) EasyCamera: EasyCamera: Applying InputClass "libinput keyboard catchall"
[    26.566] (II) event16 - (II) EasyCamera: EasyCamera: (II) device is a keyboard
[    26.608] (II) event16 - (II) EasyCamera: EasyCamera: (II) device is a keyboard
[    26.609] (**) Ideapad extra buttons: Applying InputClass "libinput keyboard catchall"
[    26.610] (II) event6  - (II) Ideapad extra buttons: (II) device is a keyboard
[    26.668] (II) event6  - (II) Ideapad extra buttons: (II) device is a keyboard
[    26.672] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[    26.672] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[    26.672] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    26.672] (**) AT Translated Set 2 keyboard: always reports core events
[    26.673] (II) event0  - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[    26.673] (II) event0  - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[    26.673] (II) event0  - (II) AT Translated Set 2 keyboard: (II) device removed
[    26.696] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[    26.698] (II) event0  - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[    26.698] (II) event0  - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[  4752.161] (II) event0  - (II) AT Translated Set 2 keyboard: (II) device removed

The last line records the time when the keyboard stopped working.

Should I change the same way to xf86-input-evdev?

Thanks by your interest, patience and help.

seth · 2017-12-27 16:02:13

So the keyboard works for about 80 minutes and then suddenly disappears?
Is there corresponding output in dmesg (to indicate the HW loss/re-add)?
Do you operate the notbook on battery or on AC?
Any power saving mechnisms in place? (laptop-mode-tools, tlp? also disable powerdevil)

Ravenman · 2017-12-27 17:38:29

seth wrote:

So the keyboard works for about 80 minutes and then suddenly disappears?

Yes, so it is. But sometimes the keyboard disappears at few minutes from I am logged.

seth wrote:

Is there corresponding output in dmesg (to indicate the HW loss/re-add)?

No, I did not see nothing weird there.

seth wrote:

Do you operate the notbook on battery or on AC?

I do operate it sometimes with battery and sometimes with AC. No difference.

seth wrote:

Any power saving mechnisms in place? (laptop-mode-tools, tlp? also disable powerdevil)

No, I do not have nothing about it.

Thanks by your interest, patience and help.

seth · 2017-12-27 18:15:03

Time to try evdev to rule out a libinput bug.

Since this seems a delayed effect, how sure can we be about

I have changed to system console and everything works fine.

?

Ravenman · 2017-12-27 18:53:35

seth wrote:

Time to try evdev to rule out a libinput bug.

I will try it and I will share it.

seth wrote:

Since this seems a delayed effect, how sure can we be about
I have changed to system console and everything works fine.
?

Because, when the keyboard disappeared in KDE, I have changed to one tty (Ctrl + Alt + F2) and the keyboard worked fine.

Thanks by your interest, patience and help.

Arch Linux

#1 2017-12-21 15:15:05

Without keyboard in Lenovo V310, suddenly

#2 2017-12-21 17:12:50

Re: Without keyboard in Lenovo V310, suddenly

#3 2017-12-21 17:50:27

Re: Without keyboard in Lenovo V310, suddenly

#4 2017-12-21 18:06:22

Re: Without keyboard in Lenovo V310, suddenly

#5 2017-12-26 16:18:11

Re: Without keyboard in Lenovo V310, suddenly

#6 2017-12-26 18:43:11

Re: Without keyboard in Lenovo V310, suddenly

#7 2017-12-26 19:25:14

Re: Without keyboard in Lenovo V310, suddenly

#8 2017-12-26 20:00:09

Re: Without keyboard in Lenovo V310, suddenly

#9 2017-12-26 20:08:46

Re: Without keyboard in Lenovo V310, suddenly

#10 2017-12-27 15:45:40

Re: Without keyboard in Lenovo V310, suddenly

#11 2017-12-27 16:02:13

Re: Without keyboard in Lenovo V310, suddenly

#12 2017-12-27 17:38:29

Re: Without keyboard in Lenovo V310, suddenly

#13 2017-12-27 18:15:03

Re: Without keyboard in Lenovo V310, suddenly

#14 2017-12-27 18:53:35

Re: Without keyboard in Lenovo V310, suddenly

Board footer