TrackPoint on a X1 tablet not found at boot time, but working after physically reattaching the keyboard

Bug #1878882 reported by gebi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libinput (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

The Trackpoint is not in the found at boot time and is not working.
A simple

sudo libinput list-devices

does not show an entry of a Trackpoint. After removing the keyboard an reattaching it, the trackpoint is listed and working well:

Device: TPPS/2 IBM TrackPoint
Kernel: /dev/input/event20
Group: 12
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *button
Click methods: none
Disable-w-typing: n/a
Accel profiles: flat *adaptive
Rotation: n/a

Any pointers how to enable it a boot time - or are there ways to trigger an event20 to libinput ? Fresh installed ubuntu 20.04 on a X1 tablet gen1.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 515 [17aa:2241]
InstallationDate: Installed on 2020-05-13 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 002: ID 1199:9079 Sierra Wireless, Inc. Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 003: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20GG002AGE
Package: libinput (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=3fa513ec-6869-4d79-9516-a844173054e9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Tags: focal ubuntu
Uname: Linux 5.4.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/13/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1LET87W (1.87 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20GG002AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 32
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1LET87W(1.87):bd12/13/2019:svnLENOVO:pn20GG002AGE:pvrThinkPadX1Tablet:rvnLENOVO:rn20GG002AGE:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:
dmi.product.family: ThinkPad X1 Tablet
dmi.product.name: 20GG002AGE
dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet
dmi.product.version: ThinkPad X1 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 1878882

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xserver-xorg-input-libinput (Ubuntu):
status: New → Incomplete
affects: xserver-xorg-input-libinput (Ubuntu) → libinput (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could also be a kernel issue

Revision history for this message
gebi (gebi) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected focal ubuntu
description: updated
Revision history for this message
gebi (gebi) wrote : DpkgLog.txt

apport information

Revision history for this message
gebi (gebi) wrote : Lspci.txt

apport information

Revision history for this message
gebi (gebi) wrote : Lspci-vt.txt

apport information

Revision history for this message
gebi (gebi) wrote : Lsusb-t.txt

apport information

Revision history for this message
gebi (gebi) wrote : Lsusb-v.txt

apport information

Revision history for this message
gebi (gebi) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
gebi (gebi) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
gebi (gebi) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
gebi (gebi) wrote : ProcEnviron.txt

apport information

Revision history for this message
gebi (gebi) wrote : ProcInterrupts.txt

apport information

Revision history for this message
gebi (gebi) wrote : ProcModules.txt

apport information

Revision history for this message
gebi (gebi) wrote : UdevDb.txt

apport information

Revision history for this message
gebi (gebi) wrote : XorgLog.txt

apport information

Revision history for this message
gebi (gebi) wrote : XorgLogOld.txt

apport information

Revision history for this message
gebi (gebi) wrote : Xrandr.txt

apport information

Revision history for this message
gebi (gebi) wrote : xdpyinfo.txt

apport information

Revision history for this message
gebi (gebi) wrote :

I also tried the mainline 5.6 kernel. This also did not resolve the issue.

maybe related to:

https://bugzilla.kernel.org/show_bug.cgi?id=33292

IMHO: as a reattaching of the keyboard resolves the issue, I guess it has to do with the "boot" order and/or initialization (but I have to admit, that I'm not aware of the detailed internals of the boot process....).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.