Ubuntu 17.10 login screen appearing upside down

Bug #1726232 reported by Scott Jacobi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
iio-sensor-proxy (Ubuntu)
Expired
High
Unassigned

Bug Description

Ever since I upgraded my laptop from 17.04 to 17.10, my login screen has been upside down, and I can find no way to correct it. I can successfully login. When I first logged in, my desktop was upside down as well. I was able to correct that by typing "xrandr --output eDP-1-1 --rotate normal" and that setting has stuck, but it has had no effect on my login screen. This laptop does not have an orientation sensor, no screen rotation is intended. This is a MSI GS60 6QE laptop, with a GeForce GTX 970M GPU, nVidia driver 384.90 installed. I apologize if there is a simple setting that I have overlooked, but I scoured Google for hours with no luck.

Scott Jacobi (plotor)
affects: wpasupplicant (Ubuntu) → ubuntu
Revision history for this message
Scott Jacobi (plotor) wrote :

I found a work around for this problem. I added that same xrandr command (xrandr --output eDP-1-1 --rotate normal) near the bottom of my /etc/gdm3/Init/Default file, just before the "exit 0". This corrected my login screen orientation. I would still consider the fact that my Ubuntu upgrade felt that my screen needed to be rotated 180 degrees a bug, but this work around will suffice.

Revision history for this message
Scott Jacobi (plotor) wrote :

Update: My solution above didn't stick. My login screen is back to being rotated 180 degrees, even with that xrandr command in my Default file.

