Ubuntu
linux package

LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

Bug #1884288 reported by Ian Hand on 2020-06-19

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 18:03:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller])
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E.G140J.D8.E1.016.bin
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: LapBook Pro
dmi.product.sku: Default string
dmi.product.version: Default string
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.1
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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ian 1619 F.... pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-37-generic N/A
linux-backports-modules-5.4.0-37-generic N/A
linux-firmware 1.187
Tags: focal
Uname: Linux 5.4.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E.G140J.D8.E1.016.bin
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: LapBook Pro
dmi.product.sku: Default string
dmi.product.version: Default string
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ian 1619 F.... pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-37-generic N/A
linux-backports-modules-5.4.0-37-generic N/A
linux-firmware 1.187
Tags: focal
Uname: Linux 5.4.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

See original description

Tags:

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-19:

CurrentDmesg.txt Edit (126.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (23.0 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (91.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.4 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Lsusb-t.txt Edit (388 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (26.1 KiB, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (747 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (328 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (7.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (191.7 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (40.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (40.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (22.6 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (109.1 KiB, text/plain; charset="utf-8")

Ian Hand (ianhand1989) on 2020-06-19

description:

updated

Ubuntu Foundations Team Bug Bot (crichton) on 2020-06-19

affects:

ubuntu → xorg (Ubuntu)

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-06-22: Re: [LapBook Pro] Touchpad sometimes does not work when machine is restarted

Please uninstall 'xserver-xorg-input-synaptics' and then tell us if the problem still happens. If it does then please also:

1. Reboot

2. Run:

journalctl -b0 > journal.txt

and attach the resulting text file here.

summary:	- Touchpad sometimes does not work when machine is restarted + [LapBook Pro] Touchpad sometimes does not work when machine is restarted
affects:	xorg (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status:	New → Incomplete

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-22:

journal.txt Edit (362.5 KiB, text/plain)

I removed 'xserver-xorg-input-synaptics' and upon restart touchpad stopped working again, I am now using an external mouse to navigate as touchpad have completely ceased to work. Please see attached journal.txt

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-06-23:

Please:

1. sudo apt install evtest

2. sudo evtest

and tell us if you see events from the touchpad even when it's not working elsewhere.

affects:

xserver-xorg-input-synaptics (Ubuntu) → linux (Ubuntu)

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-23:

Please see below results of evtest:

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: AT Translated Set 2 keyboard
/dev/input/event3: Intel HID events
/dev/input/event4: Intel HID 5 button array
/dev/input/event5: Video Bus
/dev/input/event6: USB 2.0 Camera: USB Camera
/dev/input/event7: HDA Intel PCH Mic
/dev/input/event8: HDA Intel PCH Headphone
/dev/input/event9: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event10: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event11: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event12: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=10
/dev/input/event14: Logitech USB Optical Mouse

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-06-24:

You need to figure out which is the touchpad, enter that number (I think it's 3 in the above list?) and hit Enter. Then use the touchpad and verify you see lots more information.

You-Sheng Yang (vicamo) on 2020-06-24

tags:

added: hwe-touchpad

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-24:

Unfortunately event 3 is not the touchpad, nor is 4, see below:

EVENT 3:

Input device name: "Intel HID events"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 69 (KEY_NUMLOCK)
    Event code 102 (KEY_HOME)
    Event code 104 (KEY_PAGEUP)
    Event code 107 (KEY_END)
    Event code 109 (KEY_PAGEDOWN)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 142 (KEY_SLEEP)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 166 (KEY_STOPCD)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 240 (KEY_UNKNOWN)
    Event code 247 (KEY_RFKILL)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)

EVENT 4:

Input device name: "Intel HID 5 button array"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 125 (KEY_LEFTMETA)
    Event code 240 (KEY_UNKNOWN)
    Event code 561 (?)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)

The rest do not appear to relate to the touchpad.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-24:

I restarted the laptop again to see if it helps and it is back working. I am not sure if this helps but when I move the touchpad around and pressing the left and right during the startup screen it seems it may help, I am not sure if this is complete nonsense or not.

It is now listed in the evtest:

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: AT Translated Set 2 keyboard
/dev/input/event3: HTIX5288:00 0911:5288 UNKNOWN
/dev/input/event4: HTIX5288:00 0911:5288 Touchpad
/dev/input/event5: HTIX5288:00 0911:5288 UNKNOWN
/dev/input/event6: Intel HID events
/dev/input/event7: Intel HID 5 button array
/dev/input/event8: USB 2.0 Camera: USB Camera
/dev/input/event9: Video Bus
/dev/input/event10: HDA Intel PCH Mic
/dev/input/event11: HDA Intel PCH Headphone
/dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event15: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event16: HDA Intel PCH HDMI/DP,pcm=10

I can confirm event 4 is indeed the touchpad as lots of extra information appears when event 4 is investigated when touchpad is in use.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-24:

I restarted laptop twice without touching touchpad until I get user login screen and worked fine. However, on another reboot, I touched the touchpad several times during the startup screen and it is not working again. I am not sure if this helps in the testing of this. Anyway, it is back to the non-working state, that is not to say that it will start working again with yet another reboot.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-06-25:

#10

Thanks. If the touchpad is randomly missing from 'evtest' then that sounds like a kernel bug or a hardware fault.

Revision history for this message

You-Sheng Yang (vicamo) wrote on 2020-06-25:

#11

Download full text (3.5 KiB)

[ 2786.224] (II) config/udev: Adding input device HTIX5288:00 0911:5288 Touchpad (/dev/input/event5)
[ 2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "libinput touchpad catchall"
[ 2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "touchpad catchall"
[ 2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "Default clickpad buttons"
[ 2786.224] (II) LoadModule: "synaptics"
[ 2786.224] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 2786.225] (II) Module synaptics: vendor="X.Org Foundation"
[ 2786.225] compiled for 1.20.8, module version = 1.9.1
[ 2786.225] Module class: X.Org XInput Driver
[ 2786.225] ABI class: X.Org XInput driver, version 24.1
[ 2786.225] (II) Using input driver 'synaptics' for 'HTIX5288:00 0911:5288 Touchpad'
[ 2786.226] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 31 paused 0
[ 2786.226] (**) HTIX5288:00 0911:5288 Touchpad: always reports core events
[ 2786.226] (**) Option "Device" "/dev/input/event5"
[ 2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: found clickpad property
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: x-axis range 0 - 2628 (res 22)
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: y-axis range 0 - 1332 (res 21)
[ 2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: device does not report pressure, will use touch data.
[ 2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: device does not report finger width.
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: buttons: left double triple
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: Vendor 0x911 Product 0x5288
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: invalid pressure range. defaulting to 0 - 255
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: invalid finger width range. defaulting to 0 - 15
[ 2786.227] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: touchpad found
[ 2786.227] (**) HTIX5288:00 0911:5288 Touchpad: always reports core events
[ 2786.227] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:17.3/i2c_designware.7/i2c-8/i2c-HTIX5288:00/0018:0911:5288.0001/input/input10/event5"
[ 2786.227] (II) XINPUT: Adding extended input device "HTIX5288:00 0911:5288 Touchpad" (type: TOUCHPAD, id 10)
[ 2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[ 2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) MaxSpeed is now 1.75
[ 2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) AccelFactor is now 0.068
[ 2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) keeping acceleration scheme 1
[ 2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration profile 1
[ 2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration factor: 2.000
[ 2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration threshold: 4
[ 2786.228] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: touchpad found
[ 2786.229] (II) config/udev: Adding input device HTIX5288:00 0911:5288 Touchpad (/dev/in...

[  2786.224] (II) config/udev: Adding input device HTIX5288:00 0911:5288 Touchpad (/dev/input/event5)
[  2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "libinput touchpad catchall"
[  2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "touchpad catchall"
[  2786.224] (**) HTIX5288:00 0911:5288 Touchpad: Applying InputClass "Default clickpad buttons"
[  2786.224] (II) LoadModule: "synaptics"
[  2786.224] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[  2786.225] (II) Module synaptics: vendor="X.Org Foundation"
[  2786.225] 	compiled for 1.20.8, module version = 1.9.1
[  2786.225] 	Module class: X.Org XInput Driver
[  2786.225] 	ABI class: X.Org XInput driver, version 24.1
[  2786.225] (II) Using input driver 'synaptics' for 'HTIX5288:00 0911:5288 Touchpad'
[  2786.226] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 31 paused 0
[  2786.226] (**) HTIX5288:00 0911:5288 Touchpad: always reports core events
[  2786.226] (**) Option "Device" "/dev/input/event5"
[  2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: found clickpad property
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: x-axis range 0 - 2628 (res 22)
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: y-axis range 0 - 1332 (res 21)
[  2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: device does not report pressure, will use touch data.
[  2786.227] (II) synaptics: HTIX5288:00 0911:5288 Touchpad: device does not report finger width.
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: buttons: left double triple
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: Vendor 0x911 Product 0x5288
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: invalid pressure range.  defaulting to 0 - 255
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: invalid finger width range.  defaulting to 0 - 15
[  2786.227] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[  2786.227] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: touchpad found
[  2786.227] (**) HTIX5288:00 0911:5288 Touchpad: always reports core events
[  2786.227] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:17.3/i2c_designware.7/i2c-8/i2c-HTIX5288:00/0018:0911:5288.0001/input/input10/event5"
[  2786.227] (II) XINPUT: Adding extended input device "HTIX5288:00 0911:5288 Touchpad" (type: TOUCHPAD, id 10)
[  2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[  2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) MaxSpeed is now 1.75
[  2786.227] (**) synaptics: HTIX5288:00 0911:5288 Touchpad: (accel) AccelFactor is now 0.068
[  2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) keeping acceleration scheme 1
[  2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration profile 1
[  2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration factor: 2.000
[  2786.227] (**) HTIX5288:00 0911:5288 Touchpad: (accel) acceleration threshold: 4
[  2786.228] (--) synaptics: HTIX5288:00 0911:5288 Touchpad: touchpad found
[  2786.229] (II) config/udev: Adding input device HTIX5288:00 0911:5288 Touchpad (/dev/input/mouse0)
[  2786.229] (**) HTIX5288:00 0911:5288 Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"

So it seems to me that these logs were captured when touchpad is working. Could you redo `sudo apport-collect 1884288` when touchpad is dead?

This also duplicates bug 1809586, which has expired, so let's continue investigation here.

Daniel van Vugt (vanvugt) on 2020-06-25

summary:

- [LapBook Pro] Touchpad sometimes does not work when machine is restarted
+ LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine
+ is restarted

Revision history for this message

You-Sheng Yang (vicamo) wrote on 2020-06-25:

#12

One more might be related bug 1810130.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: AlsaInfo.txt

#13

AlsaInfo.txt Edit (40.9 KiB, text/plain)

apport information

tags:	added: apport-collected
description:	updated

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: CRDA.txt

#14

CRDA.txt Edit (3.2 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: CurrentDmesg.txt

#15

CurrentDmesg.txt Edit (112.5 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: IwConfig.txt

#16

IwConfig.txt Edit (504 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lspci.txt

#17

Lspci.txt Edit (31.8 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lspci-vt.txt

#18

Lspci-vt.txt Edit (2.0 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lsusb-t.txt

#19

Lsusb-t.txt Edit (467 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lsusb-v.txt

#20

Lsusb-v.txt Edit (30.9 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcCpuinfo.txt

#21

ProcCpuinfo.txt Edit (4.8 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcCpuinfoMinimal.txt

#22

ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcEnviron.txt

#23

ProcEnviron.txt Edit (306 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcInterrupts.txt

#24

ProcInterrupts.txt Edit (4.3 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcModules.txt

#25

ProcModules.txt Edit (7.8 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: RfKill.txt

#26

RfKill.txt Edit (112 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: UdevDb.txt

#27

UdevDb.txt Edit (192.1 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: WifiSyslog.txt

#28

WifiSyslog.txt Edit (181.6 KiB, text/plain)

apport information

description:

updated

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: AlsaInfo.txt

#29

AlsaInfo.txt Edit (40.9 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: CRDA.txt

#30

CRDA.txt Edit (3.2 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: CurrentDmesg.txt

#31

CurrentDmesg.txt Edit (112.5 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: IwConfig.txt

#32

IwConfig.txt Edit (504 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lspci.txt

#33

Lspci.txt Edit (31.8 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lspci-vt.txt

#34

Lspci-vt.txt Edit (2.0 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lsusb-t.txt

#35

Lsusb-t.txt Edit (467 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: Lsusb-v.txt

#36

Lsusb-v.txt Edit (30.9 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcCpuinfo.txt

#37

ProcCpuinfo.txt Edit (4.8 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcCpuinfoMinimal.txt

#38

ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcEnviron.txt

#39

ProcEnviron.txt Edit (306 bytes, text/plain)

apport information

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-06-25: ProcInterrupts.txt

#40

ProcInterrupts.txt Edit (4.3 KiB, text/plain)

apport information

You-Sheng Yang (vicamo) on 2020-06-25

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Califa101 (rafacalifa101) on 2020-06-30

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
status:	Incomplete → Confirmed

You-Sheng Yang (vicamo) on 2020-07-03

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

66 comments hidden

view all 146 comments

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-04:

#107

that's with the 5.4 based kernel.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-06:

#108

IMG_20200706_184801.jpg Edit (4.4 MiB, image/jpeg)

@Kai-Heng, please see attached a more details relating to machine hanging on restart, this was where I removed "quiet" in the grub to display messages.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-07:

#109

Thanks. Please test this one instead:
https://people.canonical.com/~khfeng/lp1884288-3/

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-07:

#110

@Kai-Heng, both power off and restart are now working with that latest 5.4 kernel you asked me to test.

error: can't find command 'hwmatch' still appears at the powering on screen but I am not sure if this is important to the larger scheme of things.

So far so good with the touchpad working both after a cold reboot and restart.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-07:

#111

Great, let's try it a day more or two.
I'll send the patch upstream once we are certain it's working.

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-07:

#112

@ Kai-Heng, that patch you say is to put it on for a next official update?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-07:

#113

Not that soon. First, we need to be certain it fixes the issue. Then I'll send the patch to upstream kernel, and after that we can backport the patch to Ubuntu's kernel.

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-07:

#114

And how long would we be talking about?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-08:

#115

Can't say for sure. Please use the kernel I compiled for now.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#116

@Kai-Heng, unfortunately after a cold boot this afternoon the touchpad is not working again. The machine was off for the best part of 15 hours.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-08:

#117

"Not working" right after boot? If it stops working in the middle of usage, it's a different bug.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#118

Not working directly after boot, this was always the issue, never in the middle of usage.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#119

It's an all or nothing bug for my machine, if it doesn't work directly after boot it will never spontaneously start working again in the middle of a session.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#120

Likewise when it is working, it will never spontaneously stop working in the middle of a session.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-08:

#121

Hmm. Ok. Then my patch doesn't work.

Does a reboot from Windows to Linux always work?

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#122

I stripped my machine of Windows in favour of Ubuntu without a partition, unfortunately I could not foresee this problem with the touchpad.

@Califa may be able to answer your question as I think they still have Windows on their machine.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#123

Tour kernel does seem to dramatically lower the chances of the touchpad not working upon reboot if that makes any sense. The newer Ubuntu kernel is very hit nad miss with the touchpad after reboot.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#124

Apologies, I meant Your

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-08:

#125

As I said earlier, when I start the laptop from scratch with Ubuntu for the first time, sometimes the touchpad works. Instead, when it never works is when I reboot.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#126

@Califa, yes, the same as me, but when you boot Windows the touchpad works every time, yes?

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#127

The holy grail here is obviously trying to crack what Windows is doing in the background that has the touchpad working perfectly every time.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#128

@Kai-Heng, are there other potential workarounds that may help with this? If you need any additional logs from me please don't hesitate to ask.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-08:

#129

UPDATE:

OK, so routing around some more articles about similar problems, I found this:

https://askubuntu.com/questions/1041820/touchpad-not-working-on-ubuntu-18-04

The first answer in the article gives me a partial solution where I can get the touchpad back working again mid-session:

sudo rmmod i2c_hid
sudo modprobe i2c_hid

However, their suggestion to update the GRUB with GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash" does not improve the bug at boot, in fact to makes it worse where the touchpad is dead upon every reboot I have tested over the last 20 minutes.

Note: I am still upsing @Kai-Heng's latest 5.4 kernel.

Hopefully this information might add something to the next step in discovering a solution.

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-09:

#130

@Ian, Yes, yes, when I log in to Windows, I never have problems with the touchpad, all the time the session in Windows lasts, the touchpad works perfectly, without any problem.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-09:

#131

My last attempt, I am out of ideas to try:
https://people.canonical.com/~khfeng/lp1884288+last/

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-09:

#132

@Kai-Heng, unfortunately that latest kernel you compiled has not solved it, touchpad is dead with both a cold boot and restart.

Is there a way of running the following:

sudo rmmod i2c_hid
sudo modprobe i2c_hid

automatically at boot?

Apologies if this is what you were trying to do all this time. Running those two lines of code in the terminal is the closest thing I have to a fix once I'm logged in... if it could somehow be ran beofre log in at boot then surely that would solve it? Maybe I am over simplifying the situation.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-09:

#133

Systemd oneshot service is a good way to achieve this.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-09:

#134

@Kai-Heng, thanks. Just so I don't go and make a mistake along the way, could you please forward me on a tutorial/blog page that gives a step by step on how to set up Systemd oneshot. Thank you.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-09:

#135

For me I always use the manpage:
https://www.freedesktop.org/software/systemd/man/systemd.service.html

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-09:

#136

@Kai-Heng, thanks, much appreciated. I will configure this evening will let you know how it goes.

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-09:

#137

Why don't you use Windows until a definitive solution for Ubuntu comes out and you get out of trouble?

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-09:

#138

@Califa, I left Windows behind a long time ago, I only use it at work now due to it being on my work machine. It is a personal preference for me to use Ubuntu. Yes, I could easily go back to Windows but I will not. As I said before, I am not absolutely stuck as I have an external mouse. I would rather contribute to the Open Source project that is Ubuntu by means of trying to fix this bug than go back to Windows.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-09:

#139

There won't be any "definitive solution" until Chuwi can push Hantick to take a look on this issue.

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-09:

#140

I understand you, @Ian, but you will have the problem when you have to use the laptop without being able to support the mouse ...

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-09:

#141

Okay. I have bad news to give you. I definitely think I'm going to return the laptop. Today I have been using the touchpad in Windows for a long time (I use the laptop almost always without a mouse) and it has several faults, although it does not always do them: the cursor does not stop where I want it to stop and also, in the Upon release, it makes a slight displacement in any direction.
It is a pity that, otherwise, this laptop is very good value for money.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-09:

#142

@Califa, I am sorry to hear for you bad experience.

@Kai-Heng, OK so I don't think I have the proper know-how to successfully set up the systemd oneshot service. However, the best solution I currently have set up is a keyboard shortcut that runs a bash script that resets the touchpad on demand whenever it may fail again in the future.

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-12:

#143

@Kai-Heng, given the amount of investigation and testing we have put into this, should we mark this bug as confirmed or is it still technically incomplete?

Kai-Heng Feng (kaihengfeng) on 2020-07-12

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Califa101 (rafacalifa101) wrote on 2020-07-12:

#144

@Kai-Heng, you who have much more experience in these issues about bugs and errors, would this error have a solution?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2020-07-12:

#145

Please see comment #139...

Revision history for this message

Ian Hand (ianhand1989) wrote on 2020-07-12:

#146

touchpad_reset.sh Edit (63 bytes, text/x-sh)

As a workaround, I am happy to share my bash script that can be ran using a keyboard shortcut whenever the touchpad may act up (have to log in first), please see attached. To assign it to a keyboard shortcut, go to Settings > Keyboard Shortcuts > scroll down to the end of the shortcuts and add a new shortcut and type in the following as the command:

pkexec /"path to script"/touchpad_reset.sh

and make sure script is executable, see https://askubuntu.com/questions/229589/how-to-make-a-file-e-g-a-sh-script-executable-so-it-can-be-run-from-a-termi