Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)

Bug #1804804 reported by Christopher M. Rogers
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
iio-sensor-proxy (Ubuntu)
Confirmed
Undecided
Unassigned
libinput (Ubuntu)
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ubuntu 18.10
GNOME Shell 3.30.1
Cinnamon 3.8.8

Hardware: ASUS Transformer Mini.

Also confirmed problematic for Yoga Series tablet/laptop hybrids. (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

Screen rotation works fine, but tablet coords including touch screen and pen coords do not rotate with it.

Gnome gets touch screen rotation correct, but not pen coords
Cinnamon gets touch screen rotation and peen coords wrong

User can correct using convoluted xinput commands like:
xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1

I spoke with Mint devs who said I should file it against iio-sensor-proxy or libinput, which I assume is a better solution that asking various wm developers to fix it individually.

tags: added: libinput
summary: Screen rotation does not rotate all input devices and needs custom user
- commands
+ commands (iio-sensor-proxy or libinput should probably handle this)
summary: Screen rotation does not rotate all input devices and needs custom user
- commands (iio-sensor-proxy or libinput should probably handle this)
+ commands (iio-sensor-proxy or libinput should probably handle this?)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1804804

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
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.20 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.20-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Your full name (wzpdqbty) wrote :

Confirmed in LP: #1807250 and LP: #1792813̈́

Ubuntu kernels >=4.15 are the culprit, does not affect debian 4.18.20

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jason Oliveira (jason.oliveira) wrote : apport information

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ashley 1774 F.... pulseaudio
 /dev/snd/controlC0: ashley 1774 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:73f5 Synaptics, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer One S1003
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=fcaaf731-6ab3-4df3-80a7-52e36a5bc770 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-7-generic N/A
 linux-backports-modules-5.0.0-7-generic N/A
 linux-firmware 1.178
Tags: disco
Uname: Linux 5.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/20/2018
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.19
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: One S1003
dmi.board.vendor: Acer
dmi.board.version: V1.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.19:bd03/20/2018:svnAcer:pnOneS1003:pvrV1.19:rvnAcer:rnOneS1003:rvrV1.19:cvnAcer:ct32:cvrChassisVersion:
dmi.product.family: CHT-CR
dmi.product.name: One S1003
dmi.product.sku: S1003_1025112B_1.19
dmi.product.version: V1.19
dmi.sys.vendor: Acer

Changed in linux (Ubuntu):
status: Expired → New
tags: added: apport-collected disco
Revision history for this message
Jason Oliveira (jason.oliveira) wrote : AlsaInfo.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : CRDA.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : IwConfig.txt

apport information

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1804804

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.

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : Lspci.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : ProcCpuinfo.txt

apport information

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jason Oliveira (jason.oliveira) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : ProcModules.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : PulseList.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : RfKill.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : UdevDb.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jason Oliveira (jason.oliveira) wrote :

Currently experiencing this problem in disco on an Acer One 10 S1003. screen is by default in portrait, which makes using the keyboard attachment a little painful.
For default landscape mode, I manually set:
xinput set-prop 13 "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
and try to keep it in landscape mode by default. It'd be nice if this would automatically change when the screen rotated.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Also experiencing same problem on a Dell Inspiron 3168. Seems as though what should be handled by iio-sensor-proxy is not being handled for the input part of the touchscreen.

Changed in iio-sensor-proxy (Ubuntu):
status: New → Confirmed
Changed in libinput (Ubuntu):
status: New → Confirmed
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.