Jeremy Bícha (jbicha)
affects: ubuntu → iio-sensor-proxy (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

What's the output of those commands for you?
$ gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy
$ G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
$ udevadm info --export-db | grep iio

Changed in iio-sensor-proxy (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Scott Jacobi (plotor) wrote :

Hi, thanks very much for investigating this. Here's the output of all that you asked for:

procyon@MSI-GS60-6QE:~$ gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy
node /net/hadess/SensorProxy {
  interface org.freedesktop.DBus.Properties {
    methods:
      Get(in s interface_name,
          in s property_name,
          out v value);
      GetAll(in s interface_name,
             out a{sv} properties);
      Set(in s interface_name,
          in s property_name,
          in v value);
    signals:
      PropertiesChanged(s interface_name,
                        a{sv} changed_properties,
                        as invalidated_properties);
    properties:
  };
  interface org.freedesktop.DBus.Introspectable {
    methods:
      Introspect(out s xml_data);
    signals:
    properties:
  };
  interface org.freedesktop.DBus.Peer {
    methods:
      Ping();
      GetMachineId(out s machine_uuid);
    signals:
    properties:
  };
  interface net.hadess.SensorProxy {
    methods:
      ClaimAccelerometer();
      ReleaseAccelerometer();
      ClaimLight();
      ReleaseLight();
    signals:
    properties:
      readonly b HasAccelerometer = true;
      readonly s AccelerometerOrientation = 'normal';
      readonly b HasAmbientLight = false;
      readonly s LightLevelUnit = 'lux';
      readonly d LightLevel = 0.0;
  };
  node Compass {
  };
};
procyon@MSI-GS60-6QE:~$ G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
** (process:4305): DEBUG: iio-sensor-proxy is already running, or it cannot own its D-Bus name. Verify installation.
procyon@MSI-GS60-6QE:~$ udevadm info --export-db | grep iio
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: SYSTEMD_WANTS=iio-sensor-proxy.service

Revision history for this message
Eduardo Aquiles Radanovitsck (eduardoaquiles-ar) wrote :
Download full text (4.5 KiB)

I have the same issue. The login screen and Wayland are by default rotated 180 degrees. Gnome is working fine. I have an HP OMEN laptop that has some sensor to identify if the laptop is "falling" and disable the HD. I don't know about another accelerometer, however, if I rotate the laptop, Ubuntu flips my screen as I move it. Either it is reading the value incorrectly or the sensor is mounted upside-down. Either way, there should be a way to disable this system-wide and use the same orientation that Gnome is using.

Since it was asked the output of some commands to another user, I'm pasting the output of my computer as well (with the laptop on a platform on top of the table):

gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy
node /net/hadess/SensorProxy {
  interface org.freedesktop.DBus.Properties {
    methods:
      Get(in s interface_name,
          in s property_name,
          out v value);
      GetAll(in s interface_name,
             out a{sv} properties);
      Set(in s interface_name,
          in s property_name,
          in v value);
    signals:
      PropertiesChanged(s interface_name,
                        a{sv} changed_properties,
                        as invalidated_properties);
    properties:
  };
  interface org.freedesktop.DBus.Introspectable {
    methods:
      Introspect(out s xml_data);
    signals:
    properties:
  };
  interface org.freedesktop.DBus.Peer {
    methods:
      Ping();
      GetMachineId(out s machine_uuid);
    signals:
    properties:
  };
  interface net.hadess.SensorProxy {
    methods:
      ClaimAccelerometer();
      ReleaseAccelerometer();
      ClaimLight();
      ReleaseLight();
    signals:
    properties:
      readonly b HasAccelerometer = true;
      readonly s AccelerometerOrientation = 'bottom-up';
      readonly b HasAmbientLight = false;
      readonly s LightLevelUnit = 'lux';
      readonly d LightLevel = 0.0;
  };
  node Compass {
  };
};

(I stopped the service before running the next command)
eduaquiles@eduaquiles-OMEN-by-HP:~$ sudo G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
** (process:2761): DEBUG: Found input accel at /sys/devices/platform/lis3lv02d/input/input12/event11
** (process:2761): DEBUG: Found device /sys/devices/platform/lis3lv02d/input/input12/event11 of type accelerometer at Input accelerometer
** (process:2761): DEBUG: Accel read from input on '(null)': 7, 853, 814 (scale 0.038320)
** (process:2761): DEBUG: Accel sent by driver (quirk applied): 7, 853, 814 (scale: 0.038320)
** (process:2761): DEBUG: Emitted orientation changed: from undefined to bottom-up
** (process:2761): DEBUG: Handling driver refcounting method 'ClaimLight' for ambient light sensor device
** (process:2761): DEBUG: Handling driver refcounting method 'ClaimAccelerometer' for accelerometer device
** (process:2761): DEBUG: Handling driver refcounting method 'ClaimAccelerometer' for accelerometer device
** (process:2761): DEBUG: Accel read from input on '(null)': -5, 852, 814 (scale 0.038320)
** (process:2761): DEBUG: Accel sent by driver (quirk applied): -5, 852, 814 (scale: 0.038320)
** (process:2761): DEBUG: Accel read from input on...

Read more...

Revision history for this message
Eduardo Aquiles Radanovitsck (eduardoaquiles-ar) wrote :

Sorry, typing in 180 degrees made me mix some things. There are two options on my login: "Ubuntu on Xorg" and "Unity". I have the issue on the login screen and on "Ubuntu on Xorg". On "Unity" I don't have the issue.

Revision history for this message
Mark Jowett (deedtheinky) wrote :

I had a similar problem that I solved, but the answer turned out to be a bit strange.

I had a PS4 controller plugged in to my laptop, and it was somehow reading the gyroscope of the controller as the orientation of the computer, and it just stayed at whatever orientation it was at when the controller was unplugged.

So I fixed it by plugging the controller back in, turning it upside down so the login screen flipped back to normal, and then uplugging it again!

Not sure if this is necessarily the solution to OP's problem, but it fixed it for me and since this is on the front page of Google results when you search this issue I thought I'd add it in case it's helpful. :)

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

[Expired for iio-sensor-proxy (Ubuntu) because there has been no activity for 60 days.]

Changed in iio-sensor-proxy (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Stian Skjelstad (mywave) wrote :

Problem continues into 18.04.2 #1767650

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.