Bug 1910784 - Screen auto-rotation not detected when running Wayland
Summary: Screen auto-rotation not detected when running Wayland
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1958433 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-24 16:00 UTC by Matthew Saltzman
Modified: 2024-02-19 19:46 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:17:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME mutter issues 1686 0 None None None 2021-11-05 02:16:31 UTC

Internal Links: 2158105

Description Matthew Saltzman 2020-12-24 16:00:25 UTC
Description of problem:
I have a Lenovo Yoga X1 2nd-generation laptop with Intel graphics. When I log into gnome-shell using Xorg, the screen rotation lock appears in the system menu and rotation works as expected. When I log in using Wayland, the rotation lock does no appear and the screen does not auto-rotate when the computer orientation changes.

Version-Release number of selected component (if applicable):
gnome-shell-3.38.2-4.fc33.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Log into gnome-shell
2. Change computer orientation
3. Check system menu for orientation lock

Actual results:
Screen does not auto-rotate. Rotation lock icon does not appear in system menu.

Expected results:
Screen auto-rotates when laptop orientation changes. Rotation lock is controlled by system menu icon.

Additional info:
Filed here because the symptom shows up here. If it belongs in some other component, I'd be glad to file it there.

Comment 1 hopland 2021-04-05 03:18:58 UTC
Can confirm that auto-rotation is available and functional in 3.38 (Wayland/Xorg) and on GNOME 40 through Xorg on my Lenovo Yoga 520-14IKB, but not in GNOME 40 under wayland. I can't find any input using libinput or evemu that has the SW_TABKET_MODE event switch. So I can't enable auto-rotation.

Comment 2 hopland 2021-04-09 04:41:45 UTC
Simon Sherred (over at the GNOME GitLab) pointed out what the problem was, and I quote:

| This might've been obvious, but I figured I should mention it in case anyone else is waiting for a fix on this: I can confirm that !1710 (merged) (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1710) is the source of the problem. I just rebuilt mutter with this line (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1710/diffs#393a5084c9bfea0ac16e42f878071f2f5aa2d008_1537_1563)reverted to touch_mode = TRUE;, and no other changes, and the issue is fixed on my device. Screen rotation and the OSK work again, and rotation can still be disabled via the top bar.

Comment 3 Robin Lee 2021-04-25 08:11:24 UTC
I met the same issue with Lenovo ThinkBook 14s Yoga. Auto-rotation works on Plasma Workspace but not on GNOME Shell.

gnome-shell-40.0-3.fc34.x86_64
mutter-40.0-5.fc34.x86_64

Comment 4 Robin Lee 2021-04-26 14:48:42 UTC
(In reply to hopland from comment #2)
> Simon Sherred (over at the GNOME GitLab) pointed out what the problem was,
> and I quote:
> 
> | This might've been obvious, but I figured I should mention it in case
> anyone else is waiting for a fix on this: I can confirm that !1710 (merged)
> (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1710) is the source
> of the problem. I just rebuilt mutter with this line
> (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1710/
> diffs#393a5084c9bfea0ac16e42f878071f2f5aa2d008_1537_1563)reverted to
> touch_mode = TRUE;, and no other changes, and the issue is fixed on my
> device. Screen rotation and the OSK work again, and rotation can still be
> disabled via the top bar.

Confirmed this workaround.

Comment 5 Luya Tshimbalanga 2021-05-09 17:39:17 UTC
*** Bug 1958433 has been marked as a duplicate of this bug. ***

Comment 6 Alexander Y. Dmitriev 2021-07-31 15:01:32 UTC
Confirm, does not work on Lenovo Yoga L13.
Doesn't work in Wayland. Also doesn't work in Xorg session

gnome-shell-40.3-1.fc34.x86_64
mutter-40.3-1.fc34.x86_64

Comment 7 Jonas Ådahl 2021-07-31 17:27:29 UTC
If on F34, try donwgrading iio-sensor-proxy.

Comment 8 Alexander Y. Dmitriev 2021-07-31 19:39:09 UTC
> If on F34, try donwgrading iio-sensor-proxy.

Yes, rolling back to the previous version helped. Screen rotation works. Suitable as a temporary solution


iio-sensor-proxy-3.0-3.fc34.x86_64

Comment 9 Jonas Ådahl 2021-07-31 20:07:36 UTC
What you're experiencing then is https://bugzilla.redhat.com/show_bug.cgi?id=1978419

Comment 10 Matthew Saltzman 2021-08-06 13:04:42 UTC
Neither this update nor downgrading iio-sensor-proxy solved the problem with Wayland screen rotation on my Yoga X1 2nd-gen. Rotation in Xorg works fine.

iio-sensor-proxy-3.1-1.fc34.x86_64
mutter-40.3-1.fc34.x86_64
gnome-shell-40.3-1.fc34.x86_64

Comment 11 Luya Tshimbalanga 2021-08-07 18:27:44 UTC
Current workaround: https://extensions.gnome.org/extension/4191/screen-autorotate/

Comment 12 Ben Cotton 2021-11-04 13:48:37 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Ben Cotton 2021-11-04 14:18:00 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Ben Cotton 2021-11-04 15:15:41 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Luya Tshimbalanga 2021-11-05 02:16:32 UTC
Changing the release 35 and adding link to upstream bug report due to a change of codes since mutter 40 beta.

Comment 16 Luya Tshimbalanga 2021-11-05 02:23:29 UTC
As explained on upstream bug report, the issue is the upstream changes for the screen auto-rotation impacts the touchpad on majority of 2-in-1 laptops.
See https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1846 and https://gitlab.gnome.org/GNOME/mutter/-/issues/1686#note_1271723.

Comment 17 Ben Cotton 2022-11-29 16:51:08 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 18 Ben Cotton 2022-12-13 15:17:00 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 19 Ben Cotton 2023-02-07 15:09:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 20 Luya Tshimbalanga 2024-02-19 19:46:32 UTC
Updated status as the issue still occurs on all version of mutter since 40 beta.


Note You need to log in before you can comment on or make changes to this bug.