Auto-rotate is not working properly when system is booted up while not in its regular orientation

Grace,

 Thanks for your report. I could reproduce this issue.
 And I found the screen position is right, I could open the Nautilus, click the top-right corner to active the menu, but the display is invert. It should be a bug. I need spend more time on it.

Status changed to 'Confirmed' because the bug affects multiple users.

I did more debug. I found in the GNOME desktop the dbus message is correct.

When I boot up from bottom-up mode, the value of net.hadess.SensorPorxy.AccelerometerOrientation is "bottom-up", after that, I change to normal mode, I found the value is "normal". But the screen is totally revert.

I tried to use xrandr to rotate the screen.
$ xrandr --output eDP-1 --rotate inverted

Although the screen show correctly, but I found the mouse and touch screen is still keep inverted.

I thought this issue is not related to kernel, cause we could got correct value from AccelerometerProxy, I doubt the gnome-shell could handle it correctly.

Thanks!

I doubt the gnome-shell couldn't handle it correctly. :)

It's a generic bug, I reproduced it on 18.04.3 with 5.0.0-32 kernel.

Hi Bin Li,

Thanks for the updates. Could you specify a target date for the bug fix?

Thank you!

Grace,

I tried the latest gnome-shell 3.34.1 on 5.2.0 kernel, this issue is fixed. So I thought the upstream already met this issue before.

I will need more time to find the root cause and patches.

It's a little hard to have a target date for me to resolve this issue, it also depends the people from the ubuntu desktop team, I will do my best and hope find related patches at this week.

Thanks!

Hi Bin,

Ok, I'll take note of this. Thank you very much!

Today I tried the gnome-shell 3.30 and mutter 3.30, I could reproduce this issue. And the mutter did handle the display things, so it should be related to mutter.

It's a similar issue in below link, it says 3.32.1 don't have below issue. I will verify it.

https://gitlab.gnome.org/GNOME/mutter/issues/514

The code changed a lot from 3.28 to 3.32, I need more time to debug it.

Hi Bin,

Can I please get an update on the status of this bug?

Thank you very much.

@Grace,

 We discussed with PM, this issue is lower priority, we will report a upstream bug for it first.
 I also tried to read the source code and structure of mutter, need more time to debug it.
 Thanks!

Hi Bin,

Thanks for the update! This is noted.

I reported a upstream bug.

https://gitlab.gnome.org/GNOME/mutter/issues/954

Hi Bin,

I read in the issue's comment that it may not be related to mutter. Does this mean the bug is not affected by Gnome Shell? Or is this still subject for further checking?

Grace,

 Might be gnome-shell, but I prefer to the mutter, we need further checking. Thanks!

I debugged it, found that by default it will use gdm-wayland-session in greeter UI.

/usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart

After login the system, it will use the gdm-x-session, so this might be the root cause.

When I try to disable Wayland in gdm3, this issue is fixed, because it will use gdm-x-session all the time.

cat /etc/gdm3/daemon.conf
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

Hi Bin,

Thanks for your update. Will you be forwarding this bug to the people concerned with gdm to find a permanent fix?

Copy the comment from mutter bug.

I debugged it, found that by default it will use gdm-wayland-session in greeter UI.
/usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart
After login the system, it will change to use the gdm-x-session, so this might be the root cause.
When I try to disable Wayland in gdm3, this issue is fixed, because it will use gdm-x-session all the time. So it might be a gdm3 issue.
cat /etc/gdm3/daemon.conf
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

Hi Jason,

Will you be forwarding this bug to the people concerned with gdm to find a permanent fix? Or should we simply apply the given debug methods on our system?

Additionally, will there be any affected drivers, or is this simply related to the greeter UI?

@grace,

 This is not a real fix, so we couldn't just disable it in upstream, it's just a workaround. Thanks!

@Bin,

I see. I'll just await for further updates on this then. Thank you very much!

Bug has also been observed in 18.04.04 LTS, 19.10 and 20.04 (daily build)