[Lenovo ThinkPad X1 Yoga 4th] Computer stuck when screen touched with touchpen

[Jesko]

I have a Lenovo Thinkpad X1 Yoga 4th Gen. My OS version is 20.04.

My touchscreen works fine, but when I use my pen the entire OS freezes and even any sound that plays repeats in a loop that is maybe half a second long. The only way I found to get out of this is to force shutdown. I can reproduce this on my laptop without fail. And it is independent of any program I have open.

This problem started around 17th March (I don't remember exactly) and update almost every day.

Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
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
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2020-05-09 (317 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20QFS10B00
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Tags: focal ubuntu
Uname: Linux 5.8.0-45-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: 01/14/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET60W (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QFS10B00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: dmi:bvnLENOVO:bvrN2HET60W(1.43):bd01/14/2021:br1.43:efr1.22:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QFS10B00
dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1920749/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Jesko (jeskowastaken)]

xorg version: 1:7.7+19ubuntu14

[Daniel van Vugt (vanvugt)]

Next time the problem happens, please:

1. Reboot.

2. Run these commands in a Terminal:

   journalctl -b-1 > prevboot.txt
   apport-collect 1920749

3. Attach the resulting text file here.

4. Follow these steps to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

apport information

[Jesko (jeskowastaken)]

result of journalctl -b-1

[Jesko (jeskowastaken)]

There are no crashes in /var/crash and all whoopsies are unrelated (they are older than the probelm)

[Daniel van Vugt (vanvugt)]

Since you say the problem started mid-March I wonder if it's a regression in kernel 5.8.0-45.51.

Are you able to boot an older kernel? Please also try some other versions from:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

[AaronMa (mapengyu)]

Probably duplicated to 1920785.