Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

Bug #1600371 reported by chives
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as an inductive screen for styluses. When I rest my palm on the screen and then hover my stylus above the screen so that the stylus is recognized and the mouse pointer follows it, and then move the stylus around Gnome seems to freeze for some seconds. The duration of the freeze is proportional to the time the notebook received simultaneous input from the two methods.

"Freeze" means that the screen is not updated. Keyboard inputs that I make during the freeze would be executed after the freezing stops.

I do not need to touch the screen with the stylus for the bug to occur. The bug occurs also when I actually touch the screen with the stylus.

What I expect to happen (and what actually happens in all stylus-supporting tablets, running with Android or Windows) is that the input from the touch screen is rejected as long as the stylus is hovering above the screen.

I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The problem was present in 15.10 as well.

I attach a script as a workaround solution.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: timeshifter 1787 F.... pulseaudio
 /dev/snd/controlC0: timeshifter 1787 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
InstallationDate: Installed on 2016-03-19 (111 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20C0003SFR
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/zsh
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-28-generic N/A
 linux-backports-modules-4.4.0-28-generic N/A
 linux-firmware 1.157.1
Tags: xenial
Uname: Linux 4.4.0-28-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers wireshark
_MarkForUpload: True
dmi.bios.date: 04/29/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: B0ET33WW (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0003SFR
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0003SFR
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

Revision history for this message
chives (mra+ubuntu) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1600371

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
chives (mra+ubuntu) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
chives (mra+ubuntu) wrote : CRDA.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : CurrentDmesg.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : IwConfig.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : JournalErrors.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : Lspci.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : Lsusb.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : ProcInterrupts.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : ProcModules.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : PulseList.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : RfKill.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : UdevDb.txt

apport information

Revision history for this message
chives (mra+ubuntu) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jean-Philippe Bernardy (jeanphilippe-bernardy) wrote :

I could reproduce the bug with v4.7-rc7

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
chives (mra+ubuntu) wrote :

Joseph, as I mentioned the bug was present in 15.10 as well. I could not test it with Ubuntu older than 15.10.

Revision history for this message
Jean-Philippe Bernardy (jeanphilippe-bernardy) wrote :

The bug does not appear with a TWM session nor with a LXDE session. Thus I think that we can safely conclude that this is in fact not a kernel bug.

In my case it occurs only with gnome-shell.

tags: removed: kernel-bug-exists-upstream
affects: linux (Ubuntu) → gnome-shell (Ubuntu)
tags: added: input pen touch
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019

https://ubuntugnome.org/ubuntu-gnome-16-04-lts-is-here/
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/UbuntuGNOME

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Won't Fix
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